Shopify Accessibility Index 2026: 100% of Stores We Scanned Failed WCAG

Every one of the 71 live Shopify storefronts we analyzed failed WCAG 2.1/2.2 AA, and 91.5% carried at least one critical-severity violation. The average store had 1,608 accessibility issues, the median had 826, and the worst single store had 22,090. Across the sample we counted 114,158 violations. This is the 2026 Shopify Accessibility Index: an analysis of 71 real US Shopify stores, scanned with the same Playwright + axe-core engine that powers the AccessComply app. It is a starting baseline we will expand, and the headline is already blunt. Most Shopify stores are not close to compliant, and the overlay widgets many install do not fix the underlying theme code.

Key findings: the 2026 Shopify Accessibility Index in 10 stats

Every stat below comes from our analysis of 71 distinct live Shopify storefronts, scanned with Playwright + axe-core against WCAG 2.1 and 2.2, Levels A and AA. Numbers are reported exactly as measured, with no rounding up.

• 100% of the 71 Shopify stores we analyzed failed WCAG 2.1/2.2 AA. Not one store passed clean.
• 91.5% of stores had at least one critical-severity violation, the kind that blocks a screen-reader or keyboard user outright.
• The average store had 1,607.9 violations. Accessibility debt on Shopify is measured in the thousands, not the dozens.
• The median store had 826 violations, so even the typical store, not just the outliers, is deep in non-conformance.
• We counted 114,158 total violations across the 71 stores.
• The worst single store had 22,090 violations on the pages we scanned.
• 53.5% of stores ship images with no alt text (WCAG 1.1.1), the single most common failure.
• 39.4% of stores run videos with no captions (WCAG 1.2.2), a requirement the EAA names explicitly.
• 30 of 71 stores (42%) had more than 1,000 violations each. Only 6 stores came in under 50.
• 0 stores in the sample relied on accessibility that an overlay widget alone could deliver. Every violation we found lives in theme source code, where overlays cannot reach.

Honest framing: this is a small, deliberately selected sample of mostly US direct-to-consumer brands, not a census of all Shopify. The point is not that these 71 represent every store. The point is that when you actually scan real, live, mid-size Shopify stores, the failure rate is total and the violation counts are enormous.

Why this matters in 2026: the ADA and EAA double deadline

Accessibility moved from best-practice to legal exposure on two continents at once, and ecommerce is the primary target. In the United States there were 3,117 federal ADA website lawsuits filed in 2025, up about 27% year over year (Seyfarth Shaw, adatitleiii.com). The large majority of these target ecommerce, and Shopify is reported as the most-sued ecommerce platform, appearing in roughly a third of cases. A merchant does not need to be large to be sued. Most demand letters and filings target small and mid-size stores precisely because they are unlikely to have remediated.

In the European Union, the European Accessibility Act (EAA) has been enforceable since 28 June 2025. It requires consumer-facing ecommerce to meet accessibility standards aligned with WCAG, and national regulators can impose penalties. In Germany, fines under the implementing law can reach up to EUR 100,000 per violation, and broader EU-member enforcement frameworks contemplate penalties up to the multi-million-euro range. German Abmahnung warning letters and French injunctions tied to accessibility are already on record.

The takeaway, stated plainly: if you sell to US or EU consumers from a Shopify store, an automated scanner can already find dozens to thousands of violations on your storefront, and those same violations are what plaintiffs' firms and EU regulators look for. This report does not promise that fixing them stops a lawsuit. It does show, with first-party data, how exposed the typical store is right now.

Methodology: how we analyzed 71 Shopify stores

We analyzed 71 distinct live Shopify storefronts, deduplicated by host. The stores were selected during AccessComply's June 2026 cold-outreach campaign, drawn from three already-collected scan sources rather than from any new scanning run, because the production scanner is shared with paying merchants. For each distinct scan we made one read-only request to the AccessComply scan API and read three authoritative fields: total_violations, critical_count, and the per-store rule summary.

