The European Accessibility Act: what it means for your website

What is the EAA, and when did it take effect?

The European Accessibility Act, formally Directive (EU) 2019/882, is an EU law requiring digital products and services to be accessible to people with disabilities, and it became enforceable on 28 June 2025 across all 27 member states, each of which transposed it into national law (WCAGAlert, 2026; Level Access, 2026). It builds on the earlier Web Accessibility Directive of 2016, which covered the public sector, and extends the obligation to private businesses for the first time (Level Access, 2026).

The directive has two stated purposes: improving access for the estimated 87 million people with disabilities in the EU, and streamlining cross-border commerce by replacing a patchwork of national rules with one unified standard, which lowers compliance costs for businesses operating across multiple countries (Level Access, 2026). Practitioners frequently describe it as the accessibility equivalent of GDPR — a single European framework with real teeth and global reach (Accessibility.Works, 2026).

Does it apply to my business — even outside the EU?

This is the part that surprises people: the EAA applies to any economic operator that places covered products or provides covered services to EU consumers, regardless of where the company is headquartered (Level Access, 2026). A US or Canadian e-commerce site that accepts orders from France, Germany or any other member state falls under its jurisdiction, and non-EU businesses are expected to appoint an EU-based authorized representative (accessibility.works, 2026).

The covered sectors are specific: e-commerce, banking and financial services, electronic communications, transport ticketing, e-books, and audiovisual media, and the rules reach both B2C and B2B services (WCAGAlert, 2026). For an online store, that means the website, the mobile app, the checkout process and customer communications all have to be accessible (TestParty, 2026). If your site offers EU shipping or accepts EU orders, the safe assumption is that you’re covered.

What does it actually require?

The EAA doesn’t invent a new technical rulebook; it points to an existing one. It references EN 301 549, the harmonized European standard for ICT accessibility, and the current version (v3.2.1) incorporates WCAG 2.1 Level AA in full as its web-content baseline (accessibility.works, 2026). Conforming to EN 301 549 creates a “presumption of conformity” with the law — meaning regulators presume you meet the requirements if you meet the standard (Acquia, 2026).

Two things are worth knowing beyond the web baseline. First, EN 301 549 extends past websites to cover mobile apps, non-web documents like PDFs, and hardware, so a full compliance picture may reach beyond your site (Acquia, 2026). Second, a version update — EN 301 549 v4.1.1, expected in 2026 — will incorporate WCAG 2.2 and its nine newer criteria; because WCAG 2.2 is backwards-compatible with 2.1, adopting it early creates no conflict while preparing for the future (Level Access, 2026). A mandatory accessibility statement, declaring conformance and giving a feedback contact, is also required.

One standard for the EAA, the ADA and Section 508

Here is the fact that turns a compliance burden into a single decision. EN 301 549 is built on WCAG 2.1 Level AA — the very same benchmark the US ADA requires under Title II and that Section 508 uses — so a website meeting WCAG 2.1 AA satisfies the core digital requirements of all three at once (ADAQuickScan, 2026). If you’re already working toward ADA conformance, you’re simultaneously working toward EAA conformance for your digital services (ADAQuickScan, 2026).

This convergence is why we treat accessibility as one global standard rather than a stack of regional obligations. Build to WCAG 2.1 AA once, and the same site is compliant in the EU, the US and any market that references WCAG — which most now do. That’s the practical, cross-border version of the argument in our pillar on whether web accessibility is the law: the standard is stable and shared, so the work doesn’t multiply per jurisdiction.

Who’s exempt? The narrow microenterprise carve-out

There is one exemption, and it’s tighter than most hope. Microenterprises — businesses with fewer than 10 employees and annual turnover or balance-sheet total not exceeding €2 million — are exempt from the EAA’s service requirements, though not from product (hardware) requirements (Level Access, 2026). Crucially, that carve-out does not extend to businesses based outside the EU that serve the EU market, so a small overseas store cannot rely on it (ADAQuickScan, 2026).

