How Accessible Are Event Ticketing Pages? What the WCAG Data Shows

A year has passed since the European Accessibility Act became enforceable on 28 June 2025, and the question it raised for every organizer selling tickets online has not gone away: can a blind screen-reader user, a shopper with a motor impairment, or someone with low vision actually buy a ticket on your site? The honest answer, for most of the web, is no. This analysis pulls together the largest public accessibility datasets — the WebAIM Million, UsableNet’s litigation tracking, and the Click-Away Pound consumer survey — and maps them onto the specific steps of a ticket purchase, so you can see where ticketing pages fail and which WCAG criteria govern each step.

The state of the web: 95.9% of pages fail automated WCAG checks

The most comprehensive recurring study of web accessibility is the WebAIM Million, an annual automated evaluation of the top 1,000,000 home pages. The 2026 edition found detectable WCAG 2 failures on 95.9% of home pages — worse than the 94.8% recorded in 2025, reversing several years of slow improvement. Pages averaged 56.1 detected errors each, up 10.1% year over year.

Just six error types account for roughly 96% of everything detected, and they have topped the list for seven consecutive years: low-contrast text (found on 83.9% of pages in 2026), missing image alt text, missing form input labels, empty links, empty buttons, and missing document language. Note what those are: form labels, links, and buttons — the exact building blocks of a ticket selection and checkout flow. An automated scan only catches a subset of WCAG issues (WebAIM estimates it detects only a portion of possible failures), so real-world conformance is likely worse than these figures suggest, not better.

The legal exposure is no longer theoretical

Two regulatory forces now apply directly to ticket sellers:

United States — ADA litigation. UsableNet’s lawsuit tracking counted more than 5,000 digital accessibility lawsuits filed in 2025, with e-commerce sites the target of roughly seven in ten claims. Notably, 1,427 of those 2025 suits targeted companies that had already been sued over accessibility before — settling once and changing nothing is a documented pattern, and plaintiffs’ firms track it.

European Union — the European Accessibility Act. Since 28 June 2025, the EAA requires e-commerce services offered to EU consumers — including ticket sales — to be accessible, with WCAG 2.1 AA (via the EN 301 549 standard) as the practical technical benchmark. It applies regardless of where your business is headquartered if you sell to EU consumers. Microenterprises (under 10 employees and under €2 million turnover) providing services are exempt, and some pre-existing service contracts have transition time until 2030, but new services launched today are in scope now. Member states set their own penalties, which must be “effective, proportionate and dissuasive.”

The revenue case: the customers you never hear from

The WHO estimates 1.3 billion people — about 16% of the global population — live with significant disability. The best public data on what inaccessibility costs sellers comes from the UK’s Click-Away Pound survey (2019, the most recent edition): 69% of disabled online consumers simply click away from a site they find hard to use, an estimated £17.1 billion in abandoned UK spending, and — the figure that should worry organizers most — only 8% of users who hit a barrier ever tell the site owner. Your analytics will show these visitors as ordinary abandonment. The same survey found 86% of respondents would rather pay more on an accessible site than less on an inaccessible one, which for ticketing means accessible competitors quietly absorb your would-be buyers.

Accessibility failures also compound the ordinary drop-off we documented in our ticketing cart-abandonment analysis — an unlabeled field or an unreachable button is simply another reason to abandon, stacked on top of the usual ones.

Where ticket purchases break: a step-by-step WCAG map

Below we map each stage of a typical ticket purchase to the failure modes most likely at that stage and the WCAG success criteria that govern them, including the criteria added in WCAG 2.2 (published October 2023) that are particularly relevant to checkout flows.

Three of the criteria above are new in WCAG 2.2 and read like they were written with checkout in mind: Target Size (interactive controls at least 24×24 CSS pixels — think quantity steppers on a phone), Redundant Entry (don’t make buyers re-type information within the same session), and Accessible Authentication (no cognitive puzzles as the only way to log in and retrieve tickets).

What this means for self-hosted WordPress ticketing

Here the architecture question matters, as it did in our self-hosted vs SaaS capability matrix. With a SaaS widget or iframe embed, the checkout markup belongs to the vendor: if their seat map traps keyboard focus or their button has no accessible name, you cannot fix it — yet under the EAA, you are still the service provider selling to the consumer.

On a self-hosted stack, accessibility is in your hands — which is both the opportunity and the obligation. With Venuera, tickets are ordinary WooCommerce products, so buyers go through the native WooCommerce checkout your theme renders; accessibility fixes made once at theme level apply to your whole store, and WooCommerce’s own long-running accessibility work on core checkout carries over. The Custom Attendee Fields add-on outputs its per-attendee inputs as standard form fields with programmatic <label for> elements rather than placeholder-only inputs. Structured event data (Schema.org Event markup, covered in our event schema guide) also helps assistive-technology users and search engines alike understand what, when, and where the event is. None of that makes a site automatically conformant — your theme’s contrast, focus styles, and heading structure still decide most of the WebAIM-style failures — but it means nothing is locked inside a third-party iframe you can’t repair.

Sources & methodology

This analysis synthesizes public datasets rather than presenting new primary research: the WebAIM Million 2026 (automated WAVE evaluation of 1,000,000 home pages; automated tooling detects only a subset of WCAG failures), UsableNet’s 2025 lawsuit reporting (manual review of US federal and state filings), the Click-Away Pound survey (UK consumer survey, 2019 edition — dated but still the best public estimate of accessibility-driven abandonment), the WHO disability fact sheet, and the normative WCAG 2.2 recommendation. The purchase-stage mapping in the table is our editorial analysis of which success criteria most commonly fail at each step, based on the failure categories WebAIM reports. Legal figures change; check the primary sources before relying on them for compliance decisions.

Frequently asked questions

Does WCAG legally apply to my ticketing website?

WCAG itself is a technical standard, not a law, but laws point to it. In the EU, the European Accessibility Act has applied to e-commerce services (including ticket sales) since 28 June 2025, with WCAG 2.1 AA as the practical benchmark. In the US, courts and DOJ settlements consistently use WCAG as the reference standard in ADA web cases. If you sell tickets to EU consumers, the EAA can apply even if your business is based elsewhere.

What did WCAG 2.2 change for ticket checkouts?

WCAG 2.2 (October 2023) added criteria that map directly onto checkout flows: minimum 24×24 CSS pixel target sizes for controls like quantity steppers, a ban on forcing users to re-enter information within the same process (Redundant Entry), and Accessible Authentication, which prohibits making a cognitive puzzle the only way to log in.

Is passing an automated accessibility checker enough?

No. Automated tools such as WAVE or Lighthouse detect only a subset of WCAG failures — mostly markup-level issues like missing labels, alt text, and low contrast. Keyboard operability of seat maps, focus order, and screen-reader usability of dynamic ticket selectors need manual testing. A clean automated scan is a floor, not proof of conformance.

Are small event organizers exempt from the European Accessibility Act?

Only microenterprises — service providers with fewer than 10 employees and under €2 million annual turnover — are exempt from the EAA’s service requirements. Larger small and medium businesses must comply, and some pre-existing service contracts have transition time until 2030. National rules vary, so verify with the enforcement authority in the member states you sell into.