Accessibility

Our commitment

We aim to meet WCAG 2.2 Level AA across this website and the application. Accessibility is treated as a build requirement rather than a later audit.

What that means in practice

• Every text colour pair in our design system has a measured contrast ratio recorded against both backgrounds, and each one meets or exceeds 4.5:1. Two tokens were changed during the build because measurement showed they failed.
• Focus indicators are never removed, and are a 2px high-contrast ring at 2px offset.
• Everything is operable by keyboard, with a skip link and a logical tab order.
• Touch targets are at least 44×44px with spacing between them.
• Every form control has a visible label; errors appear next to the field they concern and are announced to screen readers.
• Colour never carries meaning alone — code status always has a text label as well as a colour.
• prefers-reduced-motion is respected globally; the single animated moment on the site renders in its final state immediately.
• Generated QR codes carry alternative text describing their destination, rather than the unhelpful "QR code".

Known gaps

Stated plainly, because a statement listing only successes is not useful:

• The colour pickers in the code designer rely on the browser's native colour input, whose accessibility varies between browsers. Hex values can be typed directly as an alternative.
• Scan analytics charts convey trends visually. Every chart has an accompanying data table, but we have not yet added text summaries of the trend itself.
• We have tested with keyboard navigation, automated tooling and screen readers, but we have not yet commissioned an independent audit by disabled users. We intend to.

Reporting a barrier

If something here does not work for you, please tell us — [email protected] or the contact form. Describe what you were trying to do and what assistive technology you were using if relevant. We treat accessibility reports as bugs, not feature requests, and we will tell you what we are doing about it.

Assessment approach

Self-assessment, using automated checks in our build pipeline, manual keyboard-only testing, and contrast ratios computed from our design tokens rather than estimated by eye.