Why the EAA Enforcement Dates Matter
The European Accessibility Act (Directive 2019/882) was transposed into national law by every EU member state and reached its primary enforcement date on 28 June 2025. From that day forward, the products, services, and digital channels covered by the directive must satisfy harmonised accessibility requirements or face the market-surveillance and penalty regime each member state adopted during transposition. The accessibility act 2025 deadline is the same date across the bloc, but the consequences — fines, contractual cure notices, public-procurement exclusion — are enforced locally and applied per product or service.
Unlike the U.S. ADA, the EAA does not depend on a private right of action to drive enforcement. National market-surveillance authorities now have an independent mandate to investigate, request remediation, and publish findings. Built into the directive is a presumption of compliance: when a business meets the harmonised standard (EN 301 549, whose technical baseline is WCAG 2.1 AA Level), the directive treats it as compliant.
EN 301 549 cites WCAG 2.1 AA as the floor for any "information and communication technology" deliverable that touched a consumer request or contract. The EAA does not invent new criteria — the four dozen AA success criteria are the binding test. For the underlying ADA lawsuit exposure U.S. businesses face on the same floor, see our ADA Website Lawsuit Risk guide.
Who the European Accessibility Act Applies To
The EAA covers both products and services offered to consumers in the EU. The categories that matter for a small business operating a website are explicit: e-commerce, banking, e-books, e-commerce platforms, and certain transport and ticketing services. B2C sites that target EU consumers are in scope even when the seller is incorporated outside the bloc, because territorial scope is determined by where the consumer sits, not where the supplier is headquartered. The directive also covers any "websites and mobile applications" that support a covered service — which is the language that captures every e-commerce checkout, account dashboard, and self-service booking flow sold into the EU.
The directive carves out a specific group of "microenterprises" providing services (fewer than 10 employees and under €2 million turnover), but the carve-out only applies to services and explicitly does not cover e-commerce or banking. If your site sells products, ships into the EU, or accepts payment from EU cards, you are in scope.
What an EAA-Compliant Website Requires Under WCAG 2.1 AA
EAA compliance on a website means satisfying every WCAG 2.1 AA success criterion against real browser-rendered pages, not a static HTML parse. The four automated-failure surfaces plaintiff scanners and EAA authorities run first are the same ones ADAflags checks by default: missing alternative text on images, unlabeled form fields, insufficient color contrast, and keyboard traps that block access to interactive elements. The directive's harmonised technical standard (EN 301 549) also incorporates the WCAG 2.2 additions, so the same five new AA criteria apply for site owners who want the cleanest audit trail.
The pattern is identical to what we see in U.S. ADA web demand letters: the same scanners the platform regulator runs are the scanners a business can run themselves. The difference under the EAA is that the authority running the scanner is a national market-surveillance body with a published penalty matrix. Plaintiffs and regulators use the same checklist, and the same categories of small interactive failures trip both. For the underlying substrate U.S. businesses are judged against, see our WCAG 2.2 New Requirements guide and the contrast between evidence-only scanners and overlay widgets.
Overlays still do not satisfy WCAG. The EAA's harmonised standard requires repair at the level of the underlying product or service, not a runtime patch that fires after page load. The same legal reasoning that fails overlays in U.S. ADA web accessibility cases applies to EAA enforcement, and the trio of AccessiBe, UserWay, and AudioEye each fail the same WCAG 2.1 AA rules the EAA enforces.
The June 2025 Effective Date and Ongoing Enforcement
The 28 June 2025 deadline applied to "new" products and services placed on the market after that date. The EAA's separate deadline — for products and services already on the market before 28 June 2025 — is 28 June 2030, but service providers must comply throughout the transition for new or renewed contracts. Market-surveillance authorities can investigate at any time from the 2025 effective date onward. Published findings (and the related penalty matrices in national laws) typically start with a cure period, escalating to formal fines and delisting for repeat non-compliance.
The pattern maps cleanly onto U.S. ADA web accessibility settlements: a regulator or plaintiff identifies a violation, the defendant is offered a cure window, and remediation evidence is later audited. Both regimes reward the same defensive posture — an evidence trail that shows what a real browser rendered at the time a violation was identified, not a self-attested conformance claim.
How to Check Your Site Before the EAA Deadline
The fastest way to surface EAA exposure on your own site is to run the same WCAG 2.1 AA scanner the regulator would run. ADAflags' free scan walks the live checklist, attaches real-Chrome evidence to each result, and ranks your failures by the same lawsuit-risk heuristic plaintiff firms use. The output is a public scorecard that maps directly onto EN 301 549 (and by extension onto the EAA's harmonised standard).
Run a Free EAA-Readiness Scan
ADAflags' free scan checks your live site against the WCAG 2.1 AA and 2.2 AA criteria the EAA enforces, ranks each violation by lawsuit risk, and shares the scorecard under a public URL you can attach to a remediation plan. No account required, no overlay vendor contract involved.
Run My Free Scan →A single scan is a snapshot — the same regulator-run scanner a market-surveillance authority uses will find the same failures six months later. For ongoing protection, our Starter ($9.99/mo) and Pro ($29/mo) plans rescan your site monthly and email you the deltas.
Related reading: For the ADA lawsuit-risk context that maps onto the same WCAG 2.1 AA floor, see ADA Website Lawsuit Risk. For the WCAG 2.2 additions the EAA's EN 301 549 standard also enforces, see WCAG 2.2 New Requirements. For the scanner-vs-overlay contrast that drives EAA-defensible evidence, see WCAG Scanners vs. Overlay Widgets. For the trio breakdown — vs. AccessiBe, vs. UserWay, vs. AudioEye — start with the AccessiBe comparison. For ongoing monthly monitoring under the EAA's 2030 transition horizon, see the Starter ($9.99/mo) or Pro ($29/mo) plans.