Effective 14 September 2026
Accessibilitystatement
We aim for WCAG 2.1 AA across the site, and we treat a miss as a bug.
Our goal
The site is small, rendered on the server, and built with semantic HTML, so it stays readable and navigable with a keyboard and with assistive technology. We measure it against WCAG 2.1 AA and fix what falls short.
Colour and contrast
Text and controls meet the AA minimum of 4.5:1 against the ground. The brand sage is 2.09:1 there, so it carries only stops, rules, and large display type; a deeper sage at 5.07:1 is used wherever the colour has to be read. On the deck's dark ground the brand sage reaches 6.62:1 and is used directly. Colour is never the only carrier of meaning.
Structure and keyboard
Every page has a skip link, a single main landmark, one first-level heading, and a visible focus ring on keyboard navigation. The capability deck can be driven by keyboard, by on-screen controls, and by swiping on touch devices, and slide changes are announced to screen readers.
Motion
Everything that moves is a spring, and every spring jumps to its resting state when your system asks for reduced motion. With JavaScript off, the page shows every element at rest, so nothing depends on a script to be readable.
Known limitations
- The menu on small screens closes on Escape and leaves the tab order when shut, but it does not yet trap focus while open. Tabbing past its last link can reach content behind it.
Reporting an issue
If something on this site is hard to use, or you cannot reach content you need, tell us through the contact form on the home page. We treat accessibility reports as bugs and fix them.