Skip to content

Accessibility

WCAG 2.2 level AA

We build to WCAG 2.2 level AA across every surface: the marketing site, a studio's storefront, checkout and the studio console. That is the target we work to, not a certificate anyone has issued us.

What an automated check covers today

An automated check runs against marketing site, storefront themes, checkout and studio console.

  • Marketing site — checked automatically. Six pages are scored by Lighthouse in the browser suite, and a run fails on anything under a perfect accessibility score.
  • Storefront themes — checked automatically. Every hosted theme is checked against axe on six pages, and a build fails on a single moderate or worse issue. Colour pairs are checked for contrast when a theme is uploaded and refused if they fall short.
  • Checkout — checked automatically. The filled-in checkout is checked against axe in the browser suite, and a run fails on a moderate or worse issue.
  • Studio console — checked automatically. Six console screens are checked against axe in the browser suite, and a run fails on a moderate or worse issue.

An automated check finds a fraction of what matters. It cannot tell you whether a booking flow makes sense with a screen reader, or whether a room grid is usable with a keyboard alone. We test those by hand and we get them wrong sometimes.

What we know is not there yet

  • A studio can upload its own theme, and we cannot promise the accessibility of markup somebody else wrote. Colour pairs are checked at upload and refused if the contrast falls short; nothing else about an uploaded theme is checked.
  • A studio writes its own room descriptions, page content and images. Where alternative text is missing, it is missing because the studio left it blank.
  • The console's calendar is a dense grid. It is reachable by keyboard, but it is the screen most likely to be awkward with assistive technology.

Tell us what you hit

Email [email protected] with the page, what you were trying to do, and what stopped you. Say what you are using — browser, screen reader, magnifier — if you can; it usually decides how fast we can reproduce it. We reply within five working days.

If a barrier is on a particular studio's storefront rather than on our own screens, tell us anyway — we will work out which of the two it is. See also our security page and the terms of service.