Ecommerce accessibility means building a store that people with disabilities can browse and buy from, measured against the W3C's Web Content Accessibility Guidelines (WCAG) at level AA.
It pays off in two ways: it lowers legal risk in the US and EU, and several of its core fixes (bigger text, larger tap targets, clearer contrast) have won real A/B tests in our database, with lifts of roughly 2-7% in revenue per visitor.
Not every accessibility fix will show up in an A/B test, though, so don't make conversion lift the only reason you do the work.
This page covers what WCAG asks of a store, what our tests show about accessibility and conversion rate, and which fixes to start with.
Every test cited is from the LiftArchive test database and credited to whoever ran it.
WCAG for ecommerce: what the standard asks of a store
WCAG is published by the W3C. The current version, WCAG 2.2, groups its success criteria into levels A, AA and AAA.
Level AA is the target most laws and audits point to.
Most store templates trip over a short list of criteria again and again.
These are the ones that matter most on product, cart and checkout pages:
| WCAG criterion | Level | What it requires | Where stores fail it |
|---|---|---|---|
| 1.4.3 Contrast (Minimum) | AA | Text contrast of at least 4.5:1, or 3:1 for large text | Light gray body copy, white text on pastel buttons, sale badges |
| 1.4.4 Resize Text | AA | Text can be zoomed to 200% without losing content or functions | Fixed-height buy boxes and drawers that cut off zoomed text |
| 2.5.8 Target Size (Minimum) | AA | Pointer targets at least 24 by 24 CSS pixels (with exceptions for spacing and inline links) | Variant swatches, quantity steppers, mobile menu links |
| 1.1.1 Non-text Content | A | Text alternatives for meaningful images | Product photos and icon-only buttons with no alt text or label |
| 3.3.2 Labels or Instructions | A | Labels or instructions when content needs user input | Checkout and newsletter fields that rely on placeholder text alone |
The contrast and resize rules come straight from the WCAG 2.2 specification.
The 24-pixel target rule is explained in the W3C's Understanding 2.5.8 note, which also suggests aiming higher for important controls.
How far most sites are from AA
The WebAIM Million 2026 report ran automated checks on the home pages of the top one million websites.
It found detectable WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page.
The most common failures were low-contrast text (83.9% of home pages), missing image alt text (53.1%), missing form input labels (51%), empty links (46.3%) and empty buttons (30.6%).
Those are the same problems in the table above, and most of them can be fixed in a theme file.
Why stores face the most legal risk
In the EU, the European Accessibility Act (Directive 2019/882) applies to ecommerce services provided to consumers after 28 June 2025. Microenterprises that provide services are exempt.
The Act defines a microenterprise as one with fewer than 10 staff and annual turnover or balance sheet of no more than EUR 2 million.
The European Commission lists ecommerce among the covered services, and each member state enforces it through its own national law.
In the US, private lawsuits under the ADA are the main pressure.
UsableNet's 2025 midyear lawsuit report counted 2,019 digital accessibility filings in the first half of 2025. Ecommerce made up 69% of them.
One shortcut to avoid is relying only on an overlay widget.
In 2025 the FTC ordered accessiBe to pay $1 million over claims that its AI plug-in could make any website WCAG-compliant.
The final order bars the company from making that claim unless it has evidence to back it up.
Accessibility and conversion rate: what our tests show
We don't have a test in the database labeled "made the site WCAG AA compliant."
We do have tests of single changes that line up with WCAG criteria, and the readability tests are the most consistent group.
Bigger text keeps winning
Dave Diederen has run font-size tests on several stores, and all three in our database won:
- Making fonts 5% bigger sitewide lifted conversion rate 5.41% and revenue per visitor 6.91%, with AOV up 1.42%.
- A +4px font size on the product page for an older audience lifted revenue per visitor 4.17%, conversion rate 1.71% and AOV 2.41%.
- A sitewide test of +2px and +4px variants for an older audience lifted revenue per visitor 3.82% and conversion rate 2.12%.
Kasper Dolk reports the same pattern with a 2px increase in body font size, which boosted conversion for some brands, though no figures were published.
Dave Diederen's notes on these tests point to the same cause: small, low-contrast body copy is tiring to read on a phone, especially for older shoppers.
That is the problem WCAG's contrast and resize criteria are written to prevent.
These tests skew toward stores with older customers.
CDC data shows more than 1 in 4 US adults have some type of disability, including 5.5% with a vision disability and 13.9% with a cognition disability.
So the group that benefits from readable pages is large, not a niche.
Larger tap targets and clearer controls
Oliver Kenyon's team found in user testing that shoppers struggled with small, hard-to-tap mobile menu categories.
Their full-screen mobile mega menu with larger tap targets was forecast to add $50,568 per month, or $606,816 per year, with lower bounce rates. That fits the aim of WCAG 2.5.8.
Search controls tell a similar story. A larger mobile search bar at Safety Gear Pro, from a VWO case study, raised purchases 8.33%, though no significance was reported.
At Azuna, Blend Commerce found that clearer mobile search placeholder copy lifted revenue per visitor 3%.
Clearer text for an input is in the spirit of WCAG 3.3.2, but placeholder text alone doesn't meet it, so keep a visible label too.
Captions and contrast
Kasper Dolk lists adding captions to UGC videos as a proven winner for clients, without figures.
Captions are a WCAG requirement for prerecorded video, and they also help the many shoppers who watch with the sound off.
Blend Commerce's Aquarium Co-Op redesign moved to a faster theme with a more accessible color palette (black text on yellow).
Conversion rate rose 18% and store revenue 144%.
Treat that one with care: it was a quarter-over-quarter before-and-after comparison, sessions rose 73% in the same period, and speed, layout and color all changed at once.
@oliverkenyon
@DaveDiederen@DaveDiederen@DaveDiederen
Blend CommerceWhat the tests don't show
Most screen reader and keyboard fixes, such as alt text, focus order, form labels and button names, never appear in A/B test results.
Screen reader users are a small share of traffic, so a test powered on total visitors can't detect what happens to them.
A flat result does not mean the fix had no value.
Bigger is also not always better. Clean Commit's larger product images in a desktop grid showed +11.9% conversion rate but was not conclusive.
Our best practices that failed page collects more cases where an obvious usability fix didn't move sales.
Website accessibility conversion: where to start
The useful overlap is the set of fixes that both close WCAG gaps and have test evidence behind them.
Start there, then do the compliance-only work as a normal part of development, not as a test.
Fixes worth A/B testing
- Body text size. Test +2px and +4px variants against control, as Dave Diederen did. Check mobile body copy first.
- Text contrast. Darken gray body copy and low-contrast badges until they pass 4.5:1. This is the most common WCAG failure, so most stores have something to fix.
- Tap targets. Enlarge variant swatches, steppers and menu links to at least 24 by 24 CSS pixels, with more room for primary controls. See our navigation menu tests and the mobile CRO guide.
- Search and form inputs. Visible labels, clearer placeholder copy and larger fields.
- Video captions. Low effort, and required anyway.
Fixes to ship without a test
Alt text, form labels, button names, keyboard access, visible focus states and correct heading order should simply be built in.
They are cheap, they cut legal exposure and they rarely hurt anything.
Test them with a screen reader and keyboard, not a split test.
How to find the problems
Automated scanners catch the obvious failures (contrast, missing labels, empty buttons), but they miss a lot.
Pair a scan with a manual pass: keyboard-only checkout, 200% zoom, and a screen reader run through product and cart pages.
Usability testing with older shoppers or shoppers with disabilities will turn up problems no scanner finds.
For the wider picture, see our ecommerce UX guide and the CRO hub.
If you'd rather have a practitioner run this, our UX audit services directory lists agencies that audit and test stores.