Accessible PDFs: the law in Europe, the UK, and why it matters

For years, "accessible PDF" sat quietly on the wishlist — nice to have, rarely demanded. That's changed. Across Europe it's now law, in the UK it's a strong expectation backed by enforcement, and globally it's becoming a baseline standard for any brand that publishes documents online.

Here's the landscape, written for the people who commission and approve the work — not the people building the tag tree.

Why PDFs are a problem in the first place

A PDF is a visual format. By default it's a picture of a document, not a structured document. Screen readers, braille displays and reading-order tools need underlying structure — headings, reading order, alt text on images, properly tagged tables, language metadata, marked-up forms.

Without that structure, a PDF is effectively invisible to anyone using assistive technology. That's somewhere around 16% of the EU population living with some form of disability, and roughly 1 in 5 adults in the UK.

Europe: the European Accessibility Act (EAA)

The big shift is the European Accessibility Act (Directive (EU) 2019/882), which became enforceable on 28 June 2025.

What it covers, in plain terms:

• Who: Private-sector businesses selling certain products and services into the EU — including e-commerce, banking, e-books, transport ticketing, and consumer-facing digital services.
• What: Digital content provided as part of those services must be accessible. PDFs delivered to consumers — terms, statements, invoices, manuals, product information, contracts — fall squarely inside scope.
• Standard: Compliance is measured against EN 301 549, which in turn references WCAG 2.1 Level AA and PDF/UA-1 (ISO 14289-1) for documents.
• Exemptions: Microenterprises (fewer than 10 staff and under €2m turnover) providing services are largely exempt. Disproportionate-burden arguments exist but are narrow and must be documented.
• Enforcement: Each member state appoints its own market surveillance authority. Penalties vary by country but include fines, removal from market, and reputational consequences.

For the public sector, the older Web Accessibility Directive (EU) 2016/2102 has already required accessible PDFs on public-sector websites and apps since 2018–2020.

United Kingdom

The UK didn't onshore the EAA after Brexit, but the direction of travel is the same.

• Equality Act 2010: Service providers have a duty to make "reasonable adjustments" so disabled people aren't placed at a substantial disadvantage. Inaccessible documents are a textbook example. Enforcement is via individual claims and the Equality and Human Rights Commission.
• Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018: Public-sector PDFs published since September 2018 must meet WCAG 2.1 AA, including documents. The Government Digital Service actively monitors compliance.
• Practical reality for private companies: If you sell into the EU, the EAA applies regardless of where you're based. Most UK brands of any meaningful size are therefore building to EAA standards anyway.

Beyond Europe — the wider picture

• United States: Section 508 (federal) and the ADA (private sector, via case law) both pull in the same direction — WCAG 2.x AA for documents.
• Canada: The Accessible Canada Act applies federally; provincial regimes (notably AODA in Ontario) extend it.
• Australia: Disability Discrimination Act, with WCAG 2.x AA as the de-facto benchmark.

The standards converge. Build a PDF to PDF/UA-1 + WCAG 2.1 AA and you're substantially compliant almost everywhere that matters.

Who's typically on the hook

A surprising number of stakeholders sit inside scope without realising it:

• FMCG and consumer brands publishing product manuals, ingredient sheets and safety information
• Financial services issuing statements, contracts, KIDs and policy documents
• Retailers and e-commerce delivering invoices, returns labels and T&Cs
• Publishers producing reports, white papers and e-books
• Agencies delivering campaign assets, decks and case studies on behalf of clients
• Anyone with a "Download PDF" button on a regulated service

If a customer can receive a PDF from you as part of using your service, the document is part of the service.

What "accessible" actually means at the deliverable level

Without going into the mechanics, an accessible PDF is one that:

• Has a logical reading order independent of visual layout
• Carries proper structure (headings, lists, tables, language)
• Describes its images for people who can't see them
• Works with a keyboard and assistive technology
• Declares itself — title, language, tagging — in its metadata
• Conforms to PDF/UA-1, with WCAG 2.1 AA as the wider benchmark

A document that ticks those boxes is not just legally safer. It also indexes better, converts to other formats more reliably, and ages far better than a flat-export PDF.

Why brands should actually care

Compliance is the floor, not the ceiling. The real arguments are commercial:

1. Risk: Fines, complaints, removal from market, and the PR cost of being publicly called out.
2. Reach: Around 1 in 5 of your audience benefits directly. Many more benefit indirectly — older readers, mobile users in poor conditions, anyone using read-aloud tools.
3. Procurement: Larger clients (especially public sector and regulated industries) increasingly require accessibility conformance statements before signing.
4. Longevity: A properly structured PDF is easier to repurpose, translate, and re-flow into other channels.
5. Brand: Inaccessible documents quietly tell a portion of your audience that they weren't considered.

What good looks like in practice

For brands and agencies commissioning work, the practical checklist is short:

• Decide accessibility scope at brief stage, not at the proofing stage
• Commission artwork from someone who understands PDF/UA-1 as well as print production
• Ask for a conformance statement with delivery
• Treat accessibility amends like any other QA pass — budgeted for, not bolted on

The cost of building accessibly from the start is small. The cost of retrofitting an entire library of legacy PDFs is not.

---

Need accessible artwork delivered to PDF/UA-1 and WCAG 2.1 AA? Get in touch — we handle accessible artworking as standard, not as an extra.