EAA for Ecommerce: Which Stores Must Comply [2026]

Last updated: October 31, 2026

Yes — the European Accessibility Act covers ecommerce, but "does the EAA apply to ecommerce" isn't really your question. Your question is whether it applies to your store, and that comes down to five yes/no tests: EU sales, size, audience type, marketplace role, and timing. Walk them in order below.

Key numbers: Directive (EU) 2019/882 defines "e-commerce services" in Article 3(30) as any service "provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract" — language broad enough to reach nearly every online store. The services microenterprise exemption requires fewer than 10 employees AND annual turnover or balance sheet total under €2 million, both conditions, company-wide (Art. 4(5)). Roughly 87 million people in the EU live with a disability, the population this scope question is ultimately about (European Commission). Maximum penalties are set by each member state and reach €500,000 in some, while Germany's BFSG caps fines at €100,000. On June 4, 2026, the Tribunal judiciaire de Caen ordered Carrefour France to make its site and app fully accessible within six months, backed by a €500-per-day penalty and €10,000 in damages — the first EAA-linked court order of its kind.

This guide is general information about EAA scope, not legal advice. Whether the directive applies to your specific store — and whether any exemption genuinely covers you — is a question for qualified counsel.

Is ecommerce covered by the EAA?

Yes, explicitly. Directive (EU) 2019/882 names e-commerce services in its own text, and Article 3(30) defines the term broadly enough to reach almost any online store — a service "provided at a distance...by electronic means...with a view to concluding a consumer contract."

That definition isn't limited to the homepage. It sweeps in the full storefront (search, category pages, product descriptions and alt text), checkout and payment, account creation, and the support channels a customer uses when something breaks — live chat, help-center forms, phone-tree menus tied to the service. It also reaches the paperwork a purchase generates: order confirmations, receipts, and PDF invoices, where TestParty's audits routinely find gaps nobody thought to test because they don't feel like "the website." If your business runs any part of that path, you're evaluating scope, not whether the law reaches you.

Which stores actually have to comply?

Five yes/no tests, applied in sequence, tell you whether your specific store is in scope. No single test decides it alone, and most direct-to-consumer brands clear the first three without much debate — it's the last two that trip people up.

1. Do you sell to EU consumers? The test is qualitative, not a volume threshold: EU shipping zones, EUR pricing, localized storefronts, and EU-targeted marketing are the evidence regulators and courts look to. A single unsolicited order from Belgium is a different fact pattern than an active German or French market with a translated checkout.

2. Are you a micro-enterprise? The services exemption requires fewer than 10 employees AND annual turnover or balance sheet total under €2 million — both conditions, measured across the whole company, not its EU slice. A lean seven-person label doing several million dollars worldwide is well over the line, and there's no grace period once you cross it. Document the self-assessment — headcount and financials, dated — rather than relying on an assumption nobody wrote down.

3. Is your storefront B2C, or genuinely B2B-only? The EAA regulates services offered to consumers; a wholesale portal gated to verified trade accounts, with no public path a consumer can buy through, generally sits outside scope. The catch: plenty of sites labeled "wholesale" or "trade" still run a public marketing and product layer anyone can browse, even if checkout itself is locked. That public layer keeps you in the analysis regardless of what your account gate says.

4. Are you a marketplace seller, or the marketplace operator? The platform operator — the marketplace itself — carries the Annex I obligations for the surfaces it controls: search, cart, checkout, account, payment. A seller listing only inside someone else's marketplace, using the operator's templates, generally isn't running an "e-commerce service" of its own under the directive. That flips the moment the same seller also runs its own direct storefront — a common setup for brands selling on Amazon and their own Shopify site — because the brand's own site is a separate service it owns outright, independent of the marketplace's compliance. Mixed setups are genuinely unsettled in places — read your own platform agreement with counsel rather than assume either side's compliance covers the other.

5. Is this a new service, or does a pre-existing exception apply? June 28, 2025 already passed, and there's no grace period for a live storefront operating today — new or long-running. The 2030 date circulating in vendor marketing covers a narrow exception: products a provider was already lawfully using to deliver a similar service before June 28, 2025 may keep running to June 28, 2030, and a small class of service contracts concluded before that date may run to term, capped at five years. Neither covers an ecommerce site's day-to-day operation, and a redesigned or relaunched storefront resets the clock outright — it's judged as a new deployment against today's standard, not whatever predated it.

What do US and UK stores need to know?

US stores face the same test as any non-EU seller: the EAA follows the customer, not the company's address, so incorporation in Delaware doesn't put you outside a directive that shipping to Dublin puts you inside. The UK sits entirely outside the EAA, governed instead by its own law.

For a US business, there's no EU-entity trigger and no revenue floor — if checkout accepts an address in a member state, treat the applicability analysis above as live rather than academic. The UK's exit from the EU means the directive simply doesn't apply to UK-only operations; obligations there come from the Equality Act 2010's reasonable-adjustments duty instead, a regime that references WCAG in practice rather than naming EN 301 549. Don't assume EAA compliance covers UK exposure, or the reverse. Our full breakdown of the applicability test and enforcement-risk math for US sellers works through the extraterritorial reach and enforcement against non-EU businesses so far.