Engine. Playwright drives a real Chromium browser and runs axe-core against each storefront, evaluating WCAG 2.1 and 2.2 at Levels A and AA. This is the same engine that scans for AccessComply's paying merchants. All 71 scans returned a completed status with no errors, no 404s, and no failed exclusions.

What counts as a violation. Each violation is a distinct axe-core rule failure on a distinct element. critical_count is the count of critical-impact failures as classified by the scan engine.

Honest caveats, stated up front because they matter:

1. Small, non-random sample. These 71 stores are mostly US direct-to-consumer apparel, food, and beverage brands selected for outreach. They skew toward mid-size catalog stores. Absolute violation counts here are not generalizable to all of Shopify. Treat this as a baseline we will expand, not a population census.
2. Per-rule totals are floors, not ceilings. The public scan response we read caps the rule summary at each store's top three rules. So our per-rule "stores affected" and "occurrence" figures only capture each store's three largest buckets and undercount rules that exist but rank lower on a given store. Contrast and tap-target issues in particular are almost certainly more widespread than the table shows. Per-store total_violations and critical_count are full figures and are not affected by this cap.
3. Automated scanning finds roughly 30 to 40% of WCAG success criteria. The absence of an automated error is not proof of accessibility. Manual testing with real assistive technology is still required for a full conformance claim. We report what an automated scan finds, which is a floor on the real problem, never a ceiling.

We publish these caveats because a report without them is marketing, not research.

The headline number: WCAG conformance across Shopify

100% of the 71 Shopify stores we analyzed had WCAG errors, and 91.5% had critical errors. For comparison, WebAIM's 2025 analysis of the top 1,000,000 home pages on the web found that 94.8% had detectable WCAG failures, averaging about 51 errors per page. Our Shopify sample is smaller and selected, but it ran clean past that bar: every store failed, and the average store carried far more than a single home page's worth of errors because we scanned multiple template types per store.

The two studies measure different units (whole stores across many templates vs single home pages), so the averages are not apples-to-apples. The directional conclusion holds either way: WCAG failure on Shopify storefronts is the norm, not the exception, and the per-store debt is large.

Violation volume distribution: how bad is the typical store

42% of the stores we scanned had more than 1,000 violations each, and only 8% came in under 50. The distribution below is the clearest single picture of the problem. The mass of stores sits in the high-violation buckets, which is why the average (1,608) sits well above the median (826): a handful of very large catalogs pull the average up, but even the middle of the pack is in deep non-conformance.

Read the bottom two rows together: 58 of 71 stores (81.7%) had more than 200 violations, and 30 of those had more than 1,000. A store owner who assumes "we are probably mostly fine" is, in this sample, almost always wrong.

The most common WCAG violations on Shopify stores

Missing alt text is the most common failure on Shopify, present on 53.5% of stores, followed by uncaptioned video (39.4%) and unnamed buttons (31%). The table below ranks every rule that surfaced in our analysis, with the plain-English meaning, the WCAG criterion and severity, and exactly how AccessComply fixes it in the theme source code rather than masking it.

Important: because the public scan response caps each store at its top three rules, the "stores affected" and "occurrences" columns are floors. Color contrast and target size in particular are near-certainly more widespread than shown.

The pattern across the top rules is consistent: most of the highest-frequency failures are Level A criticals (alt text, captions, button names, labels, select names), which are the most basic, most testable, and most litigated requirements in WCAG.

The overlay trap: why accessibility widgets do not fix this

Accessibility overlay widgets do not fix the violations in this report, because the violations live in theme source code and overlays only run a script on top of the rendered page. In January 2025 the US Federal Trade Commission settled with overlay vendor accessiBe for USD 1 million over deceptive claims that its automated widget could make any website WCAG and ADA compliant. Independent trackers have documented hundreds of websites that were running an accessibility overlay and were still named in ADA lawsuits, and legal-data firms have reported dozens of overlay-using defendants sued in a single month.

