EAA Compliance
Overview
Guides compliance with the European Accessibility Act (EU Directive 2019/882) and the underlying technical standard EN 301 549. Covers scope, deadlines, exemptions, and enforcement across EU member states.
Instructions
When conducting an EAA/EN 301 549 compliance review:
Determine which law applies:
- Web Accessibility Directive (WAD) — public sector websites and mobile apps (already in force since 2020/2021)
- European Accessibility Act (EAA) — private sector products and services (enforced from 28 June 2025)
Identify if the product/service is in scope (see Products and Services section)
Evaluate against EN 301 549 v3.2.1, which incorporates WCAG 2.1 AA for web content (Clause 9) and extends to:
- Non-web documents (Clause 10)
- Non-web software / mobile apps (Clause 11)
- Hardware and self-service terminals (Clause 12-13)
Check exemptions — microenterprises, disproportionate burden, fundamental alteration
Provide remediation guidance with reference to specific EN 301 549 clauses
Recommend accessibility statement — required under both WAD and EAA
Products and Services in Scope (EAA)
Products
- Computers and operating systems
- Smartphones and tablets
- TV equipment and related services
- E-readers
- Self-service terminals (ATMs, ticket machines, check-in kiosks, payment terminals)
- Consumer telecommunication equipment
Services
- E-commerce websites and mobile apps
- Banking services (online and ATMs)
- E-books and dedicated software
- Audiovisual media services
- Transport services (websites, apps, ticketing, real-time travel info)
- Telephony and messaging services
EN 301 549 Structure
| Clause |
Scope |
Key Requirements |
| 5 |
Generic requirements |
Closed functionality, biometrics, preservation of accessibility |
| 6 |
ICT with two-way voice communication |
Real-time text (RTT), caller ID, video communication |
| 7 |
ICT with video capabilities |
Captions, audio description, player controls |
| 8 |
Hardware |
Physical dimensions, connections, keypads, biometrics |
| 9 |
Web content |
WCAG 2.1 Level AA (all success criteria) |
| 10 |
Non-web documents |
WCAG 2.1 AA applied to documents (PDFs, Word, spreadsheets) |
| 11 |
Non-web software |
WCAG 2.1 AA adapted for native apps and desktop software |
| 12 |
Documentation and support |
Accessible docs, help desk, support services |
| 13 |
ICT providing relay or emergency services |
Relay services, 112 emergency access |
Who Must Comply
| Law |
Sector |
Scope |
| Web Accessibility Directive (2016/2102) |
Public sector |
All EU public sector websites and mobile apps |
| European Accessibility Act (2019/882) |
Private + public |
Manufacturers, service providers, importers, distributors offering in-scope products/services in EU |
Territorial reach: Any organization offering in-scope services to EU consumers, regardless of where the organization is headquartered.
Deadlines
| Obligation |
Date |
| WAD — Public sector websites |
23 September 2020 |
| WAD — Public sector mobile apps |
23 June 2021 |
| EAA — All in-scope products and services |
28 June 2025 |
| EAA — Products placed on market before June 2025 |
Grace period until 28 June 2030 |
| EN 301 549 v4.1.1 (planned, includes WCAG 2.2) |
Expected 2026 |
Exemptions
- Microenterprises — fewer than 10 employees AND annual turnover ≤ €2 million (EAA only)
- Disproportionate burden — documented assessment required; does not exempt from all requirements
- Fundamental alteration — compliance would change the nature of the product/service
- Third-party content — not funded, developed, or controlled by the economic operator
- Archived content — not updated after 28 June 2025
Penalties
Enforcement is per member state. Examples:
| Country |
Penalty |
| General range |
Up to €500,000 in fines |
| Some states |
Product removal from market |
| At least one state |
Criminal penalties possible |
Penalties must be "effective, proportionate, and dissuasive."
Presumption of Conformity
Products/services conforming to harmonised European standards (notably EN 301 549) benefit from a "presumption of conformity" — they are presumed to meet EAA requirements without further proof.
Accessibility Statement
Both WAD and EAA require publishing an accessibility statement that includes:
- Scope of content covered
- Standard used (EN 301 549)
- Level of conformance achieved
- Known limitations with rationale
- Contact mechanism for reporting barriers
- Link to enforcement procedure
Examples
Example: E-commerce Audit
Input: "Our online store sells to EU customers, what do we need?"
Response approach:
- Confirm the store is in scope (e-commerce service)
- Check for microenterprise exemption
- Audit website against EN 301 549 Clause 9 (= WCAG 2.1 AA)
- Audit mobile app against Clause 11 if applicable
- Check self-service terminals (kiosks) against Clause 8 if applicable
- Verify accessibility statement is published
Example: SaaS Product
Input: "We're a US company with EU customers, does EAA apply?"
Response approach:
- Yes — EAA applies to any organization offering in-scope services to EU consumers
- Determine which product/service categories apply
- Audit against EN 301 549 (not just WCAG)
- Note that EN 301 549 covers software (Clause 11), not just web content
Guidelines
- Always determine WAD vs EAA applicability first — different obligations and history
- Reference EN 301 549 clause numbers, not just WCAG criteria, when reporting issues
- EN 301 549 is broader than WCAG — covers hardware, RTT, biometrics, documentation
- Note that EN 301 549 v4.1.1 (expected 2026) will incorporate WCAG 2.2
- Microenterprise exemption applies only to EAA, not to WAD
- Never recommend overlay widgets as a compliance solution
References
1---2name: eaa-compliance3description: Use when auditing digital products or services for European Accessibility Act (EAA) compliance, checking EN 301 549 conformance, or advising on EU Web Accessibility Directive obligations.4---56# EAA Compliance78## Overview910Guides compliance with the European Accessibility Act (EU Directive 2019/882) and the underlying technical standard EN 301 549. Covers scope, deadlines, exemptions, and enforcement across EU member states.1112## Instructions1314When conducting an EAA/EN 301 549 compliance review:15161. **Determine which law applies:**17 - **Web Accessibility Directive (WAD)** — public sector websites and mobile apps (already in force since 2020/2021)18 - **European Accessibility Act (EAA)** — private sector products and services (enforced from 28 June 2025)19202. **Identify if the product/service is in scope** (see Products and Services section)21223. **Evaluate against EN 301 549 v3.2.1**, which incorporates WCAG 2.1 AA for web content (Clause 9) and extends to:23 - Non-web documents (Clause 10)24 - Non-web software / mobile apps (Clause 11)25 - Hardware and self-service terminals (Clause 12-13)26274. **Check exemptions** — microenterprises, disproportionate burden, fundamental alteration28295. **Provide remediation guidance** with reference to specific EN 301 549 clauses30316. **Recommend accessibility statement** — required under both WAD and EAA3233## Products and Services in Scope (EAA)3435### Products36- Computers and operating systems37- Smartphones and tablets38- TV equipment and related services39- E-readers40- Self-service terminals (ATMs, ticket machines, check-in kiosks, payment terminals)41- Consumer telecommunication equipment4243### Services44- E-commerce websites and mobile apps45- Banking services (online and ATMs)46- E-books and dedicated software47- Audiovisual media services48- Transport services (websites, apps, ticketing, real-time travel info)49- Telephony and messaging services5051## EN 301 549 Structure5253| Clause | Scope | Key Requirements |54|---|---|---|55| 5 | Generic requirements | Closed functionality, biometrics, preservation of accessibility |56| 6 | ICT with two-way voice communication | Real-time text (RTT), caller ID, video communication |57| 7 | ICT with video capabilities | Captions, audio description, player controls |58| 8 | Hardware | Physical dimensions, connections, keypads, biometrics |59| 9 | Web content | WCAG 2.1 Level AA (all success criteria) |60| 10 | Non-web documents | WCAG 2.1 AA applied to documents (PDFs, Word, spreadsheets) |61| 11 | Non-web software | WCAG 2.1 AA adapted for native apps and desktop software |62| 12 | Documentation and support | Accessible docs, help desk, support services |63| 13 | ICT providing relay or emergency services | Relay services, 112 emergency access |6465## Who Must Comply6667| Law | Sector | Scope |68|---|---|---|69| **Web Accessibility Directive (2016/2102)** | Public sector | All EU public sector websites and mobile apps |70| **European Accessibility Act (2019/882)** | Private + public | Manufacturers, service providers, importers, distributors offering in-scope products/services in EU |7172**Territorial reach:** Any organization offering in-scope services to EU consumers, regardless of where the organization is headquartered.7374## Deadlines7576| Obligation | Date |77|---|---|78| WAD — Public sector websites | 23 September 2020 |79| WAD — Public sector mobile apps | 23 June 2021 |80| EAA — All in-scope products and services | **28 June 2025** |81| EAA — Products placed on market before June 2025 | Grace period until 28 June 2030 |82| EN 301 549 v4.1.1 (planned, includes WCAG 2.2) | Expected 2026 |8384## Exemptions8586- **Microenterprises** — fewer than 10 employees AND annual turnover ≤ €2 million (EAA only)87- **Disproportionate burden** — documented assessment required; does not exempt from all requirements88- **Fundamental alteration** — compliance would change the nature of the product/service89- **Third-party content** — not funded, developed, or controlled by the economic operator90- **Archived content** — not updated after 28 June 20259192## Penalties9394Enforcement is per member state. Examples:9596| Country | Penalty |97|---|---|98| General range | Up to €500,000 in fines |99| Some states | Product removal from market |100| At least one state | Criminal penalties possible |101102Penalties must be "effective, proportionate, and dissuasive."103104## Presumption of Conformity105106Products/services conforming to **harmonised European standards** (notably EN 301 549) benefit from a "presumption of conformity" — they are presumed to meet EAA requirements without further proof.107108## Accessibility Statement109110Both WAD and EAA require publishing an accessibility statement that includes:111- Scope of content covered112- Standard used (EN 301 549)113- Level of conformance achieved114- Known limitations with rationale115- Contact mechanism for reporting barriers116- Link to enforcement procedure117118## Examples119120### Example: E-commerce Audit121122**Input:** "Our online store sells to EU customers, what do we need?"123124**Response approach:**1251. Confirm the store is in scope (e-commerce service)1262. Check for microenterprise exemption1273. Audit website against EN 301 549 Clause 9 (= WCAG 2.1 AA)1284. Audit mobile app against Clause 11 if applicable1295. Check self-service terminals (kiosks) against Clause 8 if applicable1306. Verify accessibility statement is published131132### Example: SaaS Product133134**Input:** "We're a US company with EU customers, does EAA apply?"135136**Response approach:**1371. Yes — EAA applies to any organization offering in-scope services to EU consumers1382. Determine which product/service categories apply1393. Audit against EN 301 549 (not just WCAG)1404. Note that EN 301 549 covers software (Clause 11), not just web content141142## Guidelines143144- Always determine WAD vs EAA applicability first — different obligations and history145- Reference EN 301 549 clause numbers, not just WCAG criteria, when reporting issues146- EN 301 549 is broader than WCAG — covers hardware, RTT, biometrics, documentation147- Note that EN 301 549 v4.1.1 (expected 2026) will incorporate WCAG 2.2148- Microenterprise exemption applies only to EAA, not to WAD149- Never recommend overlay widgets as a compliance solution150151## References152153- European Accessibility Act: https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en154- EN 301 549 v3.2.1 (PDF): https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf155- Web Accessibility Directive: https://digital-strategy.ec.europa.eu/en/policies/web-accessibility156- WCAG 2.1: https://www.w3.org/TR/WCAG21/
beshkenadze