Every game is keyboard-playable. A machine checks it, every single build.
Most classroom games say they're accessible. We can show you the gate that would stop us shipping if we weren't — it runs on every game, every night, and a game that fails it is pulled off the homepage automatically.
What is checked on every build
- Keyboard-operable. Every clickable control is reachable and activatable by keyboard alone. A game with a single mouse-only control fails and does not ship.
- Every control is labelled. Each button carries text or an
aria-label, so a screen reader announces something meaningful rather than "button". - State changes are announced. Each game has an
aria-liveregion; correct/incorrect feedback and progress are spoken, not just coloured. - It can actually be finished. An automated solver plays each game to completion. This is an accessibility issue too — an unwinnable game wastes the time of the students who can least afford it.
- No flashing. Nothing in the kit strobes;
prefers-reduced-motiondisables animation and transitions. - Visible focus. A 3px focus ring on every control, never suppressed.
- No login, ever. Students never create an account — which removes a password-and-email barrier that stops a lot of pupils cold.
What we do not claim
- We have not been audited for WCAG 2.2 AA conformance by a third party, and we don't display a badge saying we have.
- Colour contrast is designed for it but not yet machine-verified on every build — it's the next gate we intend to add.
- The games have not been tested with every screen reader and version. If one behaves badly with yours, that's a bug we want reported.
We'd rather list the gaps than overstate the coverage. Teachers in special education get sold "fully accessible" constantly and find out otherwise in front of a class — that is not a discovery we want anyone making with our games.
Found something that doesn't work?
Tell us which game and what happened and it gets fixed — accessibility bugs go to the front of the queue, ahead of new features. Send it here, or use the chat in Make a game. Requests for a game that suits a specific need — larger targets, fewer items per screen, a particular reading level — are welcome too; building to order is the normal way this works, not a favour.
Every game page also publishes its accessibility properties as structured data (accessibilityFeature, accessibilityControl, accessibilityHazard) so directories and search engines can read them without taking our word for it.