Accessibility

The standard we work to

WCAG 2.2 at level AA is the bar for the site and the product. This is a statement of what has been done and checked, not a certification; an audit by a third party has not been carried out yet.

What is in place

• Keyboard: every control on the site and in the product is reachable and operable by keyboard, with a visible focus ring. In the product, the topic tabs have roving focus, the [ and ] keys step between topics, the arrow keys page the notes, and the map takes the arrow and +/− keys.
• Motion: every animation on the site and in the product is off under a “reduce motion” setting — no glide, no crossfade, nothing hidden behind a transition; the home page’s scroll-driven rooms become flat stops.
• Text: the launch film carries captions, shown while it is muted and switchable with a CC control; the co-presenter’s spoken answers appear as text in the captions and the transcript panel; every slide carries its words in the DOM.
• Contrast: the type on the slide is measured against the picture behind it; the hero holds at least 7:1 in both colour schemes. Light and dark are both first-class and follow your system setting.
• Structure: one heading per page, sequential headings, landmarks for the header, the main content, navigation and the footer; images that carry meaning have descriptions.
• Type scales with your browser’s setting; the pages reflow to a single column on a narrow screen.

What is still short

• The slide is a visual composition made in real time. A screen reader hears its words in reading order, not the arrangement; the transcript panel is the reliable text equivalent of a session.
• The product is built for a desktop browser with a microphone; on a phone it keeps a flat slide and cannot yet take part fully in a room.
• Speech is the main input. Everything a person can say to the slide can also be done with a click in the history, the topic tabs and the notes keys — but there is no full keyboard equivalent for every spoken request yet.

Tell us

If something is hard to use, write to [email protected] with the page or the moment in the product, your browser and any assistive technology you use. A person reads it, and what is fixed is recorded in the changelog.