EN 301 549 is the European harmonized standard that defines what "accessible" means for information and communication technology — including the PDFs and other documents your organization publishes. It is the technical benchmark behind the European Accessibility Act and the EU's Web Accessibility Directive, and it is the reason WCAG 2.1 Level AA shows up in European compliance conversations. This guide explains what the standard is, how it is structured, and how it maps to WCAG.
What EN 301 549 is
EN 301 549 is the European standard for the accessibility of ICT products and services. "ICT" is deliberately broad: it spans websites, software, hardware, electronic documents, and telecommunications equipment. The standard sets out detailed, testable requirements so that procurers, suppliers, and regulators across Europe share one common definition of accessibility instead of inventing their own.
It was developed jointly by the European standards bodies — CEN, CENELEC, and ETSI — at the request of the European Commission. The first version arrived in 2014, originally framed around public procurement, and it has been revised several times since to keep pace with WCAG and to widen its scope. Today it functions as the harmonized standard that underpins EU accessibility law: meeting it gives a presumption of conformity with the legal obligations that reference it.
How the standard is structured
EN 301 549 is organized so that you only apply the parts relevant to the technology you are dealing with. Its building blocks include:
- Functional performance statements — outcome-based requirements describing what a user must be able to do, expressed without assuming a particular disability. For example: usable without vision, without hearing, with limited reach or strength, or without requiring fine motor control. These set the why behind the technical clauses.
- Web content — requirements that map directly to WCAG 2.1 Level AA.
- Non-web documents — the clause most relevant to PDFs (covered below).
- Non-web software — applications, mobile apps, and desktop software.
- Hardware — physical devices such as kiosks, terminals, and phones.
- ICT with two-way voice communication — telephony and real-time text requirements.
- Documentation and support services — the requirement that product documentation and help channels are themselves accessible.
This modular structure is what lets a single standard cover everything from a bank's website to its ATMs to the PDF statement it mails you.
The clause for non-web documents (relevant to PDFs)
For document owners, the key part of EN 301 549 is the clause covering non-web documents. A PDF statement, invoice, contract, or e-book is a non-web document, and the standard requires those documents to satisfy the relevant WCAG 2.1 success criteria at Level A and AA, adapted for a document context rather than a web page.
In practice, that translates to the same fundamentals that define an accessible PDF anywhere:
- A proper tag tree marking headings, paragraphs, lists, and tables
- A logical reading order that matches how a person reads the page
- Meaningful alt text for informative images, with decorative images marked as artifacts
- Sufficient color contrast, and never relying on color alone
- Accessible form fields with labels and a sensible tab order
- Correct document metadata and language
So while the legal hook is European, the technical work to satisfy EN 301 549 for a PDF is identical to the work that satisfies US and Canadian expectations — which is why one well-built document is portable across jurisdictions.
Its relationship to the EAA and the Web Accessibility Directive
EN 301 549 does not have legal force on its own. It becomes binding because EU laws point to it as the way to demonstrate compliance:
- The European Accessibility Act (Directive (EU) 2019/882) — applicable since June 28, 2025 — covers a defined set of consumer products and services and their customer-facing documents. Conforming to EN 301 549 gives a presumption of conformity with the EAA. The operational deadline and document scope are covered in the EAA deadline for customer-facing PDFs.
- The Web Accessibility Directive requires public-sector bodies' websites and apps to be accessible, and it likewise uses EN 301 549 as its technical reference.
In other words, the same standard serves both the private-sector EAA and the public-sector directive. An organization that builds its documents to EN 301 549 satisfies the technical core of both regimes at once.
How EN 301 549 maps to WCAG
The relationship between EN 301 549 and WCAG is the most important thing to understand about the standard:
| Layer | What it is | Role |
|---|---|---|
| EAA / Web Accessibility Directive | EU law | Creates the legal obligation |
| EN 301 549 | Harmonized European standard | Defines technical conformance; grants presumption of conformity |
| WCAG 2.1 AA | W3C accessibility guidelines | Supplies the actual success criteria for web content and documents |
EN 301 549 deliberately incorporates WCAG 2.1 Level AA rather than reinventing it for web content and documents. It then adds the parts WCAG does not address — hardware, two-way voice, documentation, and functional performance — to round out the broader ICT picture. So when European law asks for EN 301 549 conformance on a PDF, it is, at the content level, asking for WCAG 2.1 AA.
This mapping is also why a multinational can standardize on a single bar. WCAG 2.1 AA satisfies EN 301 549 in Europe and serves as the working benchmark in the US, the UK, and Canada. For a full jurisdiction-by-jurisdiction view, see the PDF accessibility law comparison, and for the wider global picture start with the European Accessibility Act and global PDF laws pillar guide.
Key takeaways
- EN 301 549 is the European harmonized standard for ICT accessibility, developed by CEN, CENELEC, and ETSI, and revised over time to track WCAG and broaden its scope.
- It is modular — functional performance statements plus clauses for web content, non-web documents, software, hardware, and two-way voice — so you apply only the parts relevant to your technology.
- For PDFs, the non-web documents clause requires conformance with WCAG 2.1 success criteria at Level A and AA — meaning tags, reading order, alt text, contrast, accessible forms, and correct metadata.
- The standard underpins both the European Accessibility Act and the Web Accessibility Directive, granting a presumption of conformity with each.
- At the content level, EN 301 549 maps directly to WCAG 2.1 AA, so a single, well-built accessible PDF can satisfy European, US, UK, and Canadian expectations alike.
