The European Accessibility Act explained

What the EAA is

The European Accessibility Act is Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services. Its goal is to remove barriers created by different accessibility rules in each Member State, by setting common EU-wide accessibility requirements for products and services that are most important for people with disabilities.

Because it is a directive, it does not apply directly: each EU Member State had to transpose it into national law (the deadline was 28 June 2022), and the national laws apply the harmonised requirements from 28 June 2025.

Who is covered

The EAA covers these products when placed on the EU market:

• consumer general purpose computers and operating systems
• smartphones and other consumer terminal equipment with interactive computing capability, used for electronic communications or to access audiovisual media services
• self-service terminals such as ATMs, ticketing machines and check-in machines
• e-readers
• TV equipment related to digital television services

And these services when provided to consumers in the EU:

• e-commerce services
• consumer banking services
• electronic communications services, including emergency communications
• transport: elements of air, bus, rail and waterborne passenger transport services, such as websites, apps and electronic tickets
• e-books and dedicated software
• services providing access to audiovisual media services

For most digital teams, the practical effect is this: if you sell to consumers online in the EU, if you provide consumer banking or telecom services, or if you run passenger transport services, your website and apps are in scope.

Key dates

Exemptions and exceptions

The EAA is not absolute. Three points matter in practice:

• Microenterprises providing services (fewer than 10 employees and an annual turnover or balance sheet total not exceeding €2 million) are exempt from the service requirements. This exemption does not apply to products.
• Disproportionate burden: a provider can be excused from a requirement if meeting it would impose a disproportionate burden, after assessing the costs and the benefits for people with disabilities.
• Fundamental alteration: a requirement does not apply if it would fundamentally change the nature of the product or service.

These exceptions are narrow, must be assessed, and do not remove the duty to provide accessible alternatives where possible. They are not a shortcut around accessibility.

Enforcement and penalties

The directive does not set a single EU fine. Each Member State must lay downpenalties that are effective, proportionate and dissuasive, and must designate market surveillance or compliance authorities to check compliance and handle complaints. That is why penalties differ by country — from administrative orders to require fixes, to fines that can reach tens or hundreds of thousands of euros for serious or repeated breaches.

Enforcement usually starts with a complaint or an inspection. Providers are typically given a chance to fix the problem; fines and other measures follow when they do not. Keeping an accurate, up-to-date accessibility statement and a working feedback channel is one of the simplest ways to show good faith and to make complaints easier to resolve early.

How an accessibility statement fits

The EAA requires accessible services, not paperwork. But several national implementations and sector rules expect providers to give consumers information about accessibility and how to report problems, and public sector rules in the EU already require a published accessibility statement. A statement is the standard, human-readable page that:

• states your commitment and the standard you follow (for example WCAG 2.2 AA);
• describes your actual conformance status, honestly, including known limitations;
• gives a clear feedback channel — email, phone or a form — and a response promise;
• explains how accessibility was assessed; and
• names the legal framework and, where relevant, the authority a visitor can escalate to.

That is exactly the structure the AccessProof generatorproduces, following the W3C accessibility statement guidance.

WCAG 2.2 AA and EN 301 549

EN 301 549 is the European harmonised standard for accessibility requirements for ICT products and services. It is how the EAA's requirements are given technical substance. Its current version, EN 301 549 v3.2.1, is based on WCAG 2.1 Level AA, and it is the version currently referenced for demonstrating conformity with the EAA.

In September 2026 a new version, EN 301 549 v4.1.1, was published. It adopts WCAG 2.2 and adds an annex linking its requirements directly to the EAA. It is not yet the legal reference standard until the European Commission cites it in the Official Journal, but it shows the direction of travel: WCAG 2.2 is the future baseline.

In practice, aiming for WCAG 2.2 Level AA is the safest target. It satisfies the WCAG 2.1 AA baseline used today and prepares you for the transition. The generator defaults to WCAG 2.2 AA for that reason, and also offers Level A and Level AAA wording.

National implementation

Transposition looks different in every country. These are the main laws and frameworks that the generator can reference for you:

Practical checklist

1. Confirm whether you are in scope (sector, consumers, size).
2. Pick a target: WCAG 2.2 Level AA, tested with automated and manual checks.
3. Fix the highest-impact barriers first: keyboard access, contrast, forms, alt text, headings, captions.
4. Publish an accessibility statement and link it from every page footer.
5. Give a feedback channel and respond to reports.
6. Review and update the statement at least once a year, or whenever your site changes significantly.

Sources: Directive (EU) 2019/882 (EUR-Lex); European Commission, European Accessibility Act overview; national transposition texts (BFSG, S.I. No. 636/2023, Implementatiewet toegankelijkheidsvoorschriften producten en diensten); GOV.UK accessibility guidance; AccessibleEU news on EN 301 549 v4.1.1 (September 2026).