A venue can have a ramp, a lift, a loop, described performances and trained staff, and still be inaccessible, because the person who needed all of that could not complete the purchase. Access provision that begins at the door begins too late.
The barriers are specific, and they repeat
A seat map drawn as an image or a canvas element with no text alternative cannot be used by anyone relying on a screen reader, and those maps are the primary interface of almost every ticketing system.
A checkout session that expires after a fixed interval fails anyone who needs longer, which includes people using switch access, people with motor impairments and people who had to fetch a card from another room.
Availability shown only by colour fails colour blind users. Form fields without labels, keyboard traps in date pickers, and a challenge that requires identifying images each remove a group of people completely.
And the most common of all: accessible seats that can only be booked by telephone, during office hours. That is a different, slower and more effortful purchasing route for one group of customers, available at times when many people are at work, and it is still widespread.
There is a published standard, and it is not new
Web content accessibility guidelines are published by the World Wide Web Consortium, in versions and conformance levels, and they are the reference every regulator points at rather than a private methodology. Conformance is testable, and much of it is unremarkable engineering: label the fields, make it work from a keyboard, do not rely on colour alone, give images text alternatives.
The legal position has moved recently
In the United States, obligations arise through disability discrimination law and have been developed largely through enforcement and litigation rather than by a single technical rule. In the European Union, accessibility requirements that had applied to public sector bodies were extended to a range of private services, including consumer e-commerce, with obligations applying from June 2025. Other jurisdictions differ again.
The practical consequence is that a ticketing website is now within scope of specific requirements in a way it was not a decade ago, and selling to audiences in more than one territory means more than one set of them applies. This is a matter for legal advice on the specific organisation.
The platform is somebody else's code and your responsibility
Most venues do not build their ticketing. They buy it, and then discover they cannot fix the seat map. This is a procurement problem before it is a technical one.
The levers available are all at the point of purchase: requiring conformance in the contract, asking for a current accessibility conformance report and reading it rather than filing it, and testing the actual booking flow with a keyboard and a screen reader before signing anything. A supplier who cannot produce a report, or whose report is a marketing document, has answered the question.
Automated testing finds a minority of it
Scanning tools catch missing alternative text, poor contrast ratios and absent labels, which is genuinely useful and is a small share of what matters. They cannot tell whether the seat map makes sense, whether the flow can be completed, or whether the error message explains what went wrong.
The tests that find real barriers are completing a booking using only a keyboard, completing one with a screen reader, and asking disabled customers to try it and report back. The last of those is the one that finds problems nobody on the staff imagined, and it is the one most often skipped.
The ticket itself is the last step
A booking completed successfully can still fail at delivery. A ticket issued only as a document designed for printing, with the seat and the barcode drawn as an image, is unreadable to a screen reader, and a patron arriving unable to confirm which seat they hold is in the same position as one who never bought it.
The fix is small and is frequently missed: state the essential details, the date, the time, the door and the seat, as plain text in the confirmation message as well as inside the attachment. That single change costs a line of template and removes a whole category of arrival day problems.
The information page is part of the provision
Everything described across this section only helps someone who knows it exists. A page that states plainly which performances are captioned or described, what assistive listening is available and how to use it, where the step free route runs and how to book a companion seat, is part of the access provision rather than marketing about it.
It also has to be findable, which in practice means linked from the main navigation rather than from a footer three levels down, and written in plain terms rather than in the language of a compliance statement.
What we cannot verify
Legal obligations differ by jurisdiction, are changing, and depend on the size and activity of the organisation; the summaries here are general and are not legal advice. Conformance claims made by ticketing platforms come from those platforms, and a conformance report is a self assessment unless it says otherwise. No automated score establishes that a booking can actually be completed, which is the only question that matters to the person trying.
The short version
- Access provision that begins at the door begins too late.
- Seat maps without text alternatives are the primary interface of most systems.
- Expiring checkout sessions exclude anyone who needs longer.
- Telephone-only booking for accessible seats is a slower route for one group of customers.
- The platform is bought, so conformance belongs in the contract and is tested before signing.
- Automated scans find a minority; a keyboard, a screen reader and real users find the rest.