We want the website and game to be understandable, operable, and reportable.

The website and browser game are partially assessed against WCAG 2.2 AA. We do not yet claim full conformance because the complete manual and assistive-technology test programme listed below has not been completed.

Automated checks are part of development, but they do not prove conformance on their own. Confirmed barriers will be published here with their relevant WCAG criteria and planned remediation.

• Keyboard-only Tab and Enter flows in Chromium for marketing consent and preferences, every contact-form field, game consent, starting and configuring a game, skipping the tutorial, acknowledging a turn, and rolling
• Automated Axe checks against representative WCAG 2 and WCAG 2.2 AA rules on the marketing home, consent preferences, contact form, game landing, onboarding, tutorial, active-game, and reduced-motion states
• Page reflow at 640 CSS pixels and 320 CSS pixels, equivalent to a 1280-pixel desktop viewport at 200% and 400% zoom, for representative marketing, contact, onboarding, and active-game states
• The operating-system reduced-motion preference on the marketing home and game landing, with no long-running rendered animations remaining active in the checked states
• Visible computed focus indicators on the representative marketing and game controls used by the keyboard-only paths

These are representative automated checks, not a full WCAG conformance audit. We have not completed manual testing with VoiceOver on macOS or iOS, NVDA or JAWS on Windows, voice control, switch control, screen magnifiers, or refreshable braille displays.

The verified keyboard and reflow paths do not yet cover every card type, negotiation control, scorecard variation, end-game and debrief state, browser and operating-system combination, or real browser-zoom implementation. The separate iOS experience also needs its own versioned accessibility test record before it is included in a compliance claim. Complex board-game interactions may still expose barriers that Axe and representative viewport checks cannot find.

If a page or game action is hard to read, operate, or understand with assistive technology, please tell us the route, device, browser or app version, assistive technology, and blocked action.

• Use the public contact route or report-bug route
• Include the page URL, device, browser or app version, and what went wrong
• If possible, include whether the issue blocks access completely or makes the task harder

This statement was updated on 11 July 2026 using an isolated local production build in Chromium. The evidence used keyboard-only interaction, Axe, 640-pixel and 320-pixel reflow viewports, computed focus indicators, and an operating-system reduced-motion browser context.

We review accessibility reports alongside support and bug submissions and prioritise issues that prevent a player from starting, understanding, operating, or completing the game.