Accessibility Statement

Partial conformance with WCAG 2.2 Level AA. Most of the product has been audited against that standard and remediated. The exceptions are listed below rather than left for you to discover.

We reviewed this statement on 17 September 2026 and review it every three months, and whenever we change something substantial about how the site is used.

In September 2026 we audited every patron-facing page, the shared form controls, and the staff tools against WCAG 2.2 Level AA, found 41 problems, and fixed all of them. Among them:

• Every control on the way to buying a ticket — the quantity steppers, the event tiles, the add-on toggles — is a real button or link that works with a keyboard.
• Every form field has a label a screen reader can read, and errors are tied to the field they are about and announced when they appear.
• Text and control borders were re-coloured to meet the contrast minimums; nothing important is signalled by colour alone.
• The focus ring was put back everywhere it had been removed, and the sticky header and fixed buttons no longer cover the thing you are on.
• Pages have a single top-level heading, a skip link, landmarks, and a title that changes when you navigate.
• The carousel can be paused, hidden panels leave the tab order, and animations respect a reduced-motion setting.

Every change is checked automatically before it ships: a linter that catches inaccessible markup, and scans of the rendered interface with axe-core that fail the build on a serious or critical problem. The pages you use to buy a ticket are covered specifically, so a change that breaks them cannot be released.

Colour contrast was calculated from our design system rather than measured in a browser, because the automated scans run without one.

We have not yet tested this site with a screen reader ourselves. The fixes above were verified by reading the code and by those automated scans. A pass with VoiceOver and with NVDA is planned, and we will name what we used and when, here, once it has happened. We would rather tell you that than imply a test we have not done.

• No screen-reader testing has been done by us. Every fix was verified by reading the code and by automated scans, not by listening to the page. We have no recorded pass with VoiceOver or NVDA, so we do not claim one.
• The card payment field is Stripe's, not ours. Card details are entered into Stripe's Payment Element, a component Stripe builds and maintains. Its accessibility is theirs; the colours we ask it to use are ours, and those were fixed.
• Automated checks cannot see colour on a real screen. Our automated scans run without a browser, so they cannot measure contrast. We calculated it from the design system instead and check it by hand when colours change.
• Downloadable tickets and reports are images and PDFs. A ticket PNG and an exported PDF report are not tagged documents. The same information is available as text on the page and in the confirmation email.

Email support@backdoor.toolswith “accessibility” in the subject. Tell us what you were trying to do, what got in the way, and what you are using — a browser and screen reader if you know them, or just what happened if you do not.

We reply within two business days. If a barrier is stopping you from buying a ticket, say so and we will complete the purchase with you rather than wait for a fix — a booking you cannot make today is not helped by a release next month.

Reports of barriers are treated as bugs, with the same priority as anything else that stops a purchase. If we cannot fix something quickly, we will tell you what we are doing instead.

Backdoor Tickets — support@backdoor.tools.

Privacy Policy · Terms of Sale and Service · Cookie Policy · Back to events