Accessibility
This page says what has been done and what has not. It is not a conformance claim, because no formal audit of this build has been carried out.
What is in place
- Every interactive element can be reached and operated with a keyboard, and the focus outline is never removed.
- Colour is never the only way a state is shown. A status always carries a word as well as a colour.
- Text and background pairs were measured rather than judged by eye. Body text on white is 20.2 to 1, the brand blue on white is 8.59 to 1, and no running text uses a grey below the measured threshold.
- Charts carry their unit in the axis label and again in the caption, so a figure is readable without relying on colour.
- Forms label every field, mark an invalid field with aria-invalid, and put the error beside the field rather than only at the top.
- Tables use real table markup with header cells, so a screen reader can announce a row properly.
- Motion is limited to short transitions, and every one is switched off when the operating system asks for reduced motion.
- Each page has one h1, and headings go down in order without skipping a level.
- A skip link is the first thing in the tab order on every page.
- The layout works from 320 px upwards without a horizontal scrollbar.
What has not been done
- The product has not been tested with a screen reader by somebody who uses one every day. Automated checks and keyboard testing are not a substitute for that.
- Date fields use the browser control, which varies between platforms and is not equally good on all of them.
- Long data tables scroll sideways on a narrow screen rather than reflowing into cards.
If something here gets in your way, write through the contact page and say what you were trying to do. That is more useful to us than a score.