There’s also a “disproportionate burden” exemption under Article 14, but it isn’t a free pass: an organization must document the assessment against defined criteria and reassess at least every five years (Level Access, 2026). And even exempt or transitioning businesses face deadlines — service contracts concluded before June 2025 may continue only until June 2030, after which the exception lapses (UserWay, 2026).

How is it enforced, and what are the penalties?

The enforcement model is the biggest difference from the US. Where the ADA runs on private lawsuits, the EAA is enforced by market-surveillance authorities in each member state that proactively monitor compliance rather than waiting for a complaint (TestParty, 2026). That monitoring started immediately: France issued formal legal notices to major retailers within weeks of the deadline, Sweden’s telecom agency launched e-commerce surveillance focused on published accessibility statements, the Dutch regulator set a reporting deadline and moved to targeted audits, and the first EAA lawsuits were filed in French court in November 2025 (Level Access, 2026).

Penalties are set nationally and vary widely — from around €60,000 in Ireland to roughly €900,000 in Sweden, with Germany imposing up to €100,000 per violation and several countries adding daily fines up to €1,000 for ongoing non-compliance (Level Access, 2026; accessibility.works, 2026). Regulators can also order a service suspended or a product removed from the market. The signal they’ve sent about intent is worth quoting: the decisive enforcement question is not “are you fully compliant?” but “what have you been doing since accessibility became mandatory?” (UserWay, 2026).

The quieter risk: procurement and the accessibility statement

For many businesses the sharpest cost won’t be a fine — it will be a lost contract. European organizations now routinely require EN 301 549 conformance documentation as standard, so without proper accessibility documentation a supplier can be automatically disqualified from EU government, education and enterprise deals (Accessibility.Works, 2026). The accessibility statement is doing double duty here: it’s both a legal obligation and the document a buyer’s procurement team checks first.

That’s why Sweden’s early enforcement centred on whether retailers had even published the mandatory statement, and why a credible statement — one that names your real conformance level rather than an aspiration — matters more than a perfect score (UserWay, 2026). A statement you can stand behind requires having actually tested the site, which points back at doing the work rather than papering over it.

Overlays don’t work here either

If the ADA closed the overlay escape hatch, the EAA nailed it shut. The European Commission rejects overlay widgets for EN 301 549 compliance, stating that claims a website can be made fully compliant without manual intervention are not realistic, because no automated tool can cover all the WCAG 2.1 A and AA criteria (Accessibility.Works, 2026). The Commission goes further, warning that overlays can interfere with the assistive technologies people with disabilities rely on, potentially making a site less accessible than before (Accessibility.Works, 2026).

The European Disability Forum and the International Association of Accessibility Professionals jointly advise against overlays, recommending genuine expert remediation instead (Accessibility.Works, 2026). This is the same widget our guide on whether accessibility overlays are a legal trap documents failing under US law — now failing under two legal regimes at once, and providing neither compliance nor legal cover in either.

Why a site built accessible answers the question already

Everything above resolves into a single practical stance. Automated tools catch only 30-40% of accessibility barriers, so EN 301 549 conformance requires manual testing with assistive technologies across real user workflows — there is no button that makes a site compliant (accessibility.works, 2026). The realistic path is to build the site to WCAG 2.1 AA, test it properly, and publish an honest conformance statement, which is exactly the discipline our WCAG 2.2 checklist lays out step by step.

A site made accessible from the start answers the regulator’s question before it’s asked. Because EN 301 549 is WCAG 2.1 AA, a semantic, keyboard-operable, properly-labelled site built to the standard is compliant across the EAA, the ADA and Section 508 simultaneously, and the required statement simply describes a reality that already exists rather than promising one that doesn’t. That’s the whole argument of our accessibility pillar restated for a second continent: the most reliable way to comply with the law — any of these laws — is to build so that compliance is the default rather than the patch.