Accessibility

We are building to WCAG 2.2 level AA. We are not there yet, and the honest thing is to say which parts are not there rather than claim the target as an achievement.

What holds today

• Every warrant state is written out in words next to its colour, on every screen and in every export. Nothing in this product means anything by colour alone.
• A skip link, one main landmark, and headings in order on every page.
• Visible focus outlines that are not removed anywhere, and form fields with real labels rather than placeholder text standing in for one.
• The site follows your system light or dark setting, and the palette is defined once so both themes stay consistent.
• No text is set in an image, and no font is loaded from another server, so your own font settings hold.
• Wide content scrolls inside its own box. The page body never scrolls sideways.

Known gaps

This list is the point of the page. It shrinks as things are fixed, and nothing is removed from it because it became inconvenient.

• No independent audit has been done. Everything below is our own testing, which is exactly the kind of self-assessment a reader should discount.
• The audit report's wide tables scroll sideways inside their own box on a narrow screen. They do not break the page, but reading a wide table on a phone is still poor.
• Keyboard order through the writing workspace has not been walked end to end. The public pages have; the workspace has not.
• The upload and audit flow has not been tested with a screen reader, and a long-running audit does not announce its progress to assistive technology.
• The amber used for delegable with verification has not had its contrast measured in dark mode. The state name is always written out beside the colour, so no meaning is carried by colour alone, but the number is not known.
• Diagrams and flow strips have no long text alternative yet. The surrounding prose carries the same information, which is a mitigation rather than a fix.
• Text has not been tested at 200% zoom on every page, nor with a browser reflow at 320 pixels.

If something here blocks you

Tell us through the helper on any page, and say what you were trying to do and what stopped you. A barrier that stops you finishing a task is treated as a fault in the product, not as a request for an alternative route around it. The gap list above is updated when one is fixed.