The European Accessibility Act, explained for documents
The European Accessibility Act — Directive (EU) 2019/882 — has applied across the EU since June 28, 2025. It sets accessibility requirements for a defined list of products and services sold to consumers, including e-commerce, consumer banking, e-books and transport information, and it reaches the digital documents those services deliver.
Written in English to compare the EAA with US and Canadian regimes; member-state requirements such as France's RGAA or Spain's UNE-EN 301549 are not covered.
DocoMatic does not currently accept personal information that is subject to the EU or UK GDPR; this guide is informational.
The law
What is the European Accessibility Act?
The EAA is an EU directive, adopted in 2019, that harmonizes accessibility requirements for key products and services across all member states. The national laws transposing it apply to products placed on the market and services provided to consumers from June 28, 2025. It is the first EU-wide accessibility law aimed squarely at the private sector.
Each member state enforces the directive through its own transposing law and market surveillance authorities, so the obligations arrive as national law — but the requirements and the covered list are harmonized, which is the point: one accessibility bar across the single market.
Coverage
Who is covered by the EAA?
Manufacturers, importers and providers of the listed products and services sold to EU consumers. Microenterprises providing services — fewer than 10 staff and no more than €2 million turnover or balance sheet — are exempt.
| Covered products and services | Documents it reaches |
|---|---|
| E-commerce — any business selling to EU consumers online | Product information, support content, order documents |
| Consumer banking and financial services | Statements, contracts, notices |
| E-books and dedicated reading software and devices | The publications themselves |
| Passenger transport — air, bus, rail, waterborne | Information and ticketing documents |
| Self-service terminals — ATMs, payment, ticketing, check-in | On-screen and issued documents |
| Consumer computing — hardware, operating systems, smartphones, e-readers | Product and support documentation |
| Microenterprises providing servicesFewer than 10 staff and no more than €2 million turnover or balance sheet | Exempt. Art. 4(5). |
| EU public sector bodies | Not the EAA — the Web Accessibility Directive |
The directive applies to companies established outside the EU when they sell covered products or services to consumers in the EU — market access, not company registration, is what triggers it.
The EAA states functional accessibility requirements rather than naming a technical standard, and conformity is presumed for products and services that meet harmonized European standards. EN 301 549(opens in new tab) — Europe's ICT accessibility standard — plays that role in practice; for web content and documents it incorporates WCAG 2.1 Level AA.
EN 301 549 is maintained by the European standards organizations and contains a dedicated clause for non-web documents — clause 10(opens in new tab) — applying the WCAG criteria to files like PDFs directly. For document work, EAA readiness and WCAG 2.1 AA conformance are effectively the same engineering.
Which edition: V3.2.1 (2021)(opens in new tab) cites WCAG 2.1 and is the edition in the Official Journal; V4.1.1 (September 2026)(opens in new tab), written for the EAA, moves to WCAG 2.2, which keeps the 2.1 AA criteria and adds interactive-control ones — work done to 2.1 AA is not wasted.
Documents
What does the EAA mean for PDFs and customer documents?
Documents delivered as part of a covered service must be accessible: e-books, bank statements and contract documents, invoices, product information and support content in e-commerce, tickets and travel documents. For a PDF that means the same work WCAG 2.1 AA demands — tagged structure, correct reading order, alternative text, a set title and language, labeled forms.
The volume problem looks like the US public-sector one: banks and retailers generate customer documents continuously, so a one-off cleanup is not enough. Covered providers need accessible templates upstream and automated remediation plus verification for the long tail of existing files.
Comparison
EAA or the Web Accessibility Directive?
Two EU regimes, constantly confused. They share a technical foundation and cover different organizations.
| Aspect | European Accessibility Act | Web Accessibility Directive |
|---|---|---|
| Instrument | European Accessibility ActDirective (EU) 2019/882(opens in new tab) | Web Accessibility DirectiveDirective (EU) 2016/2102(opens in new tab) |
| Covers | European Accessibility ActA defined list of private-sector products and services sold to consumers | Web Accessibility DirectivePublic sector bodies’ websites and mobile apps |
| Applies since | European Accessibility ActJune 28, 2025 — products placed on the market and services provided after that date | Web Accessibility DirectiveWebsites from September 2019 or 2020; mobile apps from June 2021 |
| Technical basis | European Accessibility ActEN 301 549 — presumption of conformity once cited under the directive (Art. 15) | Web Accessibility DirectiveEN 301 549 V3.2.1, cited in the Official Journal |
| Extra obligations | European Accessibility ActConformity assessment; CE marking for products; accessibility information | Web Accessibility DirectiveAccessibility statement, feedback mechanism, member-state monitoring |
| Documents | European Accessibility ActThose delivered as part of covered products and services | Web Accessibility DirectiveDocuments on public-sector sites; office files from before September 23, 2018 only if still in active use |
A document can fall under neither. The EAA reaches documents delivered as part of covered products and services; the WAD reaches public-sector sites. Documents outside both may still be covered by national law.
DocoMatic does not publish a Web Accessibility Directive guide. If you are an EU public sector body, that directive is your regime, not this one.
The plan
What should a covered company do now?
The EAA already applies, so start with exposure: identify which of your products and services fall on the covered list and which member states you sell into. Then inventory the customer-facing documents those services generate, remediate the active set to WCAG 2.1 AA, and make templates produce accessible output going forward.
Scope: map your products and services against the EAA's covered list and your EU markets.
Inventory: enumerate customer-facing documents — statements, contracts, e-books, product information.
A public-site scan finds what you publish; per-customer statements and contracts must be sampled from your own systems.
Remediate and verify: bring active documents to WCAG 2.1 AA with a verification report per file.
Fix templates: statements and invoices are generated documents — accessible templates fix thousands of files at once.
FAQ
European Accessibility Act questions, answered
Buying for a larger organization?
Book a 20-minute demo(opens in new tab)Does the EAA apply to companies outside the EU?
Yes, when they sell covered products or services to consumers in the EU. A US or Canadian company running an e-commerce site that serves EU customers, or distributing e-books into EU markets, falls under the member-state laws implementing the directive — establishment outside the EU is not an exemption.
Is the EAA the same as the EU Web Accessibility Directive?
No. The Web Accessibility Directive (2016/2102) covers the websites and apps of public sector bodies, while the EAA covers a defined list of private-sector products and services. They share the technical foundation — EN 301 549 and WCAG — but the audiences and obligations are different.
Does the EAA make every PDF published in Europe accessible?
No. The EAA reaches documents delivered as part of the covered products and services — banking documents, e-books, e-commerce content, transport information. Public sector documents fall under the Web Accessibility Directive instead, and documents outside both regimes may still be covered by national law.
Is there a transition period after June 28, 2025?
A limited one. Service contracts concluded before that date may run unchanged until they expire, no later than June 28, 2030, and self-service terminals lawfully in use may serve out their economic life for up to 20 years. New offerings and renewed contracts must comply now.
| Situation | What applies | Basis |
|---|---|---|
| Service contracts agreed before June 28, 2025 | May run unchanged until they expire, but no later than June 28, 2030. | Art. 32(1) |
| Self-service terminals in use before June 28, 2025 | Member states may let them serve out their economic life, at most 20 years from entry into use. | Art. 32(2) |
How is the EAA enforced?
By each member state: market surveillance authorities check products, designated authorities check services, and consumers and their organizations can complain or take action under national law. Penalties are set nationally and must be effective and dissuasive — and non-conforming products can be kept off the market.
Sources
Every regulatory claim on this page is cited to one of these primary sources.
- EUR-Lex — Directive (EU) 2019/882, the European Accessibility Act
- ETSI, CEN and CENELEC — EN 301 549 V4.1.1 (2026-09), clause 10: non-web documents
- ETSI, CEN and CENELEC — EN 301 549 V3.2.1 (2021-03), the Official Journal edition
- EUR-Lex — Directive (EU) 2016/2102, the Web Accessibility Directive
- European Commission — European Accessibility Act page
- W3C — Web Content Accessibility Guidelines (WCAG) 2.1
Changelog
- Removed the section that described DocoMatic's own publishing plans for other markets and languages (not about the law); a scope note in the introduction replaces it. Cited EN 301 549 clause 10, added three tables, two figures, and hub, site-scan and product links.
- Initial publication.
Reviewed quarterly, and whenever a cited source or a transposing law changes. Next review: December 18, 2026.