What works, and what does not yet.
Lumen is a visual app, and that creates real barriers for some
people.
This page says what is supported today and where it falls short,
without rounding either up.
Last reviewed 18 August 2026.
What we are aiming at.
The reference is the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the same standard European and US public bodies are held to.
Lumen does not meet it yet, and this page does not claim otherwise. The sections below set out where it stands.
What already works.
- Screen readers can name what they find. Interactive controls carry text labels rather than relying on their icon, so a screen reader announces what a button does instead of reading a filename. Headings and regions are marked up so a page can be navigated by structure.
- Keyboard navigation and a visible focus ring. Controls are reachable with a keyboard and the focused element is drawn with a visible outline, so you can see where you are without a pointer.
- Right-to-left languages, properly. Lumen is available in Arabic, English, Chinese, Korean and Japanese. Choosing Arabic switches the whole interface to right-to-left and tells the browser which language it is reading, so a screen reader pronounces it correctly rather than reading Arabic with English phonetics.
- Reduced motion in the interface chrome. If your system asks for reduced motion, loading animations and the language-switching transitions shorten or stop.
- Text scales with your settings. The interface uses relative sizing, so raising the text size in your browser or operating system enlarges Lumen with it.
Where Lumen falls short.
- Background motion does not stop for reduced-motion settings. Lumen draws a slow, continuously moving ambient background behind most screens. It does not currently respond to a reduced-motion preference. If you are sensitive to motion, this is the part of Lumen most likely to affect you, and we would rather say so here than let you discover it. The animation system is tightly coupled to how the app renders, so changing it safely is a larger piece of work than it looks. It is on the list.
- The design leans on a dark, low-contrast aesthetic. Some secondary text and decorative edges sit at contrast ratios below the WCAG AA threshold of 4.5:1. Primary text and controls are the priority for improvement here.
- Some meaning is carried visually. Progress through a goal is shown through shape, fill and position. There is a text equivalent in most places, but not everywhere, and a screen-reader user gets a less rich picture of progress than a sighted user does.
- No formal audit has been carried out. Nobody has yet tested Lumen end to end with assistive technology, and it has not been assessed against WCAG 2.1 AA by an independent party. Until that happens we are not claiming conformance, at any level.
This list is deliberately specific. A statement that claimed full conformance would be easier to write and would not be true, and you would find out the moment you opened the app.
Tell us, and we will help directly.
Write to contact@lumen-tracker.live and describe what you were trying to do and what stopped you. Naming the assistive technology and device helps, but is not required.
We answer within one month. Where a fix will take longer than that, we will say so and offer another way to get the same thing done in the meantime.