What the WebAIM Million 2026 Report Shows About E-Commerce Site Accessibility
Quick answer: Every February, WebAIM runs an automated accessibility scan of the home pages of the top one million websites and publishes the results as “The WebAIM Million.” The 2026 edition — its eighth consecutive year — found an average of 56.1 detectable accessibility errors per home page, and 95.9% of home pages had at least one. E-commerce sites specifically did worse than that already-bad average: the report’s “Shopping” category averaged 71.0 errors per page (26.6% above the overall average), and every named e-commerce platform it tracked — Shopify, Magento, and PrestaShop — scored worse than the sample average too. Six error types account for 96% of everything detected, and all six map directly onto fixes covered elsewhere on this site.
This article is general accessibility information, not legal advice. It summarizes a third-party research report; it isn’t an evaluation of any specific website, and meeting or beating an average error count doesn’t establish legal compliance with the ADA, WCAG, or any other standard.
What the WebAIM Million actually measures
WebAIM built its home-page list from the Tranco ranking, which combines several “top sites” sources, then scanned each one with its own WAVE stand-alone API. The report is explicit about what that can and can’t tell you: “All automated tools, including WAVE, have limitations — not all conformance failures can be automatically detected. Absence of detected errors does not indicate that a page is accessible or conformant.” That’s the same structural limit covered in more depth in our piece on what automated scanners miss — WAVE, like axe-core or Lighthouse, can confirm a lot of markup problems but can’t watch a person actually try to complete a purchase with a keyboard or a screen reader. Keep that in mind: every number below almost certainly understates real-world accessibility problems, because it only counts what a machine can see on a single, unauthenticated home page — not a product page, not a cart, and definitely not a checkout flow.
With that caveat, the scale here is still useful context. Across the one million pages, WebAIM detected 56,114,377 distinct errors — up 10.1% from 51 per page in 2025, reversing several years of small, steady improvement. 95.9% of home pages had at least one detected WCAG 2 failure, meaning the report’s own reading is that full automated-and-manual conformance was “certainly lower than 4.1%” even before anyone opens a screen reader.
E-commerce sites scored worse than the average
The report breaks results out by site category and, separately, by the specific platform a site runs on. Both cuts point the same direction for online stores:
- “Shopping” as a category: 95,039 home pages, averaging 71.0 errors — 26.6% worse than the 56.1-error sample average, and one of the more error-prone categories the report tracks (ahead of categories like Business, Technology, and Education, which all did better than average).
- Shopify: 42,516 home pages, averaging 75.1 errors — 33.9% worse than average.
- Magento: 7,996 home pages, averaging 75.8 errors — 35.0% worse than average.
- PrestaShop: 5,044 home pages, averaging 143.2 errors — 155.3% worse than average, and by far the worst-performing platform WebAIM named.
WebAIM is careful to note that “correspondence of additional errors with a technology cannot always be attributed to that technology” — a Shopify store’s theme, apps, and page complexity all contribute, not the platform alone. But directionally, the pattern is consistent: three separate e-commerce platforms, tracked independently, all landed on the worse side of the average, and the Shopping category as a whole did too. If you sell online, the average site in your own category is measurably behind the average website generally, not ahead of it.
Six issues cause 96% of everything detected
The report’s most actionable finding isn’t the averages — it’s that a small, stable list of failure types accounts for nearly all the errors it found, and has for years:
| WCAG failure type | % of home pages affected |
|---|---|
| Low contrast text | 83.9% |
| Missing alternative text for images | 53.1% |
| Missing form input labels | 51% |
| Empty links | 46.3% |
| Empty buttons | 30.6% |
| Missing document language | 13.5% |
As WebAIM puts it: “These most common errors have been the same for the last 7 years. Addressing just these few types of issues would significantly improve accessibility across the web.” Translated into e-commerce-specific fixes, each one has a dedicated guide already on this site:
- Low contrast text (the single most common failure, with an average of 34 distinct instances per page) usually shows up on sale badges, disabled-looking button states, and text laid over hero-banner photos. See our contrast ratio guide for the actual numbers and where automated tools stop being able to compute them.
- Missing alt text and empty links are more connected than the table above suggests — the report found 45% of images missing alt text were themselves linked images, meaning a shopper tabbing through the page hits a link with no announced destination at all. See writing alt text that passes a manual review.
- Missing form labels shows up constantly in checkout and account forms. See form labels and error messages.
- Empty buttons — a button with no accessible name at all — is the icon-only wishlist heart, cart-remove ×, or carousel arrow with nothing behind it for a screen reader to announce. See making wishlist buttons accessible for the specific fix.
- Missing document language is a one-line
langattribute fix, covered in our page-language guide.
None of these six require a redesign. They’re the accessibility equivalent of low-hanging fruit — which is exactly why the same six issues have topped this report for seven straight years running.
What this data doesn’t tell you
A home page scoring well on WAVE doesn’t mean the store behind it is accessible, and a home page scoring poorly doesn’t automatically mean checkout is worse — or better. This report only looked at one page per site, using only automated detection, and every category and platform figure above is an average across tens of thousands of very different sites. Your specific store could be well above or well below its platform’s average either way. What the report is genuinely useful for is priority-setting: if you haven’t looked at your site’s accessibility at all yet, contrast, alt text, form labels, and unlabeled buttons are demonstrably where most sites’ problems actually live — start there before chasing rarer issues.
FAQ
Does this mean Shopify (or Magento, or PrestaShop) is inaccessible by default? No. The report measures the average home page built on each platform, not the platform’s templates or defaults in isolation. Theme choice, installed apps, and custom code all factor into an individual site’s error count. A well-built store on any of these platforms can score far below its platform’s average; a heavily customized one can score far above it.
Is a WAVE scan the same thing as a Quietramp audit? No. WAVE and axe-core are both automated scanners with the same structural limitation described above — they flag pattern-level markup problems but can’t determine whether a real person can actually complete a purchase using a keyboard or screen reader. That gap is exactly what the manual review portion of an audit is for.
Get a human-reviewed audit, not just a scan
An automated scan like the one behind this report is a legitimate first signal, not a full answer — even WebAIM says so about its own tool. Quietramp’s audits pair the same kind of automated scan with a manual review of keyboard flow, screen-reader semantics, and the checkout/cart flow this report never touches, delivered as a prioritized, developer-actionable PDF report. See a real sample report or check pricing — $890 one-time, $99/month for ongoing re-checks after fixes ship.
This article is general accessibility information, not legal advice. Meeting WCAG 2.1 AA does not resolve ADA or any other legal compliance question, and nothing here should be read as a compliance guarantee. Consult qualified counsel for legal risk questions.
This article was drafted with AI assistance and reviewed by a person for accuracy before publication.