The State of PDF Accessibility Under EAA 2026

Published June 30, 2026. Updated as enforcement landscape develops.

Executive Summary: The European Accessibility Act (EAA, Directive 2019/882) entered enforcement on June 28, 2026. For organisations distributing digital documents to EU consumers, this creates immediate compliance obligations under WCAG 2.1 Level AA. The critical finding: WCAG 1.4.10 Reflow — the requirement that content be presentable in a single column at 320px without horizontal scrolling — cannot be satisfied by PDF format regardless of tagging or remediation. Organisations relying solely on PDF accessibility tools will have unmeasured WCAG non-conformances on every multi-column document they distribute.

1. EAA Scope and Document Obligations

Who Must Comply

EAA (Article 2) covers products and services offered to EU consumers. The sectors with direct document exposure:

Sector	Document types in scope
Banking and financial services	Terms and conditions, statements, product guides, prospectuses
E-commerce	Product manuals, return policies, transaction documents
Transport	Booking documents, passenger rights, timetables
Telecommunications	Contracts, bills, service documents
Publishers	Digital publications distributed to EU consumers
Healthcare (digital services)	Patient information, clinical guidance distributed digitally
Public sector bodies	Already subject to Web Accessibility Directive; EAA extends to commercial-adjacent services

The microenterprise exemption (fewer than 10 employees, turnover below €2M) excludes the smallest organisations. The vast majority of organisations publishing documents digitally to EU audiences do not qualify.

What WCAG 2.1 AA Requires for Documents

EAA mandates compliance with EN 301 549, which references WCAG 2.1 Level AA. The most commonly missed requirements for document publishers:

1.1.1 Non-text Content: Alt text on all meaningful images
1.3.1 Info and Relationships: Document structure programmatically determinable
1.3.2 Meaningful Sequence: Reading order correct and determinable
1.4.3 Contrast: Text meets minimum contrast ratios (4.5:1 normal, 3:1 large)
1.4.4 Resize Text: Text can be resized to 200% without loss of content
3.1.1 Language of Page: Document language declared
1.4.10 Reflow: Content presentable in single column at 320px, no horizontal scrolling, no loss of information

WCAG 1.4.10 was added in WCAG 2.1 (2018) specifically to address the mobile and high-magnification use case. Users with low vision who magnify their screen to 400% effectively have a 320px viewport. At that magnification, fixed-layout content requires horizontal scrolling — a severe barrier. This is the criterion that PDF accessibility tools cannot satisfy.

2. The PDF Accessibility Gap

What PDF/UA Delivers

PDF/UA (ISO 14289) is the established PDF accessibility standard. A PDF/UA-compliant document has tagged document structure, correct reading order, alt text on images, language declaration, and a document title. PDF/UA compliance supports screen reader access. Tools like Adobe Acrobat Pro, CommonLook, axesPDF, and PDFix can produce PDF/UA-compliant output. PAC 2024 validates conformance.

What PDF/UA Does Not Deliver

PDF/UA does not satisfy WCAG 1.4.10 Reflow. This is structural. PDF stores content as positioned graphic objects at absolute page coordinates:

BT
/F1 10 Tf
72 720 Td           % Column 1 text starts at x=72
(Clinical guidance text) Tj
300 720 Td          % Column 2 text starts at x=300
(Drug interaction data) Tj
ET

These coordinates are fixed. The page has fixed dimensions (595pt × 842pt for A4). When the viewport narrows — whether due to mobile screen size or 400% magnification — the PDF viewer scales down but cannot reflow. Horizontal scrolling results.

Adobe Acrobat’s built-in Reflow view applies heuristics to approximate reflow. It fails for most multi-column layouts, tables crossing column boundaries, and design-heavy pages. It does not satisfy WCAG 1.4.10 in WCAG conformance audits.

The Scale of the Gap

Virtually every multi-column document distributed as PDF has a WCAG 1.4.10 non-conformance. This includes:

Academic journal articles (nearly all two-column)
Patient information leaflets (typically two-column by EMA design guidance)
Legal judgments and court documents
Annual reports (design-heavy with pull quotes, sidebars, infographics)
Technical standards and specifications
Government consultation documents

3. Sector-by-Sector EAA Exposure

Academic and STM Publishing

Exposure: Critical. Academic publishers distribute millions of journal articles as PDFs to EU institutions. Two-column layout is standard. Most publishers have invested in PDF/UA workflows but have not addressed WCAG 1.4.10. Compliance path: EPUB3 conversion of backlist via API; JATS XML → EPUB3 for new publications.

Legal Publishing

Exposure: High. Legal publishers distribute reference PDFs to EU law firms, courts, and institutions. Legal documents combine multi-column layouts with dense footnotes and complex table structures — the hardest PDF accessibility category. Compliance path: PDF → EPUB3 conversion with specialised handling for footnotes and legal section hierarchy.

Healthcare and Pharmaceutical

Exposure: Critical. Patient Information Leaflets (PILs) and Summaries of Product Characteristics (SmPCs) are legally required for every approved drug in the EU and subject to EAA. EMA’s standard PIL format — typically two columns — fails WCAG 1.4.10 as a fixed-layout PDF. PIL conversion to EPUB3 via API costs approximately $0.01/document at API rates.

Financial Services and Banking

Exposure: High. Banks and financial services firms distribute contractual documents, terms and conditions, prospectuses, and statements clearly in EAA scope. Complex formatting (regulatory disclosure tables, risk ratings, fund performance charts) is difficult to convert without manual alt-text review for financial charts.

Nonprofit and Civil Society

