Accessibility statement
We aim for the site to meet WCAG 2.2 level AA. This statement describes how we approach accessibility and the limitations we know about.
What we do
- Text and controls meet colour-contrast guidance; colour is never the only signal.
- Every workspace operation is available from keyboard-reachable menus and dialogs, not only by drag and drop.
- Status changes (saving, checking answers, AI responses) are announced to screen readers.
- Pages work at 200% zoom and on small screens, with tabbed panels on mobile.
How we test
- An automated axe scan (WCAG 2.1 A and AA rules) runs against every page template, including signed-in pages, as part of our end-to-end test suite.
- The same suite checks reflow at 320 CSS pixels wide (the equivalent of 400% zoom) and 200% text size on key pages, with no sideways scrolling.
- A keyboard-only test builds a step in the workspace, checks the answer and reaches a pass without a mouse, in Chrome, Firefox and Safari engines.
- Automated checks find only some problems, so we also review new pages by hand and fix reported barriers as bugs.
Compatibility
The site is built with standard HTML landmarks, headings and labelled controls, and is tested in current versions of Chrome, Firefox and Safari (desktop and mobile layouts). The practice workspace needs JavaScript; lessons, guides and reference pages work without it.
Known limitations
- The data grid presents large tables; screen-reader users may prefer the M editor and the result summary.
- This statement describes our own testing and isn't a formal conformance claim.
Report a barrier
If something stops you using the site, tell us with the page and what happened.
Last reviewed 5 November 2026.