If you sell to consumers in the EU on Shopify, your store is almost certainly covered by the European Accessibility Act (EAA), and making it compliant means meeting WCAG 2.1 Level AA across the whole buying journey, not just the parts Shopify controls. Shopify gives you a reasonable starting point: its checkout core is maintained centrally with accessibility in mind, and its newer themes are built to follow WCAG principles. But once you pick a theme, install apps, and add your own products and copy, the accessibility of the storefront becomes your responsibility. Shopify says as much in its own documentation.
So Shopify EAA compliance is really three jobs: confirm the law applies to you, fix the storefront your customers actually use, and write an accessibility statement that records what you did. An automated scan finds the machine-detectable issues quickly. The rest, like keyboard checkout, meaningful alt text, and screen-reader output, needs a person. No app makes a store conformant on its own, whatever the app listing claims.
Here is how to work through it without guesswork.
Does the European Accessibility Act apply to my Shopify store?
Almost certainly, if you sell to EU consumers and you are not a tiny service business. The EAA is Directive (EU) 2019/882, and member states have applied it since 28 June 2025, so it is a live law (European Commission). E-commerce is one of the consumer services it explicitly covers.
Two things catch Shopify merchants out:
- Location does not exempt you. If you ship to or sell into the EU market, it does not matter where your company is registered. A US or UK brand running a Shopify store that takes EU orders is in scope.
- The small-business carve-out is narrow. A microenterprise providing a service (fewer than 10 people and annual turnover or balance sheet total of €2 million or less) is outside the service obligations (Directive (EU) 2019/882, Article 4). Both conditions must be true, and it applies to services, not products. Most stores selling steadily into the EU sit above that line.
If you run a real shop aimed at EU shoppers and you are above the microenterprise threshold, assume you are in. Our EAA overview breaks scope down by sector if your case is unusual.
What does Shopify handle, and what's on me?
This is the part most "Shopify is accessible" claims gloss over. Shopify maintains some layers; you own the rest.
What Shopify maintains. The core checkout layout is controlled centrally by Shopify, partly for accessibility, and merchants cannot edit its fundamental structure (Shopify checkout docs). Shopify's first-party themes are built against WCAG principles, and the admin lets you add alt text to product images and theme images (Shopify Help Center). That is a genuine head start over a hand-rolled storefront.
What you own. Everything a customer touches before checkout. The theme you chose and customized, the apps you installed, and the content you published. A well-built theme can be undone by a poorly coded app, a slideshow with no keyboard support, a low-contrast brand color, or product images shipped without alt text. Shopify's own guidance is direct about this: the platform is a foundation, and ensuring the store meets accessibility standards is the merchant's job.
The data backs up why that matters. In WebAIM's 2025 analysis of the top one million home pages, 94.8% had detectable WCAG failures, averaging 51 errors per page; Shopify-powered home pages averaged 69.6 errors, roughly a third above the overall sample (WebAIM Million 2025). A good platform does not produce a conformant store by default.
What does "EAA compliant" mean for a Shopify store?
The EAA sets the goal: the service has to be perceivable, operable, understandable, and robust for people with disabilities. It does not list the technical checks. For those it relies on the harmonized standard EN 301 549, and meeting the relevant parts gives you a presumption of conformity with the law.
The version cited today, EN 301 549 v3.2.1, incorporates WCAG 2.1 Level AA for web content (ETSI). So in practice, Shopify EAA compliance comes down to: does the whole purchase journey meet WCAG 2.1 AA? That covers browsing, search and filters, product pages, cart, checkout, and the order confirmation and emails that follow.
A v4.1.1 update that references WCAG 2.2 is expected, but until it is formally cited in the Official Journal, 2.1 AA stays the legal bar. Targeting 2.1 AA now and keeping an eye on the 2.2 additions, such as focus appearance and target size, keeps the eventual switch small.
How do I check and fix my Shopify store's accessibility?
Work in two layers, because neither covers everything on its own.
Layer one: automated testing. Run your key templates, not just the home page, through a scanner built on a real rules engine: home, collection, product, cart, and any landing pages. This clears the high-frequency, machine-detectable problems fast: missing alt text, low contrast, form fields without labels, missing page language, duplicate IDs, and basic ARIA mistakes. On Shopify these usually live in three places: theme settings (colors and fonts), app-injected markup, and your own product content.
Layer two: manual review. A person checks what a machine cannot judge. Can you complete the entire checkout with the keyboard alone? Does focus move in a sensible order through a mega-menu or a quick-view modal? Is the alt text meaningful rather than IMG_4821? Does a screen reader announce the variant picker and the cart drawer in a usable way?
How much does each layer catch? Deque's analysis of more than 2,000 audits found automated testing identified about 57% of issues by volume; counting by share of WCAG success criteria puts automation closer to 30% (Deque, 2021). Either way, much of conformance only shows up under human review. Scan first to clear the obvious defects, then run a structured manual pass with our WCAG checklist so nothing slips through. Fix issues in the theme code or app settings, then re-scan to confirm the change held.
A Shopify-specific tip: audit each app before you commit to it. Cart drawers, review widgets, cookie banners, and pop-ups are common sources of keyboard traps and unlabeled controls, and you usually cannot patch their internals. Choosing an accessible app is easier than fixing a bad one.
Do I need an accessibility statement for my Shopify store?
Yes, if your service is in scope. The EAA requires providers to explain how the service meets the accessibility requirements, in the information accompanying the service. EN 301 549 Annex C gives a structured way to document that, clause by clause, recording each applicable requirement as met, partially met, or not met.
This is where EAA compliance differs from a plain WCAG audit. WCAG is a technical standard and does not, by itself, ask for any document. The EAA does. An honest statement records your conformance level, lists known limitations, gives a plan and timeline for fixing them, and offers a contact for feedback. Documented effort is what the law asks for, not a perfect score. You can draft one with our accessibility statement generator, and the accessibility statement guide explains what each section should contain. On Shopify, a simple page (for example /pages/accessibility) linked from the footer is the usual home for it.
Can a Shopify accessibility app make my store compliant?
No app makes a store conformant on its own, and it is worth being blunt about why, because the app store is full of the opposite claim.
Accessibility lives in your source code: the markup and structure that assistive technology reads. An overlay app injects a script that tries to patch the page in the browser after it loads. It cannot fix the underlying theme or app code, and it struggles with exactly the things that matter on a store: menus, product galleries, variant pickers, forms, and the cart.
The claim that a tool can do this alone has a documented cost. In April 2025 the US Federal Trade Commission approved a final order requiring the overlay vendor accessiBe to pay $1 million over claims that its product could make any website WCAG compliant, and barred it from repeating that claim without evidence (FTC, April 2025).
Use apps for what they are good at. A scanner finds issues and points you at the theme or app code to fix, and it documents your progress over time. It does not, and should not claim to, deliver conformance by itself. Full conformance needs human review and real fixes.
A practical checklist for Shopify EAA compliance
- Confirm scope. Selling to EU consumers and above the microenterprise threshold? You are in.
- Set the target. WCAG 2.1 AA across the whole journey, plus any EN 301 549 clauses specific to your service.
- Scan your templates. Home, collection, product, cart, and key landing pages, not just one page.
- Audit your apps. Test each interactive widget with the keyboard and a screen reader; replace the ones you cannot fix.
- Review by hand. Keyboard checkout, focus order, alt-text quality, and screen-reader output against a checklist.
- Fix in the theme and app settings, then re-scan to confirm.
- Publish a statement that records your level, known gaps, and plan.
- Re-test on a schedule. A store drifts out of conformance every time you change a theme, add an app, or upload products.
Frequently asked questions
Is my Shopify store EAA compliant if I use an accessible theme?
No. An accessible theme is a strong start, but apps, customizations, and your own content can introduce issues a theme cannot prevent. Conformance depends on the whole store as published, which is why a scan plus manual review is the only way to know.
Does the EAA apply to a Shopify store based outside the EU?
Yes. If you offer products or services to consumers in the EU, the directive applies regardless of where your business is registered.
Which WCAG version does a Shopify store need to meet?
The EAA points to EN 301 549 v3.2.1, which incorporates WCAG 2.1 Level AA. A v4.1.1 update referencing WCAG 2.2 is expected, but until it is formally cited, 2.1 AA is the legal bar.
Does Shopify make my store compliant automatically?
No. Shopify maintains the checkout core and builds its themes against WCAG principles, but it states that ensuring the store meets accessibility standards is the merchant's responsibility once you customize the theme, add apps, and publish content.
Do I need an accessibility statement for a Shopify store?
For an in-scope store, yes. The EAA requires you to explain how your service meets the accessibility requirements. EN 301 549 Annex C gives a clause-by-clause format you can follow.
Check where your Shopify store stands
The fastest way to turn Shopify EAA compliance from a worry into a plan is to see your actual issues. Run a free scan of your home, collection, and product templates to find the machine-detectable problems, then work through the manual checklist for the rest. You will know what to fix, in what order, and what to put in your statement.
Pavel Charkasau, founder, wcagc.com. Last updated 22 June 2026.
Sources
- Directive (EU) 2019/882 (European Accessibility Act), EUR-Lex — scope, e-commerce, microenterprise exemption (Article 4), accessibility information requirement. Accessed 22 June 2026.
- European Accessibility Act, European Commission — application from 28 June 2025. Accessed 22 June 2026.
- EN 301 549 v3.2.1, ETSI — incorporates WCAG 2.1 AA (Chapter 9), Annex C documentation format. Accessed 22 June 2026.
- Accessibility for themes, Shopify Help Center — themes built to WCAG principles, alt text in admin and theme editor, merchant responsibility. Accessed 22 June 2026.
- checkout.liquid, Shopify developer docs — checkout core controlled by Shopify for accessibility. Accessed 22 June 2026.
- The WebAIM Million 2025, WebAIM — 94.8% of home pages with detectable WCAG failures, average 51 errors, Shopify average 69.6. Accessed 22 June 2026.
- Automated testing identifies 57% of accessibility issues, Deque — automated coverage. Accessed 22 June 2026.
- FTC approves final order requiring accessiBe to pay $1 million, Federal Trade Commission — deceptive WCAG-compliance claims. Accessed 22 June 2026.