The European Accessibility Act: What U.S. E-Commerce Sellers Need to Know If They Sell to the EU

Most accessibility-law content aimed at U.S. e-commerce stores — including our own coverage of ADA compliance risk and how ADA, Section 508, and WCAG relate — stops at the U.S. border. That’s a gap if your store actually sells past it. A U.S.-based business with no EU office, no EU incorporation, and no physical presence in Europe at all can still be inside the scope of a separate accessibility law: the European Accessibility Act. It doesn’t care where you’re registered. It cares who you sell to.

Quick answer: the European Accessibility Act (Directive (EU) 2019/882, “EAA”) is an EU law requiring accessibility for a defined list of products and services offered to consumers in the EU — e-commerce is explicitly one of them. Its substantive requirements have applied since 28 June 2025. Scope is based on who your customers are, not where your business is based, so a U.S.-only company selling directly to EU consumers through its own website can be a covered “economic operator.” A carve-out exists for genuine micro-enterprises providing services — fewer than 10 employees and no more than €2 million in annual turnover or balance-sheet total — but nothing in the directive exempts businesses simply because they’re based outside the EU.

This article is educational content about how a specific EU law works, not legal advice. Whether your specific business is in scope, and what if anything you need to do about it, is a legal question for an attorney familiar with EU law — not something this article, or any general article, can answer for your specific facts.

What the EAA actually is

The EAA is an EU directive — not U.S. law, and not a WCAG-style technical standard on its own — that requires accessibility for a specific list of products and services made available to consumers in the EU. Per the European Commission’s own summary, the covered list includes computers and operating systems, smartphones, ATMs and self-service terminals, e-books, certain transport services, banking services, and — named explicitly — e-commerce. The European Parliament’s own legislative summary confirms the same scope in more specific terms, describing covered e-commerce services as “websites, integrated services on mobile devices, including mobile applications.” A storefront website and its checkout flow are squarely the kind of thing this law is written to reach — the same components a WCAG 2.1 AA audit already evaluates for U.S. legal-risk reasons.

Like most EU directives, the EAA itself sets the requirement; each member state then wrote it into their own national law. EU member states had until 28 June 2022 to transpose the directive, and the Commission’s page confirms it now “monitors the complete and correct implementation and transposition of the Act” across all 27 states.

Who’s actually in scope — and why “I’m a U.S. company” isn’t an exemption

The EAA regulates products and services offered to consumers in the EU, not businesses headquartered in the EU. A U.S.-based store selling directly to EU shoppers — accepting EU addresses at checkout, pricing in euros, shipping into the EU — is providing exactly the kind of consumer-facing e-commerce service the directive covers, regardless of where the company itself is incorporated or hosted. This is a genuinely different scope test than the one most U.S. accessibility content assumes: ADA Title III risk in the U.S. turns on questions like nexus to a physical location; EAA scope turns on who’s on the other end of the transaction.

That doesn’t mean every U.S. store with an occasional EU customer is a realistic enforcement target, and this article isn’t making a legal-risk prediction either way — that’s exactly the kind of case-by-case call that belongs to an attorney, not a general article. What it does mean is that “our business is U.S.-based” isn’t, on its own, a reason to assume the EAA doesn’t apply.

The micro-enterprise exemption

The EAA does build in a real carve-out for small businesses providing services, and it’s worth knowing the actual numbers rather than assuming your store is either obviously in or obviously out. Directive (EU) 2019/882, Article 2(3), defines a “microenterprise” as an enterprise that employs fewer than 10 people and has an annual turnover or annual balance-sheet total not exceeding €2 million — and the directive’s requirements and obligations don’t apply to microenterprises providing services within its scope. (EUR-Lex, the EU’s official legislation portal, returned an automated bot-check response rather than readable content to this article’s research tooling; this specific figure was cross-verified against the same operative language quoted independently by multiple secondary legal sources rather than taken from a single unverified summary.)

Two things matter about how narrow this exemption actually is. First, it’s an EU-style micro-enterprise definition — under 10 employees and under €2 million — not the much larger “small business” thresholds U.S. owners might assume. A store with 25 employees, or one with 8 employees but €3 million in revenue, doesn’t qualify. Second, per the European Parliament’s summary linked above, the exemption structure treats service microenterprises differently from product microenterprises — a distinction with real substance in the directive’s text that a short summary (including this one) can’t fully resolve for your specific business.

Deadlines that have already passed

Two dates matter, and both are already behind us as of this article’s publish date:

• 28 June 2022 — the deadline for EU member states to transpose the directive into their own national laws.
• 28 June 2025 — the date the EAA’s substantive accessibility requirements took effect for covered products and services.

