European Accessibility Act — practical checklist (EU)
Framework, scope, harmonised standards (EN 301 549, typical WCAG 2.1 Level AA), key dates under Directive (EU) 2019/882, and an operational checklist for teams placing covered products or services on the EU market.
This page is informational only and does not constitute legal, compliance, or accessibility auditing advice. Deadlines, scope, exemptions, and conformity depend on EU Member State transposition and Commission acts. It does not address Turkish law — switch the site to Türkçe for the national checklist.
European Union — Directive (EU) 2019/882 (EAA)
The European Accessibility Act harmonises essential accessibility requirements for specific products and services traded in the internal market. It aims to improve functioning of the market and remove barriers for persons with disabilities and older people. Requirements are backed by harmonised standards (notably EN 301 549) and EU-wide market surveillance.
Material scope (high-level examples)
Non-exhaustive product examples commonly discussed under the Directive:
- General-purpose computer hardware systems and their operating systems (where in scope).
- Self-service terminals such as payment machines, ATMs, ticketing/check‑in kiosks, and certain interactive information terminals (with exclusions, e.g. integrated into vehicles).
- Consumer terminal equipment with interactive computing capability for electronic communications or audio-visual media access.
- E-readers.
Non-exhaustive service examples:
- Electronic communications services (with exclusions such as machine-to-machine only).
- Services providing access to audio-visual media.
- Passenger transport services — air, bus, rail and waterborne; includes websites/apps, e-ticketing and real-time travel information (urban/suburban/regional nuance for terminals).
- Consumer banking services.
- E-books and dedicated reading software.
- E-commerce services.
The Directive also covers accessibility of the single European emergency number 112 in specified ways. Built-environment accessibility may be optional or complementary depending on context. Passenger-transport and terminal rules contain detailed carve-outs — use the official legal text and national guidance for precise boundaries.
Standards & presumption of conformity
Harmonised standard EN 301 549 specifies detailed functional accessibility requirements for ICT products and services. For web content it incorporates WCAG 2.1 Level AA success criteria. Using harmonised standards can support presumption of conformity when the references are published in the Official Journal and correctly applied. EN 301 549 continues to evolve (e.g. updates toward WCAG 2.2 alignment are under discussion in standardisation) — monitor the citation in the Journal and your notified body guidance.
Key application milestones (Directive text)
- 28 June 2025Primary date from which new or updated products and services within scope must comply when placed on the Union market.
- 28 June 2027Further deadline related to specific emergency-services accessibility elements under the Directive.
- 28 June 2030End of transition for many goods and services lawfully placed on the market before 28 June 2025 (subject to exceptions and product-specific rules).
- 28 June 2045 / 20-year ruleLong-life self-service terminals — maximum period as defined in the Directive (whichever is earlier: date or 20 years from installation).
Micro-enterprises & proportionality
The Directive includes exceptions and proportionality mechanisms. Certain micro-enterprises that provide services may fall under exemptions defined in the text and clarified by member states — thresholds relate to staff headcount and financial ceilings. Manufacturer obligations for products generally differ from service-provider flexibility. Confirm each entity against the transposed national law in every Member State where you operate.
Transparency & accessibility statements
For relevant services, providers must supply accessibility information and compliance details in line with Commission implementing acts (format, updates, enforcement cooperation). Plan for a maintained statement, a feedback mechanism, and documentation for market surveillance authorities.
Operational checklist (EU / EAA)
Use as an internal pre-audit; pair each row with your counsel and notified-body strategy for the Member States where you operate.
| Control area | Guidance (EAA · EN 301 549 · typical WCAG 2.1 AA testing) |
|---|---|
| Assign accessibility ownership, budget, and issue SLAs. | Market surveillance may ask who maintains the performance statement and corrective action logs; procurement of covered ICT should bake in EN 301 549 acceptance criteria. |
| Maintain a conformity file (tests, WCAG reports, assistive-tech spot checks). | Supports presumption of conformity and cooperation with national authorities; tie evidence to essential requirements and harmonised standards cited in the OJ. |
| Contractual flow-down to vendors & embedments (payments, maps, chat). | EAA liability chain includes integrated third-party services for many consumer-facing offers — secure accessibility KPIs in DPAs. |
| Control area | Guidance (EAA · EN 301 549 · typical WCAG 2.1 AA testing) |
|---|---|
| Text alternatives for non-text content; captions & audio description strategy. | Maps to WCAG 2.1 AA via EN 301 549 Chapter 9 (including media) for web/document scopes. |
| Colour contrast, resize & reflow up to 400 %, orientation support. | 1.4.3, 1.4.4, 1.4.10 are routine audit lines for web conformity. |
| Structured headings, lists, and landmarks for complex layouts. | Supports ‘adaptable’ requirements in EN 301 549 and eases statement of partial conformity. |
| Control area | Guidance (EAA · EN 301 549 · typical WCAG 2.1 AA testing) |
|---|---|
| Full keyboard operability, visible focus, correct focus order. | WCAG 2.1 AA 2.1.x / 2.4.3 remain central for conformity testing. |
| Motion, timing, gestures — provide alternatives & user control. | 2.2.x, 2.5.x increasingly scrutinised for mobile apps under EU surveillance pilot programmes. |
| Control area | Guidance (EAA · EN 301 549 · typical WCAG 2.1 AA testing) |
|---|---|
| Form labels, instructions, error identification & suggestions. | 3.3.x sets are mandatory for transactional e-commerce and banking journeys. |
| Consistent navigation, language of parts, predictable components. | 3.2.x supports essential requirement on ease of use for assistive technologies. |
| Valid name, role, value for custom components; status announcements. | 4.1.2 / 4.1.3 align with EN 301 549 interoperability clauses. |
| Control area | Guidance (EAA · EN 301 549 · typical WCAG 2.1 AA testing) |
|---|---|
| Publish and maintain a user-facing accessibility statement / feedback route. | Directive Art. 13 and Annex V set accessibility information duties; Commission delegated/implementing acts and member state rules define the exact format — align your statement template with OJ‑cited acts for each market. |
| Prepare remediation playbooks for market surveillance findings or ministry orders. | National authorities can enforce penalties; demonstrate good-faith correction timelines. |
Accsiblehelps visitors adjust presentation and can support WCAG-oriented fixes, but it does not replace conformity assessment, EN 301 549 evidence packs, or legal analysis of whether the EAA applies to your offering in a given Member State.
