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 is checked automatically
A check that runs on every change blocks that change when it fails. A check run by hand before a release blocks the release.
- Marketing site
- Lighthouse scores six pages and fails on anything under a perfect accessibility score, by hand before a release.
- Storefront themes
- axe reads every hosted theme on six pages, and the booking form, and fails on a moderate or worse issue; each theme's text colours are measured against WCAG AA, every change.
- Studio console
- axe reads the screens and dialogs listed below and fails on a moderate or worse issue that is not on the known list, every change.
The console check reads these screens and dialogs:
- Bookings
- A booking
- Cancelling a booking
- An order
- Calendar, day
- Calendar, week
- The calendar's booking panel
- Moving a booking from the keyboard
- Rescheduling a booking
- New booking
- A customer
- Editing a customer
- Merging two customers
- A room, with rates by activity
- Rules and policies
- Rules, booking window
- Rules, at a studio with two locations
- Rules, changes and moves
- Rules, paying and cancelling
- Rules, charges
- Charging a customer after a session
- Refunding a charge after a session
- Charging from a customer's page
- Checkout settings
- A theme's wording
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
- The console's automated check runs without a browser's layout, so it cannot measure colour contrast or target size there. Contrast of the console's own colours is measured from its design tokens instead.
- The console's calendar is a dense board. A booking on it can be moved and resized from the keyboard, but it is the screen most likely to be awkward with a screen reader.
- A studio can upload its own theme, and we cannot promise the accessibility of markup somebody else wrote. An upload is refused only when its files cannot be read; its colours and markup are not 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.
Tell us what you hit
Email ops@soundslot.app 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 aim to 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.