What is the EAA?
The European Accessibility Act (Directive (EU) 2019/882) harmonizes accessibility requirements for key products and services across EU Member States. It aims to remove market fragmentation and improve access for people with disabilities and older persons.
Covers
- E-commerce & digital services
- Banking & payment services
- Transport ticketing/check-in interfaces
- Computers, smartphones, TV/AV equipment
- E-books & related software
Timeline
- Transposition deadline: 28 June 2022
- Enforcement: 28 June 2025
Who needs to comply?
Manufacturers, importers, distributors, service providers, and suppliers offering covered products or services in the EU—regardless of where they are based—must meet EAA requirements for the relevant scope.
What does achieving EAA compliance mean?
The EAA sets functional accessibility requirements and references European harmonized standards. For digital products and services, the primary standard is EN 301 549, which aligns with WCAG principles for web and software.
At a glance
- Use EN 301 549 as your technical baseline.
- Map requirements to WCAG success criteria for web/mobile.
- Include documentation and support accessibility (e.g., alternative formats).
The consequences of not complying
Member States monitor compliance and can impose penalties, restrict market access, or require corrective actions for non-conforming products or services.
EAA vs. Section 508 / ADA
| Feature | EAA (EU) | Section 508 (USA) | ADA (USA) |
|---|---|---|---|
| Scope | Products & services (selected sectors) | Federal ICT (agencies/contractors) | Public accommodations; broad coverage |
| Standards | EN 301 549 (WCAG-aligned) | WCAG 2.0 AA (via 508 refresh) | Courts/DOJ often reference WCAG 2.0/2.1 AA |
| Enforcement | By EU Member States (from 2025) | Federal procurement & oversight | Civil rights enforcement/litigation |
How can you know if you meet EAA requirements?
Run accessibility evaluations against EN 301 549/WCAG, combine automated testing with manual assistive-technology checks, and document findings and remediation steps.
Best practices
- Integrate accessibility requirements in design/dev from the start.
- Use semantic HTML, keyboard-accessible components, and ARIA carefully.
- Provide captions/transcripts, adequate color contrast, and resize support.
- Continuously test with users and assistive technologies.
- Maintain documentation and an accessibility statement with feedback channels.