Standard
European Accessibility Act: in force, and it covers PDFs
The EAA applied from 28 June 2025. Unlike the ADA Title II deadlines it is not approaching — it has arrived, and it reaches the private sector.
European Union — Directive (EU) 2019/882 · technical standard: EN 301 549, in practice
Dates that matter
Already live
The ADA Title II dates get the attention because they are approaching. The European Accessibility Act is not approaching — it applied from 28 June 2025, and it reaches further than most of the instruments people are preparing for, because it covers the private sector.
If your organisation provides e-commerce, banking, e-books, transport ticketing or electronic communications into the EU market, the documents that service produces are in scope.
What that means for documents
The Act sets functional requirements — perceivable, operable, understandable, robust — rather than a checklist. Conformance is demonstrated through EN 301 549, whose clause 10 applies WCAG 2.1 Level AA to non-web documents.
So the practical target is the same as everywhere else, and the work is the same work:
- a tagged document with structure that reflects meaning;
- a reading order that matches the author’s intent (why this is the hard one →);
- a determinable language, per passage where the language changes (how →);
- text alternatives on meaningful images (how →);
- accessible names on form fields (how →).
The documents that get missed
Public-sector accessibility programmes tend to focus on the website. The EAA’s scope is the service, and services generate documents nobody thinks of as web content:
- account statements and transaction confirmations
- terms and conditions attached to a purchase
- tickets and booking confirmations
- product manuals and safety information
- invoices
These are usually generated by a template, which is good news: fix the template and every future document is fixed. Running a validator over a sample of generated output will tell you quickly whether the template is the problem, and it usually is.
Taggart’s free validator checks a batch of files into one table, so a sample of a few hundred generated documents is a few batches rather than a project.
Frequently asked questions
Does the EAA cover PDFs?
Where a document is part of a covered service, yes. E-commerce, banking, e-books, transport ticketing and electronic communications are all in scope, and the documents those services provide — terms, statements, tickets, manuals — come with them.
Does it apply to private companies?
That is the significant change. Earlier EU accessibility law focused on the public sector; the EAA extends duties to private-sector products and services placed on the EU market. Microenterprises providing services have an exemption, defined by headcount and turnover.
What technical standard does it name?
The Act sets functional requirements rather than naming a technical standard directly. In practice conformance is demonstrated through EN 301 549, which is the harmonised standard for ICT accessibility in the EU.
Does it apply to us if we are not in the EU?
If you place products or services on the EU market, generally yes. It follows the market rather than the establishment, in the same way as other EU product legislation.
Related guides
- How to handle PDFs on a website you are making accessibleA site audit that ignores its documents has audited the wrapper. Which PDFs are in scope, how to find them all, and the order to work through them.
- PDF/UA vs WCAG: which one applies to your documentsOne is a format standard a validator can test. The other is what your legal obligation cites. They overlap heavily and neither one contains the other.
- How to triage a PDF backlogYou have thousands of documents and a deadline. How to find out what you are actually dealing with before committing to a plan, at no cost.
Related failure conditions
- 09-001 Tags are not in logical reading orderThe order of elements in the structure tree does not match the order a human would read the page. This is the single most common substantive defect in tagged PDFs and the one Acrobat's own tooling handles worst.
- 11-001 Natural language for text in page content cannot be determinedNo /Lang is in effect for some text: neither on the catalog, nor on an enclosing structure element, nor on a marked-content sequence.
- 13-004 Figure tag alternative or replacement text missingA Figure element has neither /Alt nor /ActualText. Every Figure must have one or the other; if the image is decorative it should be an artifact instead of a Figure.
- 28-005 A form field has neither a TU entry nor an alternative descriptionThe /TU tooltip is the accessible name of a PDF form field. Without it the field has no name at all — the visible label printed next to it is not connected to the control.
Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, and no account at all up to 60 pages.
Primary source: https://eur-lex.europa.eu/eli/dir/2019/882/oj. This page is a working summary, not legal advice.
Last updated .