EAA reality check, Part 1: France and the grocery-four lawsuits
The biggest shift after June 2025 is not rhetorical. It is operational. Under the EAA, accessibility moves from "optional backlog debt" to market-compliance work tied to regulator scrutiny.
What Changed After June 28, 2025
The European Commission states that the European Accessibility Act became applicable on June 28, 2025. That date is the practical line between preparation and enforcement.
For teams shipping digital services in the EU, this means accessibility evidence must be maintained continuously, not assembled only after a complaint arrives.
Why France Matters As An Enforcement Signal
France is a useful signal market because consumer-rights enforcement is active and reputational consequences can move faster than formal penalties. Even when legal processes differ across member states, the business impact pattern is similar:
- user-reported barriers escalate quickly
- regulatory attention follows visible service failures
- organizations with weak documentation lose credibility first
The immediate lesson is that "partial progress" may not prevent enforcement if core tasks remain inaccessible.
Practical Standard For 2026
If you serve EU users, your baseline should be:
- documented conformance target (for most teams: WCAG 2.2 AA)
- recurring testing against critical user journeys
- a maintained accessibility statement and remediation tracker
- named accountable owners by function (design, engineering, QA, content)
Claim-level Citation Notes
- Claim: EAA became applicable from June 28, 2025.
- Source: European Commission announcement (June 27, 2025)
- Claim: EAA defines covered products/services and creates accessibility obligations.
- Source: Directive (EU) 2019/882, Article 2
- Claim: Member states must establish penalties for infringements.
- Source: Directive (EU) 2019/882, Article 30
- Claim: The directive sets the compliance application timeline used by member states.
- Source: Directive (EU) 2019/882, Article 31
- Claim: WCAG 2.2 is the core technical benchmark for conformance work.
- Source: W3C WCAG 2.2 Recommendation