There’s no future compliance deadline to “get ready for” here the way there sometimes is with new U.S. rules — if the EAA applies to your store, the obligation is already active, not upcoming.

What “accessible” means under the EAA — and how it relates to WCAG

The EAA doesn’t invent its own accessibility checklist from nothing. For web content, the technical detail sits in a European harmonized standard called EN 301 549, and per the W3C Web Accessibility Initiative’s own page on EU policy, that standard has closely tracked WCAG at the AA level for years.

That relationship is mid-shift right now, and the detail matters because it’s the exact overlap this article leans on. On 2 September 2026, ETSI published EN 301 549 v4.1.1. Per the European Commission’s AccessibleEU centre, v4.1.1 “adopts WCAG 2.2 as the accessibility benchmark for websites, software and digital documents, replacing WCAG 2.1.” That’s a full version bump, not a routine refresh — the update targets a newer, stricter version of WCAG than the one most U.S. audits (including Quietramp’s) are scoped to today.

Crucially, v4.1.1 isn’t yet the legally-binding reference. The same AccessibleEU page is explicit that “the current reference remains EN 301 549 v3.2.1 (2021), which is based on WCAG 2.1 Level AA,” until the European Commission formally cites v4.1.1 in the Official Journal of the EU — the step that confers the “presumption of conformity” a harmonized standard carries. Industry coverage of the ETSI work programme (for example, Deque’s writeup of the v4.1.1 publication) puts that Official Journal citation on track for around 30 November 2026 — described as a scheduled target, not a confirmed date.

So the practical takeaway is time-bound rather than permanent: today, the standard that actually carries legal weight under the EAA is EN 301 549 v3.2.1, built on WCAG 2.1 AA — the same benchmark this site’s own audits, and most U.S. legal guidance, already point to. That makes a conformant U.S. accessibility posture a strong starting point for the EU technical bar right now. But once the Commission formally cites v4.1.1, the legally-binding technical target shifts to WCAG 2.2, and this overlap will narrow — worth revisiting this page, or asking your auditor, once that citation happens rather than assuming today’s overlap holds indefinitely.

Enforcement isn’t centralized

Unlike GDPR’s more familiar structure, the EAA doesn’t set up one EU-wide regulator or one uniform penalty schedule. Per the Commission’s own page, its role is monitoring transposition and implementation across member states — actual enforcement and penalty-setting is left to each member state’s own designated national authority, operating under that country’s own transposition law. That means the specific consequences of non-compliance genuinely vary by which EU country’s consumers you’re selling to, and this article isn’t going to guess at country-by-country penalty figures — the sourcing available for country-specific numbers wasn’t consistent or verifiable enough to print with confidence.

FAQ

We’re a small U.S. store with a handful of EU customers a year. Does this really apply to us? That’s a legal scoping question this article can’t answer for your specific facts — it depends on things like your size against the microenterprise thresholds above and how your sales into the EU actually work. It’s worth asking an attorney familiar with EU law rather than assuming either way.

If we’re already WCAG 2.1 AA compliant for U.S. ADA reasons, are we automatically EAA-compliant? Not automatically — they’re different legal frameworks with different scope and enforcement structures. Right now the standard that’s actually legally binding under the EAA, EN 301 549 v3.2.1, is itself built on WCAG 2.1 AA, so today’s overlap is real. But that’s set to change: a newer version (v4.1.1) that adopts WCAG 2.2 instead has already been published and is expected to become the binding reference once the EU formally cites it in the Official Journal, likely around late 2026 — see the WCAG section above for the detail.

Does this replace anything we already do for U.S. accessibility risk? No. The EAA is an additional consideration if you sell into the EU, not a substitute for ADA Title III risk in the U.S. — the two exist side by side.

The technical work overlaps today — a WCAG 2.1 AA audit still covers the core of it

Whether your exposure is framed as U.S. ADA risk, EAA scope, or both, WCAG 2.1 AA is the standard that carries legal weight on both sides of the Atlantic right now, so the technical work overlaps — though as the section above explains, that overlap is tied to the EU’s current reference standard, not guaranteed to stay put. Quietramp’s $890 one-time audit is a human-verified pass against WCAG 2.1 AA, with $99/month optional re-monitoring after fixes ship — not a legal opinion on EAA scope, just documented, developer-actionable accessibility findings. See a real sample report or check pricing.

---

This is provided for general educational purposes and does not constitute legal advice. Directive text, EU institutional guidance, and standards described here reflect the sources cited as of this article’s publish date and may change; only a qualified attorney familiar with EU law can assess whether the European Accessibility Act applies to your specific business.

Quietramp is an AI-operated agency with human oversight — this article was drafted by our Content/SEO writer role.