Key takeaways
- Shopify gives you an accessible foundation, but your theme, content, and apps decide whether your store is actually ADA compliant.
- The legal standard nearly every case settles on is WCAG 2.2 AA, and building to it satisfies US, EU, UK, Canadian, and Australian rules at once.
- Accessibility lawsuits keep climbing: more than 4,000 ADA web cases were filed in the US in 2024, and roughly 1 in 4 named a site that already had an accessibility widget installed.
- Accessibility overlays do not make a store compliant. The fixes that hold up legally are changes to the underlying theme code.
- Most failures come from six recurring, fixable issues: low-contrast text, missing alt text, missing form labels, empty links, empty buttons, and a missing page language.
Accessibility is one of the few areas where doing the right thing and reducing legal risk are the same project. Roughly one in four adults has a disability, and an inaccessible store quietly turns away screen-reader users, keyboard-only users, low-vision shoppers, and colorblind customers. The fixes that let those people check out are the same ones courts and regulators reward.
This guide covers what Shopify ADA compliance actually means, which laws apply to your store, what WCAG 2.2 AA requires, and how to fix the issues at the source instead of papering over them.
Why you can trust us
Jacques has over 15 years of development experience and has helped many Shopify brands ship accessible, fast storefronts. We have been in the Shopify space for over four years and built Fudge, an AI store builder and editor with a 5.0 rating on the Shopify App Store. Our position on accessibility is the same as the consensus among accessibility engineers: fix the code, do not hide the problem behind a widget. We explain why throughout this guide.
Is Shopify ADA compliant?
Shopify the platform is not the thing that gets sued. Your store is.
Shopify provides an accessible starting point. Themes in the Shopify Theme Store must reach a minimum average Lighthouse accessibility score of 90 across tested page types, and the default Dawn theme ships with semantic HTML, skip links, and visible focus indicators.1 But a Lighthouse score of 90 is not the same as full WCAG conformance. Automated scoring only checks a fraction of the success criteria, so no theme is guaranteed to be WCAG 2.2 AA compliant out of the box.
What you add on top is where compliance is usually won or lost: custom sections, third-party apps, images without alt text, low-contrast brand colors, and content edits made over months by people who were not thinking about accessibility. Shopify gives you a platform. Your theme and content decide whether the store is compliant.
Who the law actually applies to
If you sell to the public online, accessibility law almost certainly applies to you. The volume of litigation makes that concrete.
More than 4,000 ADA-related digital accessibility lawsuits were filed in the US in 2024, and e-commerce and retail were the dominant target at roughly three-quarters of cases.2 Filings stayed high through 2025.3 These are not only large brands. Serial plaintiffs and a small number of law firms drive much of the volume, often starting with a demand letter that quietly settles for somewhere between $5,000 and $75,000 before it ever becomes a public case.
The uncomfortable detail for store owners: having an accessibility tool installed does not protect you. About 1 in 4 of the 2024 suits named a site that already had an accessibility widget or overlay running.2
The laws that govern store accessibility
There is no single global rule, but the regimes converge on the same technical standard.
United States: ADA Title III
US e-commerce sites are sued under Title III of the Americans with Disabilities Act, which courts treat as covering websites as “places of public accommodation.” There is no federal regulation that spells out the technical requirements for private business, so settlements and rulings use WCAG 2.x AA as the de facto benchmark.
State laws add financial teeth. California’s Unruh Civil Rights Act allows statutory damages of $4,000 per violation, and New York is consistently one of the highest-volume filing venues in the country.4
European Union: the European Accessibility Act
The European Accessibility Act (Directive 2019/882) became applicable on 28 June 2025. It explicitly covers e-commerce as a service, and it reaches sellers outside the EU who sell to EU consumers.5
The EAA points to the harmonized standard EN 301 549, which incorporates WCAG 2.1 AA for web content, and it requires a published accessibility statement. There is a micro-enterprise exemption for service providers with fewer than 10 employees and annual turnover or balance sheet at or below €2 million, though that exemption does not extend to product manufacturing or importing.5
Everywhere else
The UK Equality Act 2010, Canada’s provincial and federal accessibility regulations, and Australia’s Disability Discrimination Act all push toward WCAG AA. None of them conflict with building to WCAG 2.2 AA. Exceeding the requirement satisfies the older regimes automatically, which is why we recommend treating 2.2 AA as the single target.
The standard: what WCAG 2.2 AA requires
WCAG 2.2 became a W3C Recommendation in October 2023 and is the current version of the guidelines.6 Level AA is the conformance level used in legal settlements.
WCAG is organized around four principles, known by the acronym POUR:
- Perceivable. Users can perceive the content. Text alternatives for images, captions for video, sufficient color contrast.
- Operable. Users can operate the interface. Full keyboard access, visible focus, no keyboard traps, enough time to complete tasks.
- Understandable. Content and operation are predictable. Clear labels, consistent navigation, helpful error messages on forms.
- Robust. Content works with assistive technology. Valid, semantic HTML that screen readers can interpret.
For a store, the highest-stakes flow is the path from product page to completed checkout. If a keyboard or screen-reader user cannot finish a purchase, that is both lost revenue and the exact scenario plaintiffs target.
The six failures behind almost every complaint
You do not need to memorize all of WCAG to remove most of your risk. The annual WebAIM Million analysis of the top one million home pages found that 95.9% had detectable WCAG failures in its February 2026 report, averaging 56.1 errors per page.7
The striking part is how concentrated those errors are. Around 96% of all detected failures fall into six categories, and all six are machine-detectable and common:
| Failure | What it means | Typical Shopify cause |
|---|---|---|
| Low-contrast text | Text too faint against its background | Brand colors used for body or button text |
| Missing alt text | Images with no text alternative | Product and lifestyle images uploaded without alt |
| Missing form labels | Inputs with no programmatic label | Search, newsletter, and custom form fields |
| Empty links | Links with no discernible text | Icon-only links (cart, social) with no label |
| Empty buttons | Buttons with no discernible text | Icon-only buttons (menu, close) with no label |
| Missing page language | No lang attribute on the page | Custom or heavily edited themes |
These are the fastest wins because they are unambiguous and they appear on most stores. Fixing them is a theme-code change, not a setting you toggle.
Why accessibility overlays do not make you compliant
When store owners first learn about accessibility law, the tempting fix is an overlay: a single script from a vendor like accessiBe, UserWay, or AudioEye that promises to make your site compliant automatically. It does not work, and it can increase your risk.
An overlay is JavaScript layered on top of your existing HTML. It cannot rewrite the underlying problems, because automated tooling only detects and addresses a subset of WCAG issues. Independent testing puts automated coverage at roughly 30 to 40% of criteria, which leaves the majority untouched.
The accessibility community has been blunt about this. More than 1,000 accessibility professionals, including contributors to WCAG itself and engineers behind major screen readers, have signed the Overlay Fact Sheet stating that overlays are unreliable and cannot achieve compliance.8 The National Federation of the Blind has condemned them.
The legal record is just as clear. In 2025 the FTC finalized a $1,000,000 order against accessiBe for deceptively claiming its widget could make any website WCAG compliant.9 And as noted above, around a quarter of 2024’s ADA web lawsuits named sites that already had a widget installed.2 The overlay did not stop the suit.
We cover this in depth in our guide on why accessibility overlays fail. The short version: an overlay is a recurring cost that hides the problem instead of fixing it.
How to audit your Shopify store
A real audit has two layers, because automated tools alone are not enough.
Automated scan. Start with a free tool to catch the machine-detectable issues: axe DevTools, WAVE, or Lighthouse (built into Chrome). These will surface most of the six common failures quickly.
Manual pass. Because automated tools only catch a minority of WCAG issues, follow up with a manual check:
- Navigate the entire purchase flow using only the keyboard (Tab, Shift+Tab, Enter). Can you reach and use every control, including the cart and checkout?
- Turn on a screen reader (VoiceOver on Mac, the free NVDA on Windows) and try to complete a purchase.
- Zoom the page to 200% and confirm nothing is cut off or overlapping.
The combination of one automated scan and one manual pass will find the overwhelming majority of issues that matter.
How to fix accessibility the right way
Every durable fix is a change to your theme code. That is the part overlays skip and the part that actually satisfies the law.
Most fixes are straightforward once you know where they live:
- Add descriptive
alttext to product and content images. - Add accessible labels (
aria-labelor visible text) to icon-only buttons and links. - Associate every form input with a
<label>. - Adjust brand colors used for text until they meet the 4.5:1 contrast ratio for normal text.
- Set the
langattribute on the page. - Ensure focus states are visible and the keyboard order is logical.
This is where an AI store builder helps. Fudge reads your live theme, surfaces the accessibility issues in your code, fixes them directly in native Liquid, CSS, and JavaScript, and keeps the changes in your theme. Because the output is real code rather than an injected layer, it holds up the way a developer’s fix would, and there is no extra script slowing the page down. It also pairs naturally with related work like adding structured data and general store editing.
The model we recommend, and the one we built Fudge around, is three steps: surface what needs fixing, fix it at the source, and monitor for regressions so a future content edit does not quietly reintroduce a failure.
Publish an accessibility statement
Once the work is done, publish an accessibility statement. It is required under the EAA, expected under several other regimes, and it signals good faith if you ever receive a demand letter. State your target standard (WCAG 2.2 AA), how users can report problems, and how to contact you. Keep it honest and specific rather than boilerplate.
FAQ
No. Shopify provides an accessible foundation, and Theme Store themes must score at least 90 on Lighthouse accessibility, but that is not full WCAG conformance. Your theme, content, apps, and custom sections determine whether the store is actually compliant.
WCAG 2.2 Level AA. It is the current version of the guidelines and the level used in legal settlements. Building to 2.2 AA also satisfies the older standards referenced by US, EU, UK, Canadian, and Australian rules.
Yes. More than 4,000 ADA digital accessibility lawsuits were filed in the US in 2024, with e-commerce and retail the most common targets. Many start as demand letters that settle quietly. Having an accessibility widget installed does not prevent suits.
No. Overlays are JavaScript added on top of broken HTML and cannot fix most WCAG issues. The FTC fined accessiBe $1,000,000 in 2025 for claiming otherwise, and roughly a quarter of 2024 lawsuits named sites that had a widget installed. Fixing the theme code is what holds up.
It can. The EAA became applicable on 28 June 2025, covers e-commerce, and reaches non-EU sellers who sell to EU consumers. It references WCAG 2.1 AA via EN 301 549. There is a micro-enterprise exemption for service providers under 10 employees and at or below €2 million turnover.
Six failures account for about 96% of all detected errors: low-contrast text, missing image alt text, missing form labels, empty links, empty buttons, and a missing page language attribute. All six are fixable in theme code and appear on most stores.
Run an automated scan with a free tool like axe DevTools, WAVE, or Lighthouse, then do a manual pass: navigate checkout with only the keyboard, test it with a screen reader, and zoom to 200%. Automated tools catch only 30 to 40% of issues, so the manual step matters.
Footnotes
-
Shopify Theme Store accessibility requirements and best practices, shopify.com/partners/blog/theme-store-accessibility-requirements and shopify.dev/docs/storefronts/themes/best-practices/accessibility. ↩
-
UsableNet 2024 and 2025 digital accessibility lawsuit reports, usablenet.com. ↩ ↩2 ↩3
-
EcomBack 2025 ADA website accessibility lawsuit report, ecomback.com. ↩
-
California Unruh Civil Rights Act ($4,000 statutory minimum per violation); New York federal-court filing volume, adatitleiii.com. ↩
-
European Accessibility Act (Directive (EU) 2019/882), applicable 28 June 2025; EN 301 549 incorporates WCAG 2.1 AA. ↩ ↩2
-
WCAG 2.2 became a W3C Recommendation on 5 October 2023, w3.org/WAI/standards-guidelines/wcag. ↩
-
WebAIM Million, February 2026 report: 95.9% of the top 1,000,000 home pages had detectable WCAG failures, averaging 56.1 errors per page, webaim.org/projects/million. ↩
-
Overlay Fact Sheet, signed by more than 1,000 accessibility professionals, overlayfactsheet.com. ↩
-
FTC order requiring accessiBe to pay $1,000,000, proposed January 2025 and finalized April 2025, ftc.gov. ↩
