Accessibility
An inaccessible product is a broken product, so this is a standard we hold our own work to rather than a policy we wrote afterwards.
- Target
WCAG 2.2 Level AA
The standard we design and build to, and the one we test against.
- Keyboard
Fully operable
Every interactive element is reachable and usable by keyboard, with a visible focus indicator at every step.
- Colour contrast
AA or better
All text and meaningful interface components meet or exceed the minimum contrast ratios in both themes.
- Motion
Respected
Animations, the typewriter, marquees and the WebGL hero all stop when your system requests reduced motion.
- Structure
Semantic landmarks
Landmarks, a skip link, one h1 per page and a logical heading order, so assistive technology can navigate rather than guess.
- Forms
Labelled and announced
Every field has a real label, errors are tied to their input and announced through a live region.
What we have not tested
We test with keyboard navigation, screen readers and automated tooling, but we have not completed a formal audit with manual assistive-technology testing by disabled users. That is a real gap and we would rather state it than imply otherwise.
Found a barrier?
Please tell us, including what you were trying to do and which browser and assistive technology you were using. We will treat a report as a bug and prioritise it accordingly — usually the same day.
Report a barrier