State of Ecommerce Accessibility 2026 (Website)
A study of nearly 60,000 product pages shows that 96% fail at least one automated accessibility check, with critical failures affecting 64% of pages.
Deep dive
- 59,400 product pages were analyzed across Shopify and WooCommerce.
- 96% of pages failed at least one WCAG A or AA automated check.
- 64% contained at least one 'critical' impact failure as defined by axe-core.
- High-traffic sites were slightly more likely to have critical failures (69% for top 100k sites vs 63% for lower tiers).
- 80% of pages suffer from poor text contrast.
- 53% have links missing accessible names.
- 49% have illogical heading orders.
- Accessibility overlays show no significant statistical improvement in critical failure rates.
Decoder
- axe-core: An open-source accessibility testing engine that automates WCAG compliance checks.
- WCAG: Web Content Accessibility Guidelines, the internationally recognized standard for web accessibility.
- Screen Reader: Assistive technology that reads digital text aloud for users with visual impairments.
- Tap Target: The clickable or touchable area of a button or link.
Original article
The problem
64% of product pages tested had at least one critical accessibility issue.
This year, 39,976 Shopify and 19,424 WooCommerce product pages from stores ranked among the world’s top one million websites were scanned. On 37,874 of them, at least one issue in the highest potential-impact category was discovered.
On a product page, that could mean a customer cannot read important information, use a form or select a buying option.
Critical findings are only part of the picture though. 96% of product pages failed at least one automated accessibility check.
These are not just technical faults. They can stop customers using a product page. In the UK alone, an estimated £17 billion in online spending does not happen each year because people find websites difficult or impossible to use. A customer may use a screen reader, enlarge the page or navigate with a keyboard. And when your product page breaks, they generally don't complain or email you. They just leave and buy from somewhere they can actually use (your accessible competitor, perhaps?).
Understanding the headline
What a critical finding can mean for your customers
Critical is the highest potential-impact rating.
For your customer, a critical finding could make important product information, a form field or option impossible to use. The report identifies the barriers with the highest potential impact and shows how common they are across product pages.
64% of the product pages tested contained at least one critical finding.
Shopify and WooCommerce have both invested significantly in accessibility, particularly in checkout and the parts of the buying journey they directly control.
However, your product page is built from platform code, a theme, apps and plugins, agency or developer work and the store's own content.
Any of those layers can introduce a barrier.
That's why accessibility needs an owner inside the business. Someone needs to find where a problem sits, assign it to the right team or supplier and make sure it gets fixed.
By popularity
More traffic did not mean better accessibility
Product pages from the most popular stores were (marginally) worse-performing.
Among stores ranked between 500,000 and one million, 63% of product pages had a critical accessibility failure. Among stores in the top 100,000, that rose to 69%.
A high-traffic store puts every unresolved accessibility barrier in front of a larger audience. Accessibility needs the same ongoing attention as conversion, performance and security.
What fails most
The accessibility problems found most often
Poor colour contrast was the standout problem. It appeared on 80% of the product pages tested.
| What the problem is | Why it's a problem | Share of pages |
|---|---|---|
| Text does not stand out enough from its background | It can be difficult to read, particularly for people with low vision. | 80% |
| Links do not have a useful name | A screen reader may announce a link without explaining what it does or where it goes. | 53% |
| Heading levels are out of order | The page structure is harder to follow when someone navigates by headings. | 49% |
| Tap targets are too small or too close together | Buttons and links are harder to select accurately on a touchscreen. | 32% |
| A button, link or field has a different name for assistive technology | People using voice commands may say the words they can see and still be unable to activate it. | 28% |
| Images are missing alternative text | A screen reader cannot communicate the image’s content or purpose. | 27% |
Rule-level results
Across the product pages tested, 52 axe-core rules identified at least one failure. The table below shows the 14 that appeared most often.
| Rule ID | What it checks | Product pages | Share | Standard | Impact |
|---|---|---|---|---|---|
| color-contrast | Text is too faint to read against its background | 47,479 | 79.9% | 1.4.3 WCAG 2.0, Level AA | Serious |
| link-name | A link has no text a screen reader can announce | 31,636 | 53.3% | 4.1.2 WCAG 2.0, Level A | Serious |
| heading-order | Headings skip a level, so the outline is wrong | 28,948 | 48.7% | Best practice | Moderate |
| target-size | A tap target is smaller than a fingertip | 18,790 | 31.6% | 2.5.8 WCAG 2.2, Level AA | Serious |
| label-content-name-mismatch | A visible label does not match its accessible name | 16,598 | 27.9% | Best practice | Serious |
| image-alt | An image carries no alternative text | 16,107 | 27.1% | 1.1.1 WCAG 2.0, Level A | Critical |
| button-name | A button has no name, so it cannot be announced | 12,232 | 20.6% | 4.1.2 WCAG 2.0, Level A | Critical |
| meta-viewport | Pinch-zoom is switched off | 12,184 | 20.5% | 1.4.4 WCAG 2.0, Level AA | Critical |
| label | A form field has no label | 8,060 | 13.6% | 4.1.2 WCAG 2.0, Level A | Critical |
| landmark-one-main | The page has no main landmark | 5,293 | 8.9% | Best practice | Moderate |
| list | A list contains something that is not a list item | 4,923 | 8.3% | 1.3.1 WCAG 2.0, Level A | Serious |
| aria-hidden-focus | Focusable content is hidden from assistive technology | 4,793 | 8.1% | 4.1.2 WCAG 2.0, Level A | Serious |
| aria-allowed-attr | An ARIA attribute is not allowed on that element | 4,680 | 7.9% | 4.1.2 WCAG 2.0, Level A | Critical |
| link-in-text-block | A link relies on colour alone to stand out from surrounding text | 4,037 | 6.8% | 1.4.1 WCAG 2.0, Level A | Serious |
Overlays
Accessibility overlays fix... nothing.
Accessibility overlays are often sold as a quick way to make a website accessible. The appeal is obvious: one product promises to take a complicated problem off your hands. However, 62% of the 1,691 product pages where an accessibility overlay widget was detected still had at least one critical accessibility failure.
Installing an overlay is not proof that the accessibility work is done.
What to do next
Start with these six checks on your own product pages
-
Make text easier to read
Increase the contrast between text and its background.
-
Give every link a useful name
Use link text that explains where the link goes or what it does.
-
Keep headings in a logical order
Build a clear page structure without skipping heading levels.
-
Make tap targets easier to select
Give buttons and links enough space to be selected accurately on a touchscreen.
-
Use the same name on screen and behind the scenes
Use the same wording visually and in the name exposed to assistive technology.
-
Add useful alternative text to images
Describe an image’s relevant content or purpose when it cannot be seen.
Bonus: AI and shopping
The same page structure that helps your customers shop also helps search engines and machines understand your products too. Clear headings, useful image descriptions and properly built, labelled form fields help your customers find product information, navigate by keyboard or shop with a screen reader. Those same elements also tell search crawlers and AI assistants what the product is, which options are available and what each button, link and field does.
Method
The research covers 59,400 product pages, all tested using one consistent process. One product page was selected per Shopify or WooCommerce store in HTTP Archive's global top-million website dataset. Every page included in the report received the same mobile Lighthouse accessibility audit through Google PageSpeed Insights.
Who built this report
I’m Dave. I’m a Web Accessibility Specialist, and I built this report to show store owners which accessibility problems appear most often on product pages.
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi