Skip to main content
AllPlay Party

Accessibility

This page is maintained by the AllPlay Party team to explain how the product is built and what we are still working on.

Our target

We design and build against WCAG 2.2 Level AAA wherever it applies to a live game. That is the target we work to. It is not a certification, and we do not claim to have been audited against it.

What we have built

  • Semantic HTML first, with ARIA only where native elements cannot express the meaning.
  • A skip to main content link as the first focusable element on every page.
  • One H1 per page and a heading structure that never skips a level.
  • Body text at a contrast ratio of at least 7 to 1, and large text at least 4.5 to 1.
  • A thick, high contrast focus indicator on every interactive element.
  • Touch targets of at least 44 by 44 CSS pixels.
  • Layouts that reflow at narrow widths and stay usable at 200 percent text size and beyond.
  • No flashing content. Motion respects your system reduced motion setting and can be switched off entirely.
  • No audio plays until you knowingly switch voice feedback on.
  • Everything the game says aloud is also written on screen.
  • Single key shortcuts that pause while you type and can be turned off.

The AI Game Guide

The Game Guide is an optional conversational helper. It exists to reduce setup effort, and it never becomes the only way to do anything.

  • Every guided step has an equivalent button, form field and keyboard path. You can leave guided setup at any point and your answers are copied into the form.
  • Speech input is push to talk. The microphone is requested only when you activate Speak, recording stops when you say so, and the audio is discarded once it has been transcribed.
  • Transcripts are shown before anything is applied, so you can correct a misheard answer.
  • Everything the guide says is written on screen word for word, and speech can be stopped instantly with the Stop speaking button or the Escape key.
  • Room codes are read one character at a time using a phonetic alphabet, for example “K, as in Kilo”.
  • The guide cannot invent rules, cannot write prompts, and cannot change a setting on its own. It can only fill in the setup questions you answer, and the room is created only after you confirm the summary.
  • Voices are described by how they sound rather than by persona, and there is a no-voice option for people who prefer their own screen reader.
  • If speech recognition or spoken output is unavailable, the guide keeps working as text and tells you what happened.

What we are still testing

  • Full screen reader passes with JAWS, NVDA, VoiceOver and TalkBack.
  • Speech input flows with Voice Control and Dragon.
  • Switch access and keyboard-only play across a complete game.
  • Speech recognition accuracy for a wider range of accents and speech patterns.
  • Long guided-setup sessions on slower connections.

Tell us what is not working

Accessibility problems are treated as bugs, not requests. Use the accessibility report form and tell us what you were doing, what you expected, and which assistive technology you use. You can also contact us for anything else.