Global digital inclusion accessibility law

A Better Accessibility Standard Arrives Before Any EAA Enforcement Model Has Proven Itself

EN 301 549 v4.1.1 gives firms a clearer route to EAA compliance, but with no fines yet confirmed, regulators should prove proportionate enforcement before escalating.

EN 301 549 v4.1.1 and EAA enforcement People of Internet Research · Global 2 Sep 2026 Standard published ETSI, CEN and CENELEC released v4.… 16 Dec 2026 Expected OJ citation Citation triggers presumption of c… 0 Confirmed EAA fines None confirmed under national laws… 124 Swedish public complaints 110 on services, 14 on products. peopleofinternet.com
EN 301 549 v4.1.1 and EAA enforcement People of Internet Research · Global 2 Sep 2026 Standard published 16 Dec 2026 Expected OJ citation 0 Confirmed EAA fines 124 Swedish public complaints peopleofinternet.com

Key Takeaways

On 2 September 2026, ETSI, CEN and CENELEC published EN 301 549 v4.1.1, the updated European standard for accessibility of ICT products and services. Ireland's National Disability Authority (NDA) says it is expected to be cited in the Official Journal on 16 December 2026. That date matters more than the publication date, because citation is what converts a technical document into a legal safe harbour. The standard arrives while enforcement of the European Accessibility Act (EAA) is still mostly administrative.

What actually changed

The headline change is technical. According to the NDA, the web-content baseline moves from WCAG 2.1 to WCAG 2.2 at Level AA, and the clauses for web content, non-web documents and software now reference WCAG 2.2. The NDA also describes v4.1.1 as the first version developed specifically with the EAA in mind. It adds an annex that maps the standard's clauses to the Act's essential requirements, and it updates the equivalent annex for the Web Accessibility Directive.

Law firm Davis Wright Tremaine summarises the legal position: the standard was formally adopted on 24 August 2026 and published on 2 September, but its most significant legal effect will not occur until it is cited in the Official Journal. Once that happens, compliance gives a presumption of conformity with the corresponding EAA requirements. Until then, the NDA says, the version in force remains v3.2.1 (2021), built on WCAG 2.1, and there is no immediate compliance deadline attached to the release.

The strongest case for tougher enforcement

The argument for a hard line deserves a fair hearing. Accessibility rules exist because voluntary effort has repeatedly failed disabled users, who still hit inaccessible checkout flows, unlabelled buttons and ATMs they cannot operate. Rights that are not enforced tend to be treated as optional. A regulator that never fines may teach firms that compliance is a cost to be deferred, and a firm that invests early can be undercut by one that does not.

That concern is not hypothetical. The EAA's national penalty ceilings are substantial. Level Access, an accessibility vendor with a commercial interest in the topic, lists them: up to €100,000 per violation in Germany, up to €1 million in Spain and Italy, and up to €900,000 or 10% of annual revenue in the Netherlands. Ireland's penalty is up to €60,000 plus up to six months' imprisonment.

What the enforcement record shows

The same Level Access report states that, as of mid-2026, no monetary fines have been confirmed under any EAA-transposed national law. It describes the first year as one of formal notices, civil society lawsuits and regulatory monitoring. It adds that regulators generally move from notification to remediation orders before imposing financial penalties. One example is a French court order requiring Carrefour France to make its services accessible, with six months to comply and a daily fine for delay. That fine is conditional, not imposed. Sweden's regulator PTS has received 124 public complaints, 110 about services (mostly e-retail sites) and 14 about products such as ATMs.

We read this record as a system working roughly as it should, not one failing. Notice, remediation, and only then penalty is the proportionate sequence. It gets accessibility fixed, which is the actual goal, without turning a standards transition into a litigation lottery.

Why the timing of the standard matters

The uncomfortable fact is that firms have been required to meet the Act's essential requirements while the harmonised standard that would give them certainty was still the 2021 version. Moving to WCAG 2.2 raises the bar. A company that built to WCAG 2.1 may now face a gap, even though the NDA is clear that nothing changes legally until citation. Firms, especially smaller ones, face a real planning problem: build to the old baseline, the new one, or both.

The annex mapping clauses to EAA requirements is the most useful innovation here. It lets a developer or procurement officer trace a specific technical test to a specific legal duty, which reduces the guesswork that drives defensive, over-cautious compliance spending. The NDA also points to the ETSI procurement technical report TR 101 551 as a resource, which matters because public buyers shape what vendors build.

What regulators and firms should do

First, regulators should publish a clear transition position before 16 December. A short statement that conformity with either v3.2.1 or v4.1.1 will be treated as good faith evidence during an initial period would cost nothing and prevent disputes over which WCAG version applies. We note that no authority has yet announced such a position that we could verify, so this is a recommendation, not a report.

Second, penalties should follow documented, uncured failures, not isolated defects. Websites change daily, and automated scanners flag trivial issues. An enforcement culture that counts scanner hits will reward consultants and punish small operators. One that prioritises barriers to core tasks such as paying, booking or signing in helps users.

Third, firms should treat WCAG 2.2 as the working target now. The cost of building to the higher baseline today is lower than retrofitting after citation, and the user-facing improvements are real.

Fourth, other jurisdictions watching Europe should note the design choice. Pairing a technical standard with a presumption of conformity gives industry a predictable path while preserving the regulator's power to act. That is a more innovation-friendly model than open-ended duties enforced by private litigation.

Bottom line

EN 301 549 v4.1.1 is a genuine improvement, and the apparent absence of publicly reported fines so far is not evidence of regulatory failure. It is evidence that the EAA is still in its calibration phase. The risk is that this phase ends abruptly, with penalties arriving before the standard that defines compliance is legally settled. Regulators who keep to the notice-and-remediate sequence, and who say plainly how they will treat the two standard versions in the interim, will get more accessibility per euro spent than those who race to publish a first fine.

Sources & Citations

  1. NDA: Updated EN 301 549 Standard
  2. ETSI: EN 301 549 V4.1.1 (PDF)
  3. Davis Wright Tremaine: New Technical Standard for EAA Compliance
  4. Level Access: EAA compliance in 2026 enforcement update