Standard

European Accessibility Act: already in force, and it covers documents

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

The Act applies to covered products and services placed on the EU market.

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 is unlimited and its report is JSON, so sampling a few hundred generated documents is a script 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 failure conditions

Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, no account.

Check a PDF free

Primary source: https://eur-lex.europa.eu/eli/dir/2019/882/oj. This page is a working summary, not legal advice.

Last updated .