EU GUIDANCE
EU PDF accessibility, in plain language.
A short overview of the rules that increasingly apply to PDFs shared in the EU — what changed in 2025, which documents are affected, and the standards a review looks at.
AT A GLANCE
Key dates and standards.
- 01European Accessibility Act — in force 28 June 2025In-scope products and services placed on the EU market after that date must meet the accessibility requirements.
- 02Transition period to 28 June 2030Service providers may continue using certain products already in use before 28 June 2025 until then.
- 03EN 301 549 — the technical standardThe harmonised European standard for ICT accessibility; its latest version (v4.1.1) references WCAG 2.2 Level AA.
- 04PDF/UA (ISO 14289)The recognised technical standard for accessible PDF documents, used as the practical conformance target.
General information, current as of 2026 — not legal advice.
THE SHORT VERSION 01
What this means for your PDFs.
The rules are less about the file format and more about whether people using assistive technology can actually read and navigate your document.
Which documents are affected?
Not every PDF falls in scope. The European Accessibility Act focuses on documents that are part of a product or service offered to consumers — think account statements, contracts, booking confirmations, product manuals and similar material. Documents published before 28 June 2025 are generally not caught unless they are updated or republished afterwards. Scope and national implementation vary, so a specific document should be assessed on its own facts.
How the standards fit together
EN 301 549 is the European standard that defines what “accessible” means in technical terms; Section 10 covers non-web documents such as PDFs. For documents it points at the same ideas as the Web Content Accessibility Guidelines (WCAG), while PDF/UA (ISO 14289) describes how those ideas are expressed in the PDF format itself. In practice, a PDF that is properly tagged and meets WCAG Level AA and PDF/UA will address the document requirements of EN 301 549.
What an accessible PDF usually needs
- A tag tree so assistive technology can read the content in a sensible order.
- A logical reading order that matches the visual layout.
- Real headings that convey the document’s structure.
- Text alternatives for images and other non-text content.
- A set document language and correct language changes within the text.
- Tables marked up with header relationships, and accessible interactive form fields.
This overview is general information to help you get oriented. It is not legal advice, and it is not a statement that any particular document does or does not comply. For a binding view, consult a qualified adviser.
Useful references
A REVIEW IN CONTEXT 02
Where a review fits.
A scoped review helps you understand where a document stands against these expectations — it is a starting point, not a certificate.
WHAT A REVIEW COVERS
Focused, documented, honest about its limits.
- Scope
- One agreed document, checked against a confirmed set of criteria drawn from WCAG and PDF/UA.
- Method
- Automated checks combined with manual inspection and sample screen-reader testing.
- Output
- Prioritised findings with locations, likely user impact and practical recommendations.
- Limitations
- A scoped review is not an exhaustive audit, legal opinion, certification or guarantee of conformance.
A review supports your own compliance work; it does not replace legal advice or a formal conformance assessment.
NEXT STEP
Have a specific PDF in mind?
Tell me a little about it — page count, type and who it’s for — and we’ll work out the right next step. No sensitive content needed at this stage.