Accessibility is usually presented to e-commerce teams as a compliance obligation, which is accurate and also the least persuasive framing available. The more useful framing: an inaccessible checkout is a broken checkout, and broken checkouts lose money from every customer segment.
An estimated 2.3 billion dollars in annual online revenue is lost to inaccessible checkouts. Around 71 percent of users with disabilities abandon an inaccessible e-commerce site immediately rather than persisting. And the fixes that serve them - clearer labels, larger targets, fewer redundant steps - reduce friction for everyone.
What Changed: 2.1 to 2.2
The baseline expectation moved from WCAG 2.1 to WCAG 2.2, and several of the new criteria land directly on transactional flows. Combined with ADA litigation in the United States and European Accessibility Act enforcement, this stopped being theoretical for anyone selling online.
Redundant Entry
If a user has already provided information during a process, do not make them enter it again. Asking for a shipping address and then requiring the identical billing address to be typed a second time now fails.
Provide the information automatically, or offer it for selection. The "same as shipping" checkbox has quietly gone from courtesy to requirement, and it lifts completion rates independently of compliance.
Target Size (Minimum)
Interactive targets must be at least 24 by 24 CSS pixels, or have adequate spacing around them. In practice this means Add to Cart, size and variant selectors, quantity steppers, pagination and carousel arrows all need to be comfortably tappable.
This is the criterion most retail sites fail, and the failure is concentrated on mobile, which is where most of the traffic is.
Focus Not Obscured
When a control receives keyboard focus, it must not be hidden behind sticky headers, floating bars or cookie banners. Sticky elements plus keyboard navigation is a very common and completely invisible failure, because the people who build the site use a mouse.
Accessible Authentication
Do not require a cognitive test - remembering, transcribing or solving a puzzle - as the only way to authenticate. Password managers must be allowed to work. Blocking paste into a password field now fails, as it always should have.
Where Checkouts Break in Practice
Beyond the specific criteria, a handful of patterns cause most real failures:
- Placeholder text as the only label. The label vanishes the moment the user types, and screen readers treat placeholders inconsistently. Use a real
<label>. - Errors signalled by colour alone. A red border communicates nothing to a screen reader and little to a colour blind user. Errors need text, association with the field, and announcement.
- Custom dropdowns without keyboard support. Styled variant selectors built from divs are frequently unreachable by keyboard entirely.
- Focus lost on step change. Multi-step checkouts that do not move focus to the new step leave keyboard and screen reader users stranded at the bottom of the previous one.
- Timeouts without warning. Sessions that expire silently, discarding a filled cart, fail the criteria and infuriate everyone.
- Inaccessible payment iframes. Third-party payment fields are still your responsibility. Test them, and choose providers that take this seriously.
The Conversion Case
WCAG 2.2 AA compliance has been associated with reductions in checkout abandonment in the range of 23 to 35 percent, attributed to clearer navigation and lower cognitive load.
The mechanism is not mysterious. Larger tap targets reduce mis-taps for people with large fingers, in motion, or on a cracked screen. Explicit labels reduce confusion for everyone. Not retyping an address saves time for every customer. Errors that explain themselves get corrected instead of abandoned.
Accessibility work is user experience work with a compliance floor attached.
How to Test Properly
Three approaches, and you need all three, because each catches what the others miss.
- Automated scanning using axe, Lighthouse or WAVE. Fast, repeatable, and catches roughly a third of issues. Anyone claiming full coverage from automation alone is mistaken.
- Manual testing. Complete a purchase using only the keyboard. Then complete one with a screen reader running. This finds the majority of real problems and requires no budget, only patience.
- Expert evaluation and user testing with people who actually use assistive technology. This catches the issues that are technically conformant and practically unusable.
Where to Start
Fix the checkout path first. It is where failure is most expensive and where the legal exposure concentrates. Product page, cart, checkout, confirmation - in that order.
Then work outward to filters, variant selectors and image galleries, which are the next most common sources of blocking issues. For the design-side view of the same standard, see our guide to WCAG 2.2 for designers.
