The European Accessibility Act (EAA) reached its application date on June 28, 2025, and for many businesses the most overlooked obligation is the one hiding in plain sight: the customer-facing PDFs you send every day. Bank statements, invoices, contracts, tickets, and terms are now expected to be accessible if your business is in scope. This guide explains who is covered, which documents are affected, what compliance actually requires, and the practical first steps to take. This is general information, not legal advice.
The June 28, 2025 application date
The EAA — Directive (EU) 2019/882 — was adopted in 2019 with a long runway, and its substantive obligations apply from June 28, 2025. That date has passed. There is no remaining grace period to "prepare for"; covered businesses are expected to be compliant now, and member states have stood up their enforcement regimes.
Because the EAA is a directive, each EU member state transposed it into national law. The accessibility requirements are common across the bloc, but the enforcement details differ by country — a point we return to below and explore further in the European Accessibility Act and global PDF laws pillar guide.
Which businesses are in scope
The EAA targets a defined list of consumer-facing sectors rather than the whole economy. You are likely in scope if you operate in:
- Consumer banking and financial services — retail accounts, payment services
- E-commerce — online sale of goods and services to consumers
- Electronic communications (telecoms) — phone and internet service providers
- Passenger transport — air, bus, rail, and waterborne travel (specified elements)
- E-books and e-readers — publishers and device makers
- Audiovisual media access services and providers of related consumer products such as smartphones, ATMs, payment and ticketing terminals
If your organization sells to consumers in the EU in one of these sectors, the EAA almost certainly reaches some of your documents.
Which PDFs are affected
The EAA is not limited to apps and web pages. It extends to the information and documents a covered service provides to consumers — and those are frequently delivered as PDFs:
| Document type | Typical sector |
|---|---|
| Account & bank statements | Banking, financial services |
| Invoices & billing documents | E-commerce, telecoms, transport |
| Contracts & terms and conditions | All covered services |
| Order confirmations & receipts | E-commerce |
| Tickets & booking confirmations | Passenger transport |
| Product manuals & instructions | Covered products (e-readers, terminals) |
The common thread is volume. These documents are usually generated automatically from templates, which means a single inaccessible template can produce millions of non-compliant files. It also means fixing the template fixes the whole stream.
What compliance requires
The EAA does not list pixel-level rules. It points to the harmonized European standard EN 301 549, and conforming to that standard gives you a presumption of conformity with the directive. EN 301 549, in turn, incorporates WCAG 2.1 Level AA for documents. The full chain looks like this:
EAA (the law) → EN 301 549 (harmonized standard) → WCAG 2.1 AA (technical criteria)
For a PDF, meeting WCAG 2.1 AA means the document must be properly built for assistive technology, not just visually correct. In practice that means:
- Tagged structure — an underlying tag tree marking headings, paragraphs, lists, and tables so a screen reader knows what each element is. An untagged PDF is silent to assistive technology.
- Correct reading order — the tag order must match the logical reading order, not the order objects were drawn (multi-column statements are a frequent failure point).
- Meaningful alt text — every informative image needs a text alternative; decorative images are marked as artifacts.
- Sufficient color contrast and never using color alone to convey meaning.
- Accessible forms — interactive fields with labels, a logical tab order, and clear instructions.
- Correct metadata and language — a document title and a specified language so the file is announced correctly.
The standard itself is broken down in EN 301 549 explained. For sector-specific patterns — statements, disclosures, and high-volume billing — see financial services accessible PDFs.
The microenterprise (services) exemption
The EAA carves out the smallest businesses. Microenterprises that provide services — generally those with fewer than 10 employees and an annual turnover or balance-sheet total not exceeding €2 million — are exempt from the service obligations.
Two things to keep in mind. The exemption is specific to services, so it does not blanket-cover product makers in the same way. And it is a hard threshold: cross 10 employees and the exemption falls away. Realistically, any organization sending statements, invoices, or tickets at scale is well past the microenterprise line.
Enforcement and penalties are set per member state
Here is where a single EU-wide answer breaks down. The EAA requires member states to set penalties that are "effective, proportionate and dissuasive," but it leaves the specifics to national law. That means:
- The standard you must meet is uniform across the EU.
- The consequences of non-compliance — fine levels, corrective orders, who can complain, and which authority enforces — depend on the country where you operate.
A business active in several member states should map its exposure country by country rather than assume one national interpretation applies everywhere.
Practical first steps
If you are in scope and not yet confident in your documents, a focused start beats a sprawling project:
- Inventory by template, not by file. Identify the handful of templates behind your highest-volume PDFs — statements, invoices, contracts, tickets.
- Test the top templates against WCAG 2.1 AA. Automated checks surface mechanical failures (missing tags, no language, low contrast); manual review confirms reading order, meaningful alt text, and form usability.
- Fix at the source. Correct the generation logic or authoring template so files are born accessible, rather than remediating each output after the fact.
- Prioritize what consumers actually receive. A current monthly statement matters more than a years-old archive.
- Document conformance. Keep dated test results against the standard — they support your presumption of conformity and shorten the response to any complaint.
- Map enforcement per country. Note the responsible authority and penalty regime in each member state where you operate.
Key takeaways
- The EAA has applied since June 28, 2025 — there is no remaining preparation window for businesses already in scope.
- In-scope sectors include banking, e-commerce, telecoms, passenger transport, and e-books/e-readers, and affected PDFs include statements, invoices, contracts, terms, tickets, and manuals.
- Compliance means meeting EN 301 549, which incorporates WCAG 2.1 AA — properly tagged documents with correct reading order, alt text, contrast, and accessible forms.
- Microenterprises providing services (fewer than 10 employees) may be exempt, but enforcement and penalties are set by each member state.
- The fastest path is to fix the templates behind high-volume documents and to document conformance against the standard.
Frequently asked questions
Which PDFs does the EAA cover?+
Documents connected to in-scope consumer services — banking statements, e-commerce receipts, contracts, tickets, and similar customer-facing PDFs — must be accessible, though small microenterprises providing services may be partially exempt.



