European Accessibility Act 2026: Complete Guide
The EAA became enforceable on June 28, 2025, across all 27 EU member states simultaneously. France filed the first lawsuits within months. Norway began issuing daily financial penalties. If your business serves EU customers, the obligation is live now. A single audit has an expiry date. Every code deploy introduces new violations. Ongoing compliance requires ongoing coverage.
Start Free Trial Run a Free Scan
Enforcement live across 27 EU member states since June 28, 2025
What's Happening Now
France moved first. In November 2025, the DGCCRF issued formal legal notices to four of France's largest retailers, Auchan, Carrefour, E.Leclerc, and Picard, demanding accessibility compliance. When the retailers failed to act, emergency injunctions were filed before the Commercial Court on November 12, 2025. These are the first EAA enforcement actions in the EU. The cases target checkout flows, product browsing, and missing Accessibility Statements.
Norway demonstrates the compounding risk. The HelsaMi health portal, used by nearly half a million residents, was issued a daily penalty of NOK 50,000 (~€4,500 per day) for persistent accessibility failures. The fine accumulates without ceiling until full remediation is complete. Every day without action increases the liability.
The Netherlands is escalating. The ACM set an October 15, 2025 deadline for non-conformance reporting. Businesses that failed to report are now prioritised for audits in spring 2026. The ACM stated plainly: "There is a very big gap between the status of the industry and the compliance with EAA."
A non-compliant site serving customers in five EU countries does not face one enforcement action. It faces five, one per national regulator, running simultaneously, with no cross-border penalty cap and no single settlement that closes all of them. Every country you sell into is a separate enforcement risk.
| Country | Maximum Penalty | Enforcement Body |
|---|---|---|
| Germany | €100,000 per violation | Bundesnetzagentur |
| France | €250,000 aggregate | DGCCRF / ARCOM / ARCEP |
| Spain | €1,000,000 (serious violations) | Ministry of Social Rights |
| Netherlands | €900,000 or 10% annual revenue | ACM |
| Sweden | SEK 10,000,000 (~€870,000) | PTS |
Figures vary by national transposition. Updated April 2026. Check your jurisdiction for current figures.
June 28,2025
Enforcement Began
27%
EU Member States Covered
87M+
EU People with Disabilities
20%
Estimated EU Population Share
What Is the European Accessibility Act
The European Accessibility Act, Directive (EU) 2019/882, is EU legislation requiring that digital products and services be accessible to people with disabilities. It was adopted in April 2019. Member states had until June 28, 2022 to transpose it into national law, and until June 28, 2025 to begin enforcement.
Previous EU accessibility law covered only public sector websites. The EAA extends this obligation to the private sector. Any business placing products or services on the EU market is covered, regardless of where it is headquartered.
The directive has explicit extraterritorial reach. A business headquartered in the United States, Australia, or India that sells products or services to EU customers falls under the EAA. The law follows the customer, not the company's registered address.
The EAA requires conformance with EN 301 549, the harmonised European ICT accessibility standard, which incorporates WCAG 2.1 Level AA for web content. Meeting EN 301 549 creates a presumption of conformity with EAA requirements.
Who the EAA Applies To
The EAA applies to any business offering products or services in the EU market. Size thresholds apply, but the exemption is narrow.
Micro-enterprise exemption
The exemption covers businesses with fewer than 10 employees AND annual turnover below €2 million.
Both conditions must apply simultaneously. Exceed either one and the EAA applies in full.
This exemption does not apply to non-EU businesses serving EU customers, regardless of size.
Which Industries Are Most Affected
What the EAA Actually Requires
The EAA creates a four-layer technical obligation. Each layer narrows the standard down to what your developers and designers actually work to.
The directive sets the obligation: products and services must meet accessibility requirements. Penalties must be effective, proportionate, and dissuasive. It does not define the technical standard directly. That is the role of EN 301 549.
Each member state transposed the EAA into national legislation. Germany enacted the BFSG, in force since June 28, 2025. France, Spain, the Netherlands, and others each have their own enforcement authority and penalty structure.
The harmonised European ICT accessibility standard defines what accessible means in practice. It incorporates WCAG 2.1 Level AA for web and mobile content. Conforming to EN 301 549 creates a presumption of EAA compliance.
50 success criteria across four principles: Perceivable, Operable, Understandable, Robust. This is what accessibility scanning tools test against. This is what enforcement agencies measure compliance by. WCAG 2.2 is current best practice, but WCAG 2.1 AA is the legal EAA standard.
Businesses covered by the EAA are required to provide clear and up-to-date accessibility information about their products and services. In practice, this obligation is implemented as an Accessibility Statement. Under EAA Article 13 and national transpositions such as Germany's BFSG §12, this information must include: conformance status (fully, partially, or non-conformant), a description of known limitations and reasons, a contact point for accessibility requests, the relevant enforcement authority link, and the date of last assessment. The statement must reflect the current state of the service at the date of publication. A statement describing your platform as it was six months ago does not satisfy this requirement. Accesstive's Accessibility Statement Generator produces statements in the required EAA and BFSG format and updates them as your compliance status changes.
The Enforcement Reality
The Full Platform
The Platform That Makes the VPAT Possible.
Every step feeds the next. Install, scan, fix, and prove. The VPAT is the output of the whole system.
01 Install
Accessibility Toolkit
User controls from day one.
Every visitor.
02 Find
Scanner
Every WCAG issue across your
full domain.
03 FIX
Fix Hub
Assign. Fix with AI.
Verify. Close.
04 PROVE
Audit Report
Audit Report
What Ongoing EAA Compliance Looks Like
An accessibility audit answers one question: what violations exist on this platform, at this moment. It does not cover next week's deploy. It does not document last month's remediation.
Every audit you commission has an expiry date. The moment your team ships a new product page, updates a checkout component, or installs a third-party script, the audit no longer reflects your platform. By the time an enforcement authority examines your site, the audit that seemed to cover you may be months out of date.
Ongoing EAA compliance requires three things to happen continuously, not once at the start of a project. Finding every violation after every deploy. Fixing issues at code level with documented evidence. Proving the current compliance state with a timestamped audit trail and an Accessibility Statement that reflects what is actually live.
This is the discipline Accesstive runs as a platform, through continuous accessibility monitoring, documented remediation, and compliance reporting that reflects the platform's current state.
How This Works in Practice
GKMB GmbH is a German business operating in the scope of the BFSG. When they engaged Accesstive, their platform carried violations across multiple WCAG 2.1 AA success criteria. Not from negligence, but from normal system changes over time.
Over 30 days, violations were identified and mapped against specific WCAG 2.1 AA criteria. Each issue was assigned and tracked through remediation. Every closure was verified against the original criterion and timestamped.
An Accessibility Statement was published covering all required BFSG fields: conformance status, known issues, contact point, Durchsetzungsverfahren link, and date of last assessment. The statement described the actual state of the platform at publication, not a projected or aspirational state.
GKMB now runs Accesstive as an ongoing discipline. New violations introduced by deploys are detected and tracked continuously. Compliance documentation reflects the current platform state.
The audit trail exists. The statement is current. The documentation is defensible. That is the only question that matters when an enforcement authority opens a case.
FAQs
No. The European Commission confirmed in December 2023 that no automated tool covers all WCAG 2.1 AA criteria. An overlay addresses surface-level issues but does not fix underlying code, does not cover keyboard navigation failures, and does not produce the documentation an enforcement authority will request.
Yes. The EAA covers any part of your digital service that EU consumers interact with, including checkout flows, account dashboards, and payment screens. The France enforcement actions specifically targeted checkout accessibility failures in e-commerce platforms.
Content published before June 28, 2025 that has not been edited since is exempt. Any new content published after that date must comply immediately. If you update archived content, the exemption no longer applies to those elements.
Yes. Each national regulator operates independently. A site serving France, Germany, and the Netherlands can face three parallel enforcement actions with no cross-border penalty cap. Germany's Bundesnetzagentur, France's DGCCRF, and the Netherlands' ACM each have independent jurisdiction.
Document your remediation effort immediately. Most enforcement authorities issue a notice before escalating. That notice is not an opportunity to delay, it is the window you have to show active remediation before the penalty phase begins. An active remediation programme and a published Accessibility Statement showing your current conformance status is your strongest protection at every stage.
No. The EAA references EN 301 549, which incorporates WCAG 2.1 AA as the legal standard. WCAG 2.2 is current best practice but not the legal EAA requirement.
The earlier directive applied only to public sector websites. The EAA extends obligations to private sector businesses including e-commerce, banking, transport, and SaaS. It covers more organisations and has active private-sector enforcement.
Every code deploy can introduce new WCAG 2.1 AA violations. A new product page with missing alt text, a checkout update breaking keyboard navigation, a third-party script introducing contrast failures. An audit completed before these changes does not cover the current state of your platform.
Your Audit Has an Expiry Date.
EAA enforcement is live across 27 member states. Every deploy without coverage is a new violation waiting to be found.