Accessibility Statement

Our target

We hold this platform to WCAG 2.2 Level AA, and describe ourselves as partially conformant. We know of no failure. The word is there because of what we have not yet checked. Every public page passes the automated checks we run, but the pages you only see once signed in have not been through the same sweep, and there has been no independent audit. The detail is below.

What meets the bar

• Every page can be operated by keyboard alone, and a skip link is the first thing focus reaches.
• The examination runner announces the time remaining at 30, 10, 5 and 1 minutes, and on submission, so a candidate using a screen reader hears that time is running out when everyone else sees it. Announcements are polite, so they never cut across a question being read aloud.
• Errors are announced when they appear rather than only shown in colour.
• Pages use real landmarks and headings, and images that carry meaning have text alternatives.
• Content reflows to 320px and survives 200% zoom without loss of function.
• The site works with a light or dark palette, and respects a reduced-motion preference.

What we know is not covered

The August 2026 review checked 23 public pages and found four kinds of failure, all since fixed: inline links that were distinguished only by being teal are now underlined, and small category labels on the roadmap and the tier pages, which measured between 2.07:1 and 4.42:1 against their background, now use the darker values the design system had already defined for light backgrounds. Those pages report no violations.

Two gaps remain.

• The signed-in pages, such as your profile and the examination runner, are not part of the automated sweep, because it runs without an account. Their components are checked one at a time as they are built, which is a weaker check than testing the whole page.
• No independent audit and no formal screen-reader testing has been carried out. When either happens, this page will say so and say who did it.

How we test

Automated checks (axe-core, WCAG 2.0/2.1/2.2 A and AA rules) run against every public page, and components are checked in isolation as they are built. Automated tools catch only some real barriers. They are good at contrast ratios and missing labels, and cannot tell whether a page makes sense in the order a screen reader reads it. A clean automated run is the minimum, which is why the section above lists what has not been examined as well as the result.

Sitting an examination with an adjustment

If a standard sitting would not give you a fair chance to show what you know, for any reason, contact us through the Contact page before you schedule. That includes disability, a health condition, or assistive technology that needs particular arrangements. We consider adjustments case by case and handle them confidentially. Asking has no bearing on your result and is not recorded on your credential.

Telling us about a problem

Report anything that blocked you through the Contact page. Please say what page you were on, what you were trying to do, and what you use to browse. We aim to reply within 5 working days. If you are in the UK or EU and are not satisfied with our response, you can raise the matter with your national accessibility enforcement body.