What is the European Accessibility Act?
What is the European Accessibility Act (Directive 2019/882)? Who it applies to, what it covers, what websites and apps must do, how it is enforced.
Short answer
The European Accessibility Act — Directive (EU) 2019/882 — is the EU law that requires common products and consumer services, including online shops, banking, transport booking and e-books, to be usable by people with disabilities. It has applied since 28 June 2025 through each country's national law. For websites and apps it means meeting the accessibility standard EN 301 549 (WCAG 2.1 Level AA today) and publishing how the service meets the requirements.
- Legal instrument
- Directive (EU) 2019/882
- Applies since
- 28.06.2025
- Services exempt
- Microenterprises (< 10 staff, ≤ €2M)
- Web standard today
- EN 301 549 v3.2.1 · WCAG 2.1 AA
- Next version
- EN 301 549 v4.1.1 · WCAG 2.2 AA
- Homepages with a barrier
- 81.3% of 3,754 (EU, 2026)
What is the European Accessibility Act?
The European Accessibility Act (EAA) is Directive (EU) 2019/882. It sets one list of accessibility requirements for a group of everyday products and consumer services, so that a business selling across the EU meets one set of rules instead of 27 different ones. This guide explains what the law covers, what it asks of a website or app, and how to start. It is a summary of the Directive, not legal advice; the law that applies to you is your country's national law that transposes it.
Key dates
| Date | What happened |
|---|---|
| 17 April 2019 | The Directive is adopted |
| 28 June 2022 | Deadline for EU countries to write it into national law |
| 28 June 2025 | The requirements apply to products placed on the market and services provided from this date |
| 28 June 2030 | End of the longest transition for existing service contracts |
Service contracts agreed before 28 June 2025 may continue unchanged until they expire, but for no longer than five years from that date. Self-service terminals already in use, such as ticket machines, may stay in use until the end of their economic life, up to 20 years.
Who it applies to
The Act applies to "economic operators": manufacturers, importers and distributors of covered products, and providers of covered services to consumers. A business outside the EU is covered when it sells those products or services to people in the EU.
One exemption matters to many small sites: microenterprises that provide services are exempt from the accessibility requirements for those services. The Directive defines a microenterprise as one that employs fewer than 10 persons and has an annual turnover or an annual balance sheet total of no more than €2 million. The exemption does not cover products: a small manufacturer still has to meet the product requirements, with lighter paperwork.
Which products and services
Products:
- consumer computers and their operating systems;
- payment terminals and self-service terminals: ATMs, ticketing and check-in machines, interactive information terminals;
- smartphones and other consumer devices used for electronic communications or to access audiovisual media;
- e-readers.
Services:
- electronic communications (phone and messaging services);
- services that give access to audiovisual media, such as streaming platforms' websites and apps;
- elements of air, bus, rail and waterborne passenger transport: websites, apps, e-tickets, travel information;
- consumer banking;
- e-books and the software used to read them;
- e-commerce — any website or app that sells products or services to consumers.
The e-commerce line is what brings most websites into scope. A brochure site with no online sales is usually outside the Act, though other laws, such as the Web Accessibility Directive for public bodies, may still apply.
What the Act requires
The requirements are in Annex I of the Directive, which has seven sections. Section I covers all products; Section III covers all services; Section IV adds requirements for specific services; the others cover further product requirements, emergency calls to 112, the built environment and functional performance criteria.
For a website or app, the core is one sentence in Section III: websites, online applications and mobile apps must be made accessible "in a consistent and adequate way by making them perceivable, operable, understandable and robust". The same section asks for information about how the service works and, where support services exist (help desks, call centres), information on accessibility in accessible formats.
Section IV adds detail per sector. For e-commerce: give the accessibility information about the products you sell when the manufacturer provides it, and make identification, security and payment functions accessible. For consumer banking, the information must also be understandable at a level no higher than B2 (upper intermediate) of the Common European Framework of Reference for Languages.
The technical standard
The Act describes outcomes; it does not list technical tests. A product or service that meets a harmonised standard cited in the EU's Official Journal is presumed to conform. For websites and apps the standard is EN 301 549, whose web chapter adopts the Web Content Accessibility Guidelines (WCAG):
- EN 301 549 v3.2.1 adopts WCAG 2.1 Level A and AA. It is the version most authorities and audits use today.
- EN 301 549 v4.1.1, published by ETSI in September 2026, adopts WCAG 2.2 Level A and AA and was prepared for the EAA. Until it is cited in the Official Journal it does not give that presumption of conformity.
In practice: test against WCAG 2.1 AA now, and build new pages to WCAG 2.2 AA so you are ready when the new version is cited. Our guide "EAA vs WCAG" explains the difference in detail.
Publishing how you meet it
Service providers must also publish information on how their service meets the requirements (Article 13 and Annex V). It belongs in the general terms and conditions or an equivalent document, and should include:
- a general description of the service in accessible formats;
- the explanations needed to understand how the service works;
- a description of how the service meets the relevant Annex I requirements.
It must be available in written and oral form, accessible to people with disabilities, and kept for as long as the service operates. Most sites publish it as an accessibility statement page linked from the footer and the terms.
Exceptions and disproportionate burden
Some web content is excluded: pre-recorded audio and video and office files (such as PDFs) published before 28 June 2025, content from third parties that you neither fund, develop nor control, and archived content that has not been updated since that date.
A business may also limit a requirement where meeting it would be a disproportionate burden or would fundamentally change the service (Article 14). That is a documented assessment against the criteria in Annex VI, not a label: it must be kept for five years, a service provider must renew it at least every five years, and it is reported to the competent authority. A microenterprise dealing with products is exempt from documenting it, but must still provide the facts if an authority asks.
Enforcement
Each EU country designates authorities that check services, follow up complaints and verify that a business has fixed what it was told to fix. Penalties are set nationally: the Directive requires them to be "effective, proportionate and dissuasive", to come with corrective action, and to reflect how serious the failure is and how many people it affects. Consumers and organisations can also bring a case before national courts or authorities. Amounts and procedures differ by country, which our guide to EAA penalties and enforcement covers.
How far websites are today
In September 2026 we checked the homepages of popular national websites in all 27 EU countries — up to 200 per country from the Chrome UX Report list for August 2026 — for five common barriers. Of the 3,754 homepages we could measure:
| Barrier | Share of homepages |
|---|---|
| At least one of the five | 81.3% |
| Links with no text a screen reader can announce | 57.1% |
| Form fields without a label | 48.8% |
| Images without alt text | 34.9% |
| Buttons without an accessible name | 33.3% |
| No page language declared | 8.1% |
On average each homepage had 22.7 instances. These five checks read the raw HTML of one page, so passing them is not compliance — but failing them is a clear sign that a site has not been tested. Our study "Website accessibility in the EU" has the figures per country and the method.
Where to start
- Check whether you are in scope. Do you sell to consumers online, or provide one of the listed services? Are you a microenterprise?
- Test your key journeys: home page, product or service pages, sign-up, basket and checkout, contact. Run an automated scan, then try each journey with the keyboard alone and with a screen reader.
- Fix the common barriers first — they are cheap and affect most users: link and button names, form labels, alt text, page language, colour contrast.
- Write your accessibility information (Annex V) and link it from the footer and the terms.
- Make it a routine. Re-test whenever templates, checkout or third-party widgets change.
RankProof's free tools cover the automated part: the accessibility scanner runs WCAG 2.1 A and AA rules on a page in your browser, the colour contrast checker tests text against the AA ratios, the alt text checker lists images without alternative text, and the accessibility statement generator drafts the Annex V information. Automated rules find only part of the problems; keyboard, screen-reader and content checks still need a person.
Free tools on this topic
Guides on this topic
Research data on this topic
Start with a free check
Run the free audit or pick one of the tools — no account, and every result explains what to fix.
Try Free Scan