What is supported
Colour and contrast
Every one of the 23 board themes is checked in both light and dark modes. Text that takes its colour from the theme meets the 4.5:1 minimum against the surface it sits on, interface outlines and the keyboard focus ring meet 3:1 against every board surface they can be drawn over, and each checker keeps a visible edge against every field, point and bar colour. Some text takes its colour from a fixed brand palette instead, and part of that palette does not clear the bar — seewhat is not supported yet.
Those checker and point colours are also checked under simulated protanopia, deuteranopia and tritanopia — the three common forms of colour blindness — so the signal that tells you whose piece is whose survives the loss of a cone class. Board state is never carried by colour alone: a legal destination, a hovered destination and the last move played differ by shape, not by hue.
Playing without a pointer
The board is fully keyboard operable. Arrow keys move a visible cursor between points, Enter picks a checker up and Space puts it down, so a complete move can be played with no pointer at all. Modal dialogs release focus rather than trapping it.
Dragging is never required. Every move can also be made by tapping the source and then the destination.
Screen readers
Each point, the bar and both bear-off trays publish their own screen-reader element carrying the owner and the number of checkers on it. Only points you can legally play from are exposed as activatable, so tabbing does not walk you through two dozen dead squares. Selection state is announced, and the end of a game is announced through a live region rather than by stealing focus mid-sentence.
Large text
Shared controls are checked at the largest accessibility text size on both platforms — roughly three times the default — and grow to fit their labels instead of clipping them. Buttons keep a 48 dp touch target at every size.
Reduced motion
Turning on Reduce Motion (iOS) or Remove animations(Android) collapses every board animation to zero duration. Dice do not tumble, checkers do not fly, and invalid-move flashes resolve immediately.
What is not supported yet
These are real gaps, listed because you may need to know about them before you install anything.
- Screen-reader narration has not been tested end to end.Individual elements are checked automatically on every build, but nobody has yet sat down with VoiceOver or TalkBack and played a full match to confirm the announcements make sense together. Until that happens we do not claim VoiceOver or TalkBack support, and we have not filled in Apple's Accessibility Nutrition Label.
- Board narration is in English only. The interface is available in 11 languages, but the point names a screen reader reads out on the board are English regardless of which one you choose.
- Board points are small targets. Twelve points share each row, so on a phone a point is about 24–29 pixels wide — below the 24 × 24 minimum on the narrowest screens, and well below the enhanced 44 × 44 guideline everywhere. A board cannot be laid out otherwise and still be a board. The keyboard cursor and the screen-reader elements exist precisely so that the small targets are not the only way to play.
- Some small labels are too low-contrast. A few pieces of text use a fixed brass or muted-walnut brand colour rather than the theme's, and on the dark card backgrounds they sit on those measure roughly 4.1–4.4:1 instead of the required 4.5:1. The clearest examples are the app-version line at the bottom of Settings and some small section headers. It is a narrow miss, but it is a miss, and it is why we have not declared "Sufficient Contrast" on Apple's accessibility label.
- Large-text checking is not exhaustive. Shared components and twelve screens are checked at large text sizes. The rest of the app is not, so there may be clipped labels we have not found.
- Some criteria are unchecked. Reflow at very large text in landscape, user-adjusted text spacing, and the behaviour of tooltips on hover or focus have no automated check and no manual pass.
How we check
The contrast, target-size, text-scaling, reduced-motion, keyboard and screen-reader-element claims above are not a one-off review. They are automated tests that run on every change, across every theme and both brightness modes — several hundred colour pairs per run. If a change breaks one, the build fails before it ships.
We chose tests over a periodic manual review because a manual review goes stale the moment the next theme lands, and we have added many. What tests cannot judge — whether a spoken match actually makes sense — stays a manual pass, and it is the pass we have not done.
Tell us what breaks
If something here is wrong, or something works badly for you, we want the report — including the parts we have already listed above, because knowing which gap actually blocks a real person is what decides the order we fix them in.
[email protected]— please say which device, which operating-system version, and which assistive technology you were using. You can also usethe support page.
We aim to reply within five working days. We are a very small team, so a fix may take longer than a reply.