Here is the mechanism, in plain terms:

• An overlay is a JavaScript layer. It loads after the page and tries to patch the DOM at runtime: add an aria-label here, bump a contrast value there. It does not change your theme files.
• The underlying violations remain in your source. If a screen reader, a legal scanner, or a tester disables the widget or reads the raw markup, the missing alt text, unnamed buttons, and uncaptioned videos are all still there. That is exactly what plaintiffs' experts do.
• Overlays can introduce their own failures. Runtime DOM rewriting frequently conflicts with assistive technology and can break keyboard navigation, which is why many accessibility practitioners actively recommend against them.

AccessComply takes the opposite approach. It scans with axe-core, then its agents write real corrections into your theme's Liquid, HTML, and CSS via Shopify's theme files API. A full theme backup is taken before any change, the page is re-scanned after the fix to confirm the violation is actually gone, and the change is rolled back automatically if it causes a regression. The fix lives in your source code, so it survives with or without any widget running. We are not telling you AccessComply guarantees you cannot be sued. We are telling you the difference between masking a violation at runtime and removing it from the code, and that the FTC has already put a price on the difference.

Lawsuit risk by store profile

84.5% of the stores we analyzed fall into HIGH or CRITICAL lawsuit-risk tiers based on violation volume, leaving only about one in six at MEDIUM or LOW. AccessComply assigns a risk tier from the scan results: CRITICAL for stores with 50 or more violations or critical keyboard and navigation failures, HIGH for 25 to 49, MEDIUM for 10 to 24, and LOW for under 10. Because the median store in this sample had 826 violations, the great majority land at the top of the scale.

The distribution maps almost one-to-one onto the volume buckets: every one of the 58 stores with more than 200 violations is squarely CRITICAL, and the six stores under 50 violations are the only ones with any plausible claim to a lower tier. In legal-exposure terms, the typical store in this sample is not in a gray area.

What merchants should do, and what to avoid

If you run a Shopify store, the fastest way to know your exposure is to scan your storefront, then fix the violations in your theme code rather than masking them with a widget. Here is the vendor-neutral order of operations.

Step 1: Get a real violation count before you decide anything

You cannot prioritize what you have not measured. Run an automated WCAG 2.1/2.2 AA scan against your live storefront, including a product page, a collection page, and the cart, not just the home page. The number you get back is your floor.

Step 2: Fix the Level A criticals first

The highest-frequency, most-litigated failures are Level A: missing alt text, uncaptioned video, unnamed buttons, unlabeled form fields, unnamed selects. These block users outright and are the easiest for a legal scanner to find. Fix these before you touch anything cosmetic.

Step 3: Fix in source code, not in an overlay

Write the corrections into your theme's Liquid, HTML, and CSS, or use a tool that does. A fix in source survives a screen reader, a legal audit, and a disabled widget. A fix that only exists in a runtime overlay does not, and the FTC has already fined a vendor USD 1 million over claiming otherwise.

Step 4: Re-scan after every change and keep a backup

Confirm each fix actually removed the violation by re-scanning, and keep a backup of your theme before any automated change so you can roll back a regression. Accessibility work that is not verified is just hope.

Step 5: Treat this as continuous, not one-time

Every theme update, app install, and new product can reintroduce violations. Scan on a schedule, not once.

What to avoid

• Do not rely on an overlay widget as your compliance solution. It does not change your source code, hundreds of overlay-using sites have still been sued, and the FTC fined a leading vendor for the underlying claim.
• Do not scan only the home page. Product, collection, and cart templates carry most of the violations in this report.
• Do not treat an automated pass as full conformance. Automated tools catch 30 to 40% of WCAG criteria; manual assistive-technology testing is still required for a complete claim.

