Accessibility

The standard we aim at

WCAG 2.1 Level AA, for this site and for the app.

We do not claim to conform to it. No formal audit has been carried out, and no testing with real assistive technology or with disabled users has been done. Saying "AA compliant" without that work is a claim nobody has earned, and this is not the page to make one on.

What has been checked on this site

• Every page reached and operated with the keyboard alone, with a visible focus indicator at each stop and a skip link to the main content.
• Both colour schemes - the site follows your system light/dark setting.
• Down to a 320px viewport, with no sideways scrolling of the page.
• Colour is never the only signal. Status carries a shape and a word as well as a colour; the current nav item carries weight and a rule; the unavailable pricing tier says "Coming soon" and disables its control.
• Reduced motion is honoured - if your system asks for less animation, the site does not animate.
• Headings run in order, images that carry meaning have text alternatives, and decorative graphics are hidden from screen readers rather than described.

What has not been checked

• Screen readers. Nothing here has been driven with NVDA, JAWS or VoiceOver.
• Voice control and switch access.
• Any testing with disabled users, which is the only kind that settles the question.

The app

The app is a separate product on a separate address, and its accessibility work is its own. One thing worth stating because it is unusual: its colour contrast is computed rather than judged by eye - every text pair is asserted against the WCAG contrast formula by a test that fails on a regression.

Reporting a problem

Email [TO SUPPLY: OWNER_SUPPORT_EMAIL]. Accessibility reports are treated as bugs, not as suggestions. Telling us the page, what you were trying to do, and what you were using to do it is enough - you do not need to identify which guideline it breaks.

Last reviewed: [TO SUPPLY: OWNER_EFFECTIVE_DATE]