Legal & Compliance

The European Accessibility Act at One Year: Enforcement Begins

One year after the EAA became enforceable, the first actions have landed — formal notices, inspections, court orders, and daily penalties across the EU.

Khushwant Parihar
5 min read

The European Accessibility Act (EAA, Directive (EU) 2019/882) became enforceable on June 28, 2025. One year on, the first enforcement actions have arrived — though confirmed monetary fines under national EAA-implementing laws remained rare. Early enforcement has centered on complaints, inspections, formal notices, market surveillance, and corrective-action deadlines rather than immediate penalties. The pattern so far is notice, then investigation, then required fixes, with fines as a later step. Two developments stand out: a French court order against Carrefour, and daily penalties in Norway.

What the EAA requires

The EAA sets accessibility requirements for a range of products and services sold in the EU, including e-commerce, banking, transport, and e-books. Its technical baseline is the harmonized standard EN 301 549, which incorporates WCAG 2.1 Level AA. There is a limited exemption for microenterprises providing services, but the reach is broad — and it is not confined to companies headquartered in Europe.

France: formal notices, then a court order

In November 2025, France’s DGCCRF — the consumer and competition authority — sent formal enforcement notices to four major retailers: Auchan, Carrefour, E.Leclerc, and Picard. Inspections had found systematic problems: keyboard-navigation failures, missing alternative text, and non-compliant checkout flows.

In June 2026, the Carrefour matter was heard, and a French court ordered Carrefour France to make both its e-commerce website and its mobile application fully accessible to people with disabilities within six months — under penalty of a fine for each day of delay. It has been described as an early EAA-era court ruling, and it underlines a key point: accessibility obligations extend beyond the website to the mobile app.

Norway: daily penalties

Norway’s equality and anti-discrimination authority imposed a daily penalty of NOK 50,000 — about EUR 4,500 per day — on the HelsaMi health portal operated by Norsk Helsenett, over persistent keyboard-accessibility failures. The case illustrates how the enforcement escalates: authorities generally issue a notice, investigate, and demand corrective action, with recurring daily penalties applied when problems persist.

The typical enforcement pattern is notice, then investigation, then corrective action — with fines as a later step, not a first resort.

A recurring theme: keyboard access

Across the French inspections and the Norwegian penalty, keyboard-navigation failures appear again and again — alongside missing alternative text and broken checkout flows. These are foundational, well-understood barriers, and they map directly to WCAG success criteria. A structured WCAG checklist helps teams catch exactly these issues before an inspector does.

What this means for you

If you sell to consumers in the EU, the EAA can apply to you — even if your company is based in the United States or elsewhere outside Europe. That is the single most important takeaway for non-EU businesses. E-commerce is squarely in scope, and the early enforcement has landed heavily on online retail.

  1. Confirm your exposure. If EU consumers can buy your products or use your services, assume the EAA is relevant and check whether the microenterprise exemption applies to you.
  2. Test the whole journey. The Carrefour order covered both website and mobile app. Cover your full purchase flow — browsing, search, cart, and checkout — on both surfaces.
  3. Fix keyboard access first. It is the most commonly cited failure and among the most straightforward to verify. Ensure every interactive element is reachable and operable by keyboard alone.
  4. Measure against EN 301 549 / WCAG 2.1 AA. That is the standard authorities are applying, so it is the standard to build and test toward.

For deeper background, see our overview of the European Accessibility Act and our reference on accessibility laws worldwide.

The bottom line

A year in, EAA enforcement is real but still ramping. Big fines under national implementing laws remain uncommon, yet the machinery — inspections, formal notices, court orders, and daily penalties — is clearly in motion, and it is reaching household-name retailers. Organizations that treat WCAG 2.1 AA as the working standard, test both web and mobile, and start with keyboard access will be well ahead of the enforcement curve.

This article is general information, not legal advice.

Sources

Written by
Khushwant Parihar

Khushwant Parihar is the founder of Accessibility.build and an accessibility specialist, consultant, and developer with more than four years of professional accessibility and software testing experience. His work covers WCAG auditing, keyboard and screen-reader testing with NVDA, JAWS, and VoiceOver, accessible frontend implementation, remediation workflows, and team enablement.

Found this useful? Share it.

Prefer Accessibility.build on Google

Add us as a preferred source and Google will show our new articles and research more often in your Top Stories and AI Overviews.

Add as a preferred source on Google

Essential Accessibility Resources

Comprehensive tools, checklists, and guides to help you create inclusive digital experiences

Top Pick

European Accessibility Act (EAA) Guide

EAA compliance requirements, deadlines, scope, and how it relates to EN 301 549 and WCAG
eaa
european accessibility act
eu accessibility
+1 more
View guide
Top Pick

Accessibility Laws by Jurisdiction

Global tracker of accessibility laws comparing WCAG requirements, penalties, and enforcement across 21 jurisdictions
european accessibility act
eaa
accessibility compliance
View resource
Top Pick

European Accessibility Act Tracker

Every EAA statutory date quoted from Directive (EU) 2019/882, national transposition measures for all 27 Member States, and the status of enforcement data
european accessibility act
eaa enforcement
View resource

Other posts filed under Legal & Compliance.

  • NFB v. DOJ: Could a Court Restore the Original Title II and Section 504 Web Deadlines?

    The National Federation of the Blind is asking a Maryland federal court to throw out the one-year extensions DOJ and HHS gave to the Title II and Section 504 web accessibility deadlines. We read the docket, the complaint and both interim final rules: what “good cause” means, what vacatur would do to dates that have already passed, and why you should not plan around the extension.

    Nov 18, 2026 · 14 min read

  • Website ADA Suits Keep Failing on Standing. That Does Not Make Your Site Accessible.

    A Chicago federal judge threw out a website accessibility suit against a shoe retailer in October 2026 because the blind plaintiff offered no evidence of standing. We read the opinion and the appellate cases behind it. Here is what standing means, why these wins are narrower than they look, and why the defendants who win tend to be the ones who had already fixed their sites.

    Nov 18, 2026 · 15 min read

  • ADA Title II After the Extension: Put Accessibility Into Your Vendor Contracts Now

    The DOJ gave state and local governments an extra year, but the Title II web rule still covers every website and app a public entity provides through a vendor. Here is what to write into contracts, how to read a vendor’s ACR without being fooled by a wall of “Supports”, and a clause checklist drawn from the rule, ADA.gov, GSA and Idaho.

    Nov 18, 2026 · 16 min read