Accessibility
We build to WCAG 2.2 Level AA. That is a floor rather than a finish line, and this page says what we hold ourselves to, what we have not got to yet, and how to tell us when something is in your way.
Built in, not bolted on
Contrast is tested, not eyed
Every colour pair in the product is asserted against the AA ratios by an automated test that fails the build. Interactive borders are held to 3:1 so a control cannot become invisible.
Never colour alone
Anything that means something carries a word as well as a colour. At the door, a verdict also carries a distinct vibration pattern, because a door is worked in the dark.
Keyboard and screen reader
Every control is reachable by keyboard with a visible focus ring, every page has a skip link, and errors are announced and say what to do rather than only what went wrong.
Targets and zoom
Tap targets are at least 44 points. Pinch-zoom is never disabled — a test fails the build if anybody tries — and the layout reflows rather than scrolling sideways.
Accessible tickets are a ticket type
Organisers can mark a ticket type as accessible seating and attach a companion ticket to it, so a wheelchair space and the seat beside it are sold together rather than separately and hopefully. Accessibility information an organiser writes appears on the event page as a section in its own right, at the same weight as the price — not as a footnote below it.
What is not there yet
- No iOS app. There is no Apple Developer account yet, so iPhone users get the website and the web ticket rather than a native app. The web ticket works offline and installs to the home screen; what is missing is push notifications.
- The browser-based door scanner is slower than the Android app. No browser on iOS can decode a QR natively, so it is done in software. It works, and it is not as quick.
- Accessibility information is written by organisers. We require the field and give it a place; we cannot guarantee what an individual organiser puts in it, or that a venue is as described.
- No independent audit yet. Our conformance claim rests on automated testing and our own review. An external audit is planned before launch and this page will say so when it happens.
If something is in your way
Tell us what you were trying to do, what happened, and what you were using — the browser or phone, and any assistive technology. That is usually enough for us to reproduce it.
For a problem with a specific event — the venue, the seating, what an organiser wrote — the organiser is the faster route, and their contact details are on the event page. For anything about this site itself, reply to any email we have sent you.
If you cannot complete a purchase because of something here, tell us and we will help you get the ticket. Not being able to buy is not an acceptable outcome while we fix it.
Also useful: refunds and the ticket terms.