Accessibility Statement

Conformance target

We aim to meet WCAG 2.2 Level AA across the practice tool and the guides. This is a target we hold ourselves to, not a certificate: the site has not been through an independent third-party audit, and we are not claiming formal conformance. What we can tell you is exactly what has been implemented and tested, which is what the rest of this page covers.

Keyboard and assistive technology

• Every interactive control is a native button, a, input, select, or textarea, so it is reachable with Tab and activated with Enter or Space without custom key handling.
• A “Skip to main content” link is the first focusable element on every page, so keyboard users can bypass the navigation.
• The mobile menu button reports its state with aria-expanded and points at the menu it controls with aria-controls.
• The page uses landmark regions — header, primary navigation, main, contentinfo — so screen reader users can jump between sections.
• Every form field has a visible label programmatically associated with it. There are no placeholder-only inputs.

Colour and contrast

Body text, links, buttons, and form controls meet the AA threshold of 4.5:1. The palette was measured against the lightest surface a colour actually appears on rather than against pure white, because a colour that passes on white can still fail on a tinted section background.

Colour is never the only way a state is communicated:

• A selected seat turns green, gains a check mark, and carries a heavier border ring.
• A sold seat is greyed, struck through, and genuinely disabled, so it cannot be clicked at all.
• Seat state is also exposed to assistive technology through aria-pressed and a spoken label such as “Selected seat A3”.

Motion, focus, and zoom

• Focus is always visible: a 3 pixel outline with a 2 pixel offset is applied to whatever currently has keyboard focus.
• Animations and transitions are suppressed when your system asks for reduced motion, via prefers-reduced-motion.
• Layout and type use relative sizing, and the pages are tested at narrow viewports.

Announced state changes

The simulator gives spoken feedback rather than silently changing numbers. The status line under the drill, and the selected-seat counter, are polite live regions, so a screen reader announces the queue clearing, a chaos event, a score, and each seat you lock in.

Known limitations

We would rather list the gaps than imply there are none:

• Third-party adverts. Ads are served by Google. We control that they are separated from content and labelled, but we do not control the markup or accessibility of the ad creative itself.
• The seat grid is inherently spatial. Seat state is announced in words, but the visual layout of rows and blocks is not fully conveyed to a screen reader user. The guides and the checkout drill carry the same practice value without the grid.
• No independent audit yet. Everything above was verified by us, in-browser, against the code. That is not the same as a formal audit by an accessibility specialist, which is on the list.

Tell us when something blocks you

If any part of this site is unusable with your setup, please use the Contact page and describe the page, the assistive technology you use, and what happened. Accessibility reports go to the front of the queue.

This statement was last reviewed on 16 September 2026.