Exposure: Moderate. EU-operating nonprofits distributing annual reports, policy papers, and grant documents are in scope unless they qualify for the microenterprise exemption. Free-tier conversion covers most organisations at typical document volumes (5–20 documents/year).

4. The EPUB3 Solution

Why EPUB3 Satisfies WCAG 1.4.10

EPUB3 is built on HTML5 and CSS. Document content is XHTML:

<html xmlns="http://www.w3.org/1999/xhtml">
<body>
  <section epub:type="chapter">
    <h1>Chapter heading</h1>
    <p>Content that reflows at any viewport width.</p>
  </section>
</body>
</html>

EPUB3 reading systems render at device viewport width. Content reflows by design. WCAG 1.4.10 conformance is structural — no additional work required for the reflow criterion.

EPUB Accessibility 1.1

EPUB Accessibility 1.1 (W3C, 2023) maps WCAG 2.1 requirements to EPUB3 documents. An EPUB3 document with EPUB Accessibility 1.1 conformance metadata satisfies the document accessibility requirements that EAA mandates. Validation is free via ACE by DAISY — the reference checker published by the DAISY Consortium. ACE produces a WCAG 2.1 conformance report suitable for internal documentation and regulatory response.

The Conversion Challenge

PDF → EPUB3 conversion is technically harder than it appears. Key challenges:

Reading order reconstruction: PDF text is stored in paint order, not logical reading order. Multi-column layouts interleave text blocks from both columns.
Structure inference: Heading levels, list items, and table cells must be inferred from typographic signals (font size, weight, indentation).
Table detection: Tables in PDF are typically constructed from ruling lines with positioned text cells.
Footnote handling: Footnote text appears at page-bottom in PDFs and must be relocated as EPUB3 notes.

toolkit.bot addresses these challenges in its conversion pipeline. ACE by DAISY validation confirms output quality per document.

5. Compliance Recommendations by Readiness Stage

Stage 1: Immediate (0–30 days)

For organisations with no current accessibility programme:

Identify documents in active use that EU consumers access
Convert those documents to EPUB3 using toolkit.bot free tier (5/month)
Run ACE by DAISY on each output to identify remaining issues
Publish EPUB3 alongside PDF with an accessibility statement

For organisations with existing PDF/UA workflows:

Continue PDF/UA remediation for screen reader compatibility
Add EPUB3 as the supplemental format for digital distribution
Update accessibility statement to reflect format options

Stage 2: Systematic (30–90 days)

Audit document inventory: classify by traffic, audience, format
Prioritise conversion backlog by EAA exposure (consumer-facing, high traffic, recent)
Implement API-based conversion workflow for new document publications
Establish ACE by DAISY validation as part of document publication checklist

Stage 3: Ongoing

Automate conversion at document creation: integrate API into document management system
Monitor ACE reports for quality trends
Address image alt-text backlog (not automatable — requires human review of figures)
Document conformance status for regulatory response readiness

6. Practical Resources

Conversion: toolkit.bot/pdf2epub — free tier (5/month, no account), Pro ($9/month unlimited), API ($29/month bulk)
EPUB validation: ACE by DAISY — free, open-source
PDF accessibility checking: PAC 2024 — checks PDF/UA conformance (note: does not check WCAG 1.4.10)
EPUB standard: EPUB Accessibility 1.1 (W3C)
WCAG 2.1: Success Criterion 1.4.10 Reflow (W3C)
EAA text: Directive 2019/882 (EUR-Lex)

Convert PDFs to WCAG 2.1 AA EPUB3. Free tier available, no account needed.

Convert PDF to EPUB3 → API plan: EUR 29/month

Frequently Asked Questions

Can PDF/UA satisfy EAA requirements?

PDF/UA satisfies most WCAG criteria but cannot satisfy WCAG 1.4.10 Reflow — a format limitation that tagging cannot fix. The EAA requires WCAG 2.1 Level AA including 1.4.10. PDF/UA alone is therefore not sufficient for EAA compliance. EPUB3, built on HTML5, satisfies WCAG 1.4.10 structurally.

Who must comply with the EAA for documents?

Organisations distributing digital documents to EU consumers in banking and financial services, e-commerce, transport, telecommunications, media, publishing, healthcare digital services, and public sector bodies. The microenterprise exemption (fewer than 10 employees, turnover below €2M) excludes the smallest organisations. Most organisations publishing documents digitally to EU audiences do not qualify for the exemption.

Why can't PDF satisfy WCAG 1.4.10 Reflow?

PDF stores content at absolute page coordinates with fixed page dimensions. At 400% zoom or on a narrow viewport, the page scales but content does not reflow — horizontal scrolling results. This is a structural property of the format, not a tagging deficiency. No remediation tool can fix this because it would require rebuilding the document in a reflowable format. EPUB3 satisfies 1.4.10 because it is built on HTML5, which reflows at any viewport width.

How does EPUB3 satisfy WCAG 1.4.10?

EPUB3 content is XHTML5. Reading systems render EPUB3 content at the device viewport width, with text wrapping and CSS responsive layout. At 400% zoom the text reflows to a single column — no horizontal scrolling. This is a structural property of the format, not something that requires per-document accessibility work for the Reflow criterion.

What is ACE by DAISY and how do I use it?

ACE by DAISY is the reference EPUB3 accessibility checker published by the DAISY Consortium. It tests EPUB3 files against EPUB Accessibility 1.1 and WCAG 2.1, including WCAG 1.4.10 Reflow. Install with: npm install -g @daisy/ace. Run with: ace --outdir ./report ./document.epub. The report is suitable for regulatory audit documentation.

Related Guides

This report is published for informational purposes. It does not constitute legal advice. Organisations should consult qualified legal counsel regarding their specific EAA compliance obligations.