Accessibility
We aim at WCAG 2.1 AA. Here is what that means in practice, and where we fall short.
Last changed:
What we aim at
The target is WCAG 2.1 at level AA, which is also the standard the European Accessibility Act will hold us to. It is not paperwork: most of those requirements are written for people who use a site by other means than a mouse and good eyesight, and those are our players too.
What works
- Everything can be operated from the keyboard, and the focused element is visible.
- Dialogs keep focus inside and close with Esc.
- Controls have a hit area of at least 44 by 44 points.
- Pages deliver their whole content without JavaScript running.
- When somebody asks their system for less motion, animation does not start — including the mark turning in the background.
- Images that mean something carry a description; decoration is hidden from readers.
- Each page has one first-level heading and a descending hierarchy under it.
Contrast, measured
The ratios are computed from the token values rather than judged by eye. Small text needs 4.5:1, large headings and controls 3:1. Measured on 22 August 2026, against the warm palette the site wears today.
- Primary text, on the canvas and on every surface
- 15.3 : 1 and up
- Secondary text
- 8.8 : 1 and up
- The dimmest text the page uses at all
- 5.3 : 1
- The amber accent, as text and as a line
- 7.8 : 1
- Text on an amber button
- 7.7 : 1
- Status colours (up, failing) as text
- 5.7 : 1 and up
No pairing the page builds falls below the small-text bar. When the palette changes this gets measured again — these numbers are a promise only until they are not.
Where we fall short
These are known and being worked on:
- We have not been through the site end to end with a real screen reader. It has only been through automated checks, and those catch nowhere near everything.
- Contrast is measured by machine whenever the look changes, but surfaces differ and a new one always has to be run through again.
Telling us
If you hit something, write to us with the button at the bottom right or on Discord. Say what you were doing and what you use to get around — a screen reader, the keyboard, magnification. We answer and we fix; an accessibility bug is not cosmetic here.
In writing: [email protected].