You can run step 1 right now, for free: scan your Shopify store at accesscomply.com and get your exact WCAG 2.1/2.2 AA violation count and risk tier in about a minute, no install required. When you want those violations fixed in your real theme code with backup, re-scan, and auto-rollback, AccessComply is on the Shopify App Store at apps.shopify.com/accesscomply.

Frequently asked questions

Are Shopify stores ADA and WCAG compliant by default?

No. In our analysis of 71 live Shopify storefronts, 100% failed WCAG 2.1/2.2 AA and 91.5% had critical violations. Shopify provides accessible building blocks, but the storefront a merchant actually ships, with its theme, apps, images, and content, is what gets scanned and litigated, and in this sample every one had errors.

What percentage of Shopify stores fail WCAG?

In this sample, 100% of the 71 stores we analyzed had WCAG 2.1/2.2 AA failures, and 91.5% had at least one critical-severity failure. The average store had 1,608 violations and the median had 826. This is a small, selected sample, so treat it as a baseline we will expand rather than a figure for all of Shopify.

Do accessibility overlay widgets prevent lawsuits?

There is no evidence they do, and significant evidence they do not. Overlays patch the page at runtime without changing your theme source code, hundreds of overlay-using sites have still been named in ADA lawsuits, and in 2025 the FTC fined overlay vendor accessiBe USD 1 million for deceptive compliance claims. The durable fix is to correct the violations in your source code.

What are the most common accessibility violations on Shopify?

Missing image alt text leads at 53.5% of stores, followed by missing video captions (39.4%), buttons with no accessible name (31%), low color contrast (23.9%), and unlabeled form fields (21.1%). The first three are Level A critical failures under WCAG.

Does the EAA apply to my Shopify store?

If you sell to consumers in the European Union, very likely yes. The European Accessibility Act has been enforceable since 28 June 2025 and covers consumer-facing ecommerce, with national penalties that in Germany can reach EUR 100,000 per violation. WCAG-aligned conformance is the practical standard.

How do I check my own store?

Run a free scan at accesscomply.com. You get a WCAG 2.1/2.2 AA report, your exact violation count, and a lawsuit-risk tier in about 60 seconds, with no install required.

Cite this report

This report is free to cite and republish with attribution. We will refresh it on a recurring cadence and expand the sample, while keeping this canonical URL stable so existing citations do not break.

How to cite: AccessComply. "Shopify Accessibility Index 2026: An Analysis of 71 Live Shopify Storefronts." accesscomply.com/shopify-accessibility-index. Published 2026.

Quick-reference facts (all from our analysis of 71 live Shopify storefronts):

• Sample: 71 distinct live Shopify storefronts, deduplicated by host, scanned with Playwright + axe-core against WCAG 2.1/2.2 Levels A and AA.
• 100% failed WCAG 2.1/2.2 AA.
• 91.5% had at least one critical violation.
• Average 1,607.9 violations per store; median 826; total 114,158 across the sample; worst single store 22,090.
• Most common failure: missing image alt text, on 53.5% of stores.

External sources referenced: Seyfarth Shaw / adatitleiii.com (3,117 US federal ADA website lawsuits in 2025, +27% YoY); WebAIM Million 2025 (94.8% of one million home pages had WCAG errors); US Federal Trade Commission (USD 1 million accessiBe settlement, 2025); European Accessibility Act (enforceable 28 June 2025).

A note on scope: the per-rule occurrence figures in this report are floors, because the underlying scan response we read caps each store at its top three rules. Per-store violation totals and critical counts are complete. Automated scanning detects roughly 30 to 40% of WCAG criteria, so all of these figures understate the true accessibility gap rather than overstate it.

For media questions or a custom cut of the data for your vertical, contact AccessComply via accesscomply.com.

Scan your own Shopify store

Scan your own Shopify store for free at accesscomply.com. You get a full WCAG 2.1/2.2 AA report and your exact violation count in about 60 seconds, no install required. If you want the violations fixed in your real theme code, AccessComply is on the Shopify App Store at apps.shopify.com/accesscomply.