Last updated 7 August 2026
Know Ball? should be playable however you use a browser — with a keyboard, with a screen reader, with text scaled up, or with motion turned down. This page says how far that goes today and where it doesn't reach yet.
We target WCAG 2.2 level AA. Screens are checked with axe-core, and the contrast of each text and background pair is measured from what production actually serves rather than from the design file.
All five games can be played to the end with a keyboard alone. The player search is a listbox: arrow keys move through the suggestions, Enter plays the highlighted name, and typing a name in full works for players the list deliberately leaves out.
Guess feedback is announced to screen readers as well as shown, in every game, so a wrong guess is never signalled only by the board shaking. The Scout's cells carry a mark as well as a colour — ✓ for an exact hit, ~ for a near miss, ? for not yet known, and nothing at all for a miss — because green against amber is unreadable for roughly one man in twelve.
Text can be scaled to 200% without losing content, the layout holds down to a 360px-wide screen with no sideways scrolling, and controls are at least 44 by 44 pixels. Animations respect prefers-reduced-motion.
We want to know. If a screen, a control or a game is hard to use, tell us what you were trying to do, which game it was, and what you were using to do it — that is usually enough to reproduce it.
Automated checks with axe-core across the screens. Manual keyboard passes through all five games. Contrast measured from the rendered page rather than the palette. Layout checked at 360px wide and at 200% text. This statement is reviewed whenever a game changes shape, and it was last checked on the date at the top.