European Accessibility Act for Shopify Stores: The 2026 Compliance Guide

Last updated: August 31, 2026

The European Accessibility Act applies to your Shopify store if you sell to consumers in the European Union — regardless of where your company is registered — unless you qualify as a microenterprise with fewer than 10 employees and no more than €2 million in annual turnover. Enforcement began June 28, 2025, the first lawsuits have been filed, and this guide covers exactly what a Shopify merchant selling into the EU must do.

Key numbers: The EAA has been enforceable since June 28, 2025, and covers ecommerce services sold to EU consumers no matter where the seller is based (Directive (EU) 2019/882). Maximum penalties vary by member state, reaching €500,000 in some, and Ireland's transposition adds potential criminal liability for company officers. The first EAA lawsuits were filed November 12, 2025, against four French retailers — Auchan, Carrefour, E.Leclerc, and Picard (Paris court filings). Roughly 87 million people in the EU live with a disability (European Commission). In TestParty's testing, Shopify's own Dawn theme ships with 30–100 detectable WCAG violations out of the box, and premium themes carry 100–350.

This guide is educational information, not legal advice. For questions about your store's specific obligations under the EAA or any member state's transposition, consult qualified counsel.

Does the EAA apply to my Shopify store if I'm not based in Europe?

Yes — the EAA follows the consumer, not the company. Directive (EU) 2019/882 covers ecommerce services "provided to consumers within the Union," so a US, UK, Canadian, or Australian Shopify merchant selling to EU shoppers is in scope (EUR-Lex).

The practical test is whether your store is directed at EU consumers, and Shopify's own tooling often supplies the evidence: shipping zones that include EU member states, EUR pricing through Shopify Markets, translated storefronts on EU-facing domains, and campaigns targeting EU audiences. If those describe your store, the safer working assumption is that the directive applies — the analysis works much like GDPR's targeting test. An occasional unsolicited order from Belgium is a different situation than an active DE/FR market with localized checkout, but the directive contains no formal de minimis threshold. For the full legal architecture — who is covered and which annexes apply — see our complete European Accessibility Act guide.

Who qualifies for the microenterprise exemption?

Microenterprises providing services — meaning fewer than 10 persons employed AND annual turnover or balance sheet total not exceeding €2 million — are exempt from the EAA's service requirements, and an online store is legally a service (Directive (EU) 2019/882, Art. 4(5)).

Three details trip merchants up. First, both conditions must hold; a three-person store doing €5 million in revenue is covered. Second, the thresholds apply to the enterprise, not the storefront — headcount and turnover are measured across your whole company, not the EU slice of it. Third, the full exemption is a services rule: microenterprises that manufacture products get lighter paperwork, not a pass on the requirements. And there is no grace period in the directive's text — the day you cross a threshold, the obligations attach, so treat the exemption as a runway rather than a shelter.

What parts of a Shopify store does the EAA cover?

The EAA covers the shopping experience end to end: product discovery and search, product pages, cart, checkout, account creation and login, payment, order tracking, digital receipts and invoices, and the support channels a customer uses to get help.

The directive's Annex I requires that the information needed to identify products, pay, and arrange delivery be perceivable and operable — which maps onto a Shopify store's product descriptions, variant pickers, shipping selectors, and payment forms. It also reaches artifacts merchants forget: PDF invoices from an order-printer app, transactional emails, the support chat widget. If a blind customer can browse your catalog but cannot complete payment at checkout, the service fails as a whole. We break down each requirement, annex by annex, in our guide to EAA requirements for ecommerce businesses.

What technical standard does the EAA require — WCAG 2.1 or 2.2?

The EAA's harmonized technical standard is EN 301 549, whose web clause currently points to WCAG 2.1 Level AA (ETSI, v3.2.1). A draft version 4 moves that reference to WCAG 2.2 AA, with Official Journal citation expected around late 2026.

Conforming to the harmonized standard earns a "presumption of conformity" — regulators treat you as meeting the law unless proven otherwise — which is why EN 301 549 is the benchmark worth documenting against. The pragmatic move in 2026 is to remediate to WCAG 2.2 AA now: it is backwards compatible with 2.1, and the draft EN 301 549 v4.1.0 (November 2025) already maps 2.2 criteria to EAA articles. The 2.2 additions hit ecommerce flows directly — minimum tap-target sizes, focus indicators that can't hide behind sticky headers, no re-typing information already entered, and accessible login without cognitive puzzles (W3C, What's New in WCAG 2.2).

Do I need an accessibility statement?

Yes. Annex V of the EAA requires service providers to publish an explanation of how their service meets the accessibility requirements — in your terms and conditions "or equivalent," available in an accessible format.

For a Shopify store, the workable pattern is a dedicated accessibility page linked from the footer, covering: what the statement applies to, the standard you target (EN 301 549 / WCAG 2.2 AA), how the requirements are met, known limitations, a feedback channel, and a "last reviewed" date. If you run market-specific storefronts through Shopify Markets, publish it in each market's language — a French storefront with an English-only statement undercuts the point. Keep it honest; an aspirational statement contradicted by a broken checkout is worse evidence than no statement at all.

Who enforces the EAA, and what are the penalties?

Each of the 27 EU member states enforces the EAA through its own market surveillance authorities and its own penalty schedule — reported maximums range from €100,000 in Germany under the BFSG to €500,000 in some member states, with Ireland adding potential criminal liability.

There is no single EU accessibility regulator; a store selling into five member states answers to five enforcement regimes, and consumers and disability organizations can complain — or, as France showed, sue directly. Activity through August 2026:

+------------------+-----------------------------------------------+----------------------------------------------------+
|   Member state   |               Enforcement route               |             Activity as of August 2026             |
+------------------+-----------------------------------------------+----------------------------------------------------+
|   Netherlands    |   Authority for Consumers and Markets (ACM)   | Required non-conformance reports by October 15, 2025; audits of non-responders began spring 2026 |
+------------------+-----------------------------------------------+----------------------------------------------------+
|      Sweden      |         Post and Telecom Agency (PTS)         | Opened its first ecommerce inspection cases in late 2025; inspections continuing through 2026 |
+------------------+-----------------------------------------------+----------------------------------------------------+
|     Ireland      |                     ComReg                    | Processing consumer complaints, including a formal complaint against a major telecom provider |
+------------------+-----------------------------------------------+----------------------------------------------------+
|      France      |                 NGO litigation                | Four national retailers summoned in November 2025 over inaccessible websites and apps |
+------------------+-----------------------------------------------+----------------------------------------------------+

Country-by-country fine schedules and complaint mechanisms are detailed in our breakdown of EAA penalties and enforcement by member state.

Is the EAA actually being enforced yet?

Yes — enforcement opened with reporting deadlines and NGO litigation rather than headline fines. The first EAA lawsuits were filed November 12, 2025, when disability organizations ApiDV and Droit Pluriel sued Auchan, Carrefour, E.Leclerc, and Picard over inaccessible websites and mobile apps.

The French timeline shows how fast the clock runs: formal notices went out July 7, 2025 — nine days after the enforcement date — with a September 1 compliance deadline, and when progress stalled, the organizations filed emergency injunction proceedings seeking court-ordered fixes rather than damages. The failures cited were ordinary ones: missing alt text, insufficient contrast, keyboard-inaccessible interfaces, broken page structure. Regulators elsewhere are starting softer — the Dutch ACM has said fines "are absolutely not the goal" of its first wave — but audits of non-responsive companies began in spring 2026. The full case history is in our report on the first EAA lawsuits against French retailers.

What does Shopify handle for EAA compliance — and what's on you?

Shopify provides accessible infrastructure and a reference theme, but its documentation is explicit that merchants are responsible for their own store's compliance with applicable accessibility laws (Shopify Help Center).

+-----------------+----------------------------------------------------+----------------------------------------------------+
|   Store layer   |               What Shopify provides                |     What remains the merchant's responsibility     |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|     Checkout    |     Maintains the hosted checkout's core code      | Checkout customizations, extensions, custom fields, and brand colors that break contrast |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|      Theme      | Dawn reference theme; Theme Store review criteria  | The theme as shipped and customized — Theme Store requirements cover only 16–22% of WCAG criteria (TestParty analysis) |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|       Apps      |               App Store distribution               | Every installed app's injected widgets, popups, and forms — apps are not reviewed for accessibility |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|     Content     |      Editor fields for alt text and headings       | Actually writing alt text, structuring headings, captioning video, choosing accessible contrast |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|     Markets     |        Shopify Markets localization tooling        | Accessibility of each translated storefront, plus per-language accessibility statements |
+-----------------+----------------------------------------------------+----------------------------------------------------+
|    Statement    |                      Nothing                       | Drafting, publishing, and maintaining the Annex V statement |
+-----------------+----------------------------------------------------+----------------------------------------------------+

In TestParty's audits, market-specific storefronts are a recurring blind spot. When we audited the EU storefronts of a US Shopify Plus consumer brand, the English flagship had been remediated — but the French and German markets had translation-stripped alt text and an untranslated, mouse-only consent widget. Every market you open is a surface you have to test.

What is the 90-day EAA compliance plan for a Shopify store?

Ninety days is enough for a typical Shopify store already selling into the EU to reach a defensible EAA posture: scope and scan in weeks 1–2, remediate the purchase path through week 7, publish the statement by week 10, then verify and set monitoring.

Days 1–15 — Scope and scan. Confirm applicability and do the microenterprise math. Inventory every EU-facing market, domain, and language. Run an automated scan, then a manual keyboard-and-screen-reader pass of the money path: home, search, product page, cart, checkout, account. Automated tooling surfaces 60–70% of issues in TestParty's detection data; the remainder only shows up manually.

Days 16–45 — Remediate the purchase path. Fix theme source code on revenue-critical templates first: form labels, alt text, focus states, contrast, variant pickers, error messaging. Triage apps ruthlessly — replace or remove any that inject inaccessible UI you cannot fix.

Days 46–75 — Statement and support. Draft and publish your Annex V accessibility statement across all market storefronts in local languages, stand up an accessible feedback channel, and date-stamp your remediation documentation as you go.

Days 76–90 — Verify and monitor. Re-audit manually, produce a dated conformance report against EN 301 549, and put monitoring in place so fixes do not regress with the next theme update. In TestParty engagements, initial remediation typically completes in 14 days, with ongoing coverage running as daily automated scans plus monthly expert manual audits — customers spend about 15–30 minutes a month reviewing the resulting pull requests.

Frequently Asked Questions

Does the EAA apply to a US Shopify store with no EU office or entity? Yes, if the store sells to EU consumers. The directive regulates services provided to consumers within the Union, not companies established there. Shipping to EU addresses, EUR pricing, EU-market storefronts, and EU-targeted marketing all indicate a covered service. Physical presence in Europe is irrelevant to the analysis — what matters is where your customers are.

Am I exempt if I only get occasional EU orders? Possibly, but do not assume it. The directive contains no order-volume threshold; the question is whether your service is directed at EU consumers. A store accepting a rare unsolicited order looks different from one running localized EU markets. If your EU revenue is worth protecting, it is worth a counsel review.

Should I remediate to WCAG 2.1 AA or 2.2 AA? Target WCAG 2.2 AA. The current harmonized standard, EN 301 549 v3.2.1, references 2.1 AA, but the draft v4 moves to 2.2 AA and 2.2 is fully backwards compatible — every 2.1 criterion is included. Building to 2.2 now means you satisfy today's benchmark and will not re-open the work when the updated standard is cited.

Does an accessibility overlay widget make my Shopify store EAA compliant? No. Overlays leave the underlying theme code unchanged, and the failures cited in the first EAA litigation — missing alt text, broken keyboard access, poor structure — live in source code. In the US context, TestParty's analysis of Court Listener records found more than 1,000 businesses with overlay widgets installed were sued in 2024.

How is the EAA different from the ADA? The EAA is a product-and-service market regulation enforced by government authorities with statutory fines; the ADA is a US civil rights law enforced mostly through private lawsuits. The EAA names its technical standard (EN 301 549) in law, while US courts look to WCAG by convention. We map the differences in detail in our EAA versus ADA comparison.

What must an EAA accessibility statement include? A description of the service covered, the accessibility requirements and standard you target (EN 301 549 / WCAG AA), how the service meets them, known limitations, and a way for customers to send accessibility feedback. Publish it in an accessible format, link it from your footer, localize it for each market storefront, and keep it dated and current.

TestParty practices a cyborg approach to content: AI assists with research and drafting, our accessibility experts validate every claim. This article represents our editorial perspective based on public data as of the publication date. We compete in the digital accessibility space — which means we have informed opinions, but also a vested interest. All sources are cited so you can draw your own conclusions.