Target and current status
Chronira is designed with WCAG 2.2 level AA as its target. This is a goal, not a formal certification: the site has not been audited by an external organisation, and some parts may still fall short. Problems that are reported are treated as errors to fix.
What is in place
- Keyboard support. Every tool, menu and button can be reached and used with a keyboard, with a visible focus indicator. A “skip to content” link is the first item on each page, and the search can be opened with Ctrl + K (Cmd + K on a Mac).
- Screen reader labels. Form fields have text labels, icon buttons have accessible names, and results are announced politely when they change, without interrupting what you are doing. A running timer does not announce every second, to avoid constant interruptions.
- Reduced motion. When your device asks for reduced motion, animations and transitions are removed or kept to a minimum.
- Contrast and themes. Text and controls are designed to meet AA contrast in both the light and dark themes. The theme follows your device setting by default and can be changed manually.
- Zoom and small screens. Pages are designed to reflow on phones and with text zoom, without horizontal scrolling for normal reading.
- Right-to-left layout. The Arabic version is laid out right to left, with the language correctly declared so screen readers use Arabic pronunciation.
- Plain language and clear errors. Invalid inputs, such as a date that does not exist, are explained in words and announced to screen readers, not shown only with colour.
- Printing. Results and time cards can be printed or saved as PDF through the browser’s print dialog.
Known limitations
- Some features, such as vibration or keeping the screen on while a timer runs, depend on what your browser and device support.
- Date and time fields use your browser’s built-in pickers, whose behaviour with assistive technologies varies between browsers. You can always type the value instead.
Report an accessibility problem
If something is hard or impossible to use, please describe it through the contact page: the page address, what you were trying to do, and, if you are happy to share it, the browser and assistive technology you use. Accessibility problems are treated as errors and fixed as soon as possible. You can also read how the tools work in the methodology.