Unlike earlier EU directives that applied only to public-sector bodies, the European Accessibility Act directly covers private-sector e-commerce websites, online banking, travel/ticketing portals, e-books, and digital consumer services sold to EU residents—even if your company is headquartered in the US or UK. Only microenterprises providing services (fewer than 10 employees AND under €2 million annual turnover or balance sheet) receive an exemption.
Technically, EAA compliance maps to European standard EN 301 549, which incorporates WCAG 2.1 Level AA for web content—and adds mandatory non-code requirements like publishing a plain-language Accessibility Statement detailing how customers can report barriers and contact national enforcement bodies.
5-Step 2026 EAA Remediation Roadmap
- 1
Confirm scope & microenterprise exemption eligibility
If your business sells goods or digital services online to EU consumers and exceeds 10 staff OR €2M turnover, your storefront, checkout, and customer portal fall directly under national EAA transpositions (such as Germany's BFSG).
- 2
Run an automated DOM baseline scan on homepage, product, and checkout pages
Scan your core conversion URLs for missing <html lang>, unlabeled checkout inputs, zoom-blocking viewport tags, broken heading hierarchies, and missing alt attributes—these account for the majority of automated enforcement flags.
- 3
Fix real HTML semantics (do not rely on JavaScript overlay widgets)
EU disability advocacy groups and EN 301 549 auditors explicitly reject one-line overlay widgets as non-compliant because they fail to repair underlying form labels, keyboard focus traps, or screen-reader announcements in checkout modals.
- 4
Verify full keyboard-only checkout & focus visibility
Unplug your mouse and navigate from your homepage to a product, add to cart, open the cart drawer, enter shipping details, and reach the payment button using only Tab, Shift+Tab, Enter, and Escape. Every interactive element must display a clear focus outline.
- 5
Publish a mandatory EAA Accessibility Statement in local customer languages
Create a dedicated /accessibility page linked from your site footer explaining your WCAG 2.1 AA / EN 301 549 conformance status, known limitations, a feedback email/phone channel, and the relevant national market surveillance authority.
EAA National Enforcement & Penalty Overview Across Major EU Markets (2026)
| Member State & Law | Enforcement Authority | Potential Non-Compliance Exposure |
|---|---|---|
| Germany (BFSG) | Marktüberwachungsstelle der Länder (MLBF) | Fines up to €100,000 plus cease-and-desist orders & competitor Abmahnungen. |
| France (Code de la consommation) | DGCCRF & ARCOM | Administrative fines per non-compliant service plus mandatory public disclosure. |
| Ireland (S.I. No. 636/2023) | Competition & Consumer Protection Commission (CCPC) | Summary conviction fines up to €5,000 or indictment penalties up to €60,000 / director liability. |
| Spain (Ley 11/2023) | National & regional consumer authorities | Tiered sanctions ranging from €301 up to €1,000,000 for severe repeated breaches. |
EN 301 549 / WCAG 2.1 AA Technical Checklist
- Declare accurate <html lang="de">, <html lang="fr">, or <html lang="en"> on every localized storefront route.
- Ensure every checkout, newsletter, and search <input> has an explicit <label for="..."> or aria-label—placeholder text alone fails WCAG 3.3.2.
- Maintain minimum color contrast of 4.5:1 for body text and 3:1 for large headings, icons, and form borders.
- Never block pinch-to-zoom with user-scalable=no or maximum-scale=1 in your viewport meta tag (fails WCAG 1.4.4 Resize Text).
- Provide descriptive alt text on product photos and empty alt="" on purely decorative icons so screen readers skip noise.
- Include semantic landmarks (<header>, <nav>, <main>, <footer>) and a visible 'Skip to main content' link.
4 EAA Mistakes That Trigger 2026 Compliance Notices
- Assuming US/UK headquarters exempts your store: EAA applies wherever you market and sell to EU consumers, regardless of corporate domicile.
- Installing an accessibility overlay script and calling it done: overlays add JavaScript bloat without fixing underlying DOM errors and are explicitly criticized by EU regulators and the European Disability Forum.
- Forgetting third-party cookie banners and chat widgets: an inaccessible OneTrust modal or Intercom bubble that traps keyboard focus makes the entire checkout unreachable.
- Publishing an English-only Accessibility Statement on a German or French storefront: statements must be understandable to the local consumer market.
Check Your Site Against 16 Real EAA/WCAG & Local SEO Rules in 5 Seconds
Run PlainAudit's free scanner above to detect missing labels, viewport zoom locks, heading gaps, and missing landmarks with exact copy-paste HTML fixes.
Frequently Asked Questions
Does the EU Accessibility Act apply to US or UK e-commerce stores?
Yes. If your US or UK online store targets and sells to consumers in EU member states (such as offering EUR pricing, EU shipping, or localized pages) and does not qualify as a microenterprise (<10 staff and <€2M turnover), EAA rules apply.
Do accessibility overlay widgets make my website EAA compliant?
No. European accessibility regulators and EN 301 549 conformance criteria evaluate your real DOM semantics, keyboard navigation, and screen-reader behavior. Fixing your actual HTML is faster, cheaper, and legally defensible.
Is WCAG 2.1 AA enough for EU Accessibility Act compliance?
WCAG 2.1 Level AA covers the core technical web criteria inside EN 301 549, but EAA also requires publishing a clear Accessibility Statement, maintaining accessible customer support channels, and ensuring downloadable invoices or PDFs are accessible.