What does compliance actually require?

Once you're in scope, the technical bar is EN 301 549 — the EU's harmonized standard — whose web clause currently points to WCAG 2.1 AA, with a draft update moving that reference to WCAG 2.2 AA. Building to 2.2 now satisfies both, since 2.2 is fully backward compatible.

Conforming to EN 301 549 earns a "presumption of conformity" that regulators treat as meeting the law unless shown otherwise, and it reaches the entire purchase path — search, product pages, cart, checkout, account, and payment — not just the parts merchandising treats as "the site." Beyond code, the directive requires a published Annex V accessibility statement naming what it covers, the standard targeted, and a working feedback channel; our walkthrough of what a compliant statement must say covers the section-by-section template. It also requires the support and documentation layer to actually work with assistive technology — an accessible complaint channel, order confirmations and PDF invoices a screen reader can read, and transactional emails that aren't a wall of unlabeled images.

What happens if you ignore it?

Penalties are set by each member state individually, not by the EAA itself, and the clearest enforcement outcome so far is a court order rather than an administrative fine: France's Tribunal judiciaire de Caen ordered Carrefour to fix its site and app within six months on June 4, 2026.

That ruling carried a €500-per-day penalty past the deadline plus €10,000 in damages to apiDV and Droit Pluriel, the disability-rights groups that brought the case — and the court rejected Carrefour's argument that partial conformance was close enough. Four member states publish figures specific enough to verify as of 2026:

Every other member state sets its own ceiling under its own transposition, so a business selling into five countries answers to five separate regimes. Our full country-by-country fine schedule covers every verified figure and the non-fine consequences — injunctions, market restriction — that often cost more than the penalty itself, and our case-by-case account of the French litigation traces how fast that timeline actually ran, from formal notice to court order.

How should a store sequence compliance now?

Four steps, in order: audit the full purchase path against EN 301 549/WCAG 2.2 AA, remediate in source code rather than with a runtime script, publish an accessibility statement, then monitor continuously so a fix doesn't regress with the next theme update.

Audit first, using both automated scanning and manual keyboard and screen-reader testing — automated tooling catches roughly 60–70% of issues in TestParty's detection data, and the remainder only surfaces manually. Remediate checkout and payment first, since it's the highest-exposure surface under the EAA and every other regime a store answers to; a shopper who can browse but can't pay defeats the service as a whole. Publish honestly, naming real gaps and dated fix targets rather than an unqualified "fully accessible" claim. Monitor continuously — in TestParty's work with EU-facing brands, daily automated scans paired with monthly expert manual audits catch what a single point-in-time audit misses, and initial remediation on the highest-severity issues typically closes within 14 days. Our Shopify-specific version of this sequence includes a full 90-day plan if you run on that platform, and our complete EAA compliance guide covers the full sequence once you've confirmed you're in scope.

Frequently Asked Questions

My store runs on Shopify — does Shopify's own accessibility work cover me? No. Shopify maintains the hosted checkout's core code and ships an accessible reference theme, but Theme Store requirements map to only 16–22% of WCAG 2.2 success criteria, and the theme as customized, every installed app, and your own content remain the merchant's responsibility under the EAA.

We sell through Amazon and also run our own site — which one has to comply? Both, but separately. The marketplace operator carries the compliance obligation for its own platform surfaces. Your own storefront is a distinct service you operate outright, and its compliance depends entirely on your own code, not on anything Amazon does on its side.

We get only a handful of unsolicited EU orders a year — are we exempt? Possibly, but don't assume it. The directive has no order-volume threshold; the question is whether the service is directed at EU consumers. A rare unsolicited order looks different from an active EU market with localized pricing or shipping — if the revenue is worth protecting, it's worth a counsel review rather than a guess.

Does labeling our storefront "wholesale only" take us out of scope? Only if there's genuinely no consumer-facing path to buy. A public marketing and product-browsing layer that any visitor can reach — even with checkout gated behind a trade-account login — keeps that layer in the analysis, regardless of how the site is labeled.

What if we cross the microenterprise threshold partway through the year? The exemption is a snapshot, not a grandfather clause. There's no grace period written into the directive — once headcount or turnover crosses the line, the obligations attach. Treat the exemption as runway you're using up, not permanent shelter.

Is the 2030 date real for any part of an ecommerce store? Only for a narrow slice: products already lawfully in use to deliver a similar service before June 28, 2025, and service contracts already concluded by that date, both capped and neither describing a live storefront's ongoing operation. A store trading today is judged against June 28, 2025 — already past — not 2030.

Like everything at TestParty, this article reflects our cyborg philosophy: AI handles the heavy lifting, humans bring the expertise. The data and opinions here are based on publicly available sources as of publication. TestParty is a participant in the accessibility market — we believe in transparency, so we encourage you to cross-reference our claims and evaluate all options for your business.