Legal Document Accessibility Under EAA: What Law Firms, Courts, and Publishers Must Do Now
EAA enforcement started June 28, 2026. The legal sector produces some of the densest, most complex PDF documents of any industry — and almost none of them are fully accessible under the new requirements.
Who in the legal sector is affected
The European Accessibility Act covers digital products and services offered to consumers in the EU. For the legal industry, this includes:
Legal publishers (LexisNexis, Thomson Reuters, Wolters Kluwer, IOS Press)
Publishing legal databases, journals, textbooks, and case reporters distributed to EU subscribers.
Law firms with EU clients or offices
Client-facing documents — engagement letters, reports, legal opinions, court submissions distributed digitally — fall within scope when served to EU consumers.
Courts and tribunals publishing judgments
Courts publishing decisions, practice directions, and procedural guides as PDFs on public websites.
Legal technology platforms
Document management, e-discovery, and contract platforms that deliver documents to EU end-users.
The key threshold: if a legal entity offers digital services (including document access) to EU consumers, EAA requirements apply regardless of where the organisation is headquartered.
The specific problem with legal PDFs
Legal documents are formatted for print. Judgments, contracts, briefs, and textbooks are typically two-column, densely footnoted, and laid out for A4 or letter-size pages. This formatting is encoded into the PDF at render time.
This is directly relevant to WCAG 1.4.10 Reflow — the accessibility requirement that causes the most problems for legal document publishers.
What WCAG 1.4.10 requires: Content must be presentable in a single column at 320px CSS width without loss of information or horizontal scrolling. This is the standard for users with low vision who increase text size to 400%.
Why legal PDFs fail: A fixed-layout PDF rendered at 320px width in a PDF viewer does not reflow. The two-column layout causes horizontal scrolling. Section numbers and footnotes that span columns produce reading order errors. This is not a tagging problem — it is a format problem.
Professional PDF accessibility tools (Adobe Acrobat Pro, CommonLook, axesPDF) remediate reading order, tags, and alt text. They cannot change the fact that the PDF format is fixed-layout. A fully remediated, PDF/UA-compliant legal document still fails WCAG 1.4.10 Reflow for multi-column content.
What PDF/UA certification does and doesn't cover
Many legal publishers have invested in PDF/UA compliance as their accessibility baseline. PDF/UA (ISO 14289) ensures:
- Tagged document structure with correct reading order
- Language declarations
- Alt text on images
- Correct heading hierarchy
PDF/UA does not ensure WCAG 1.4.10 Reflow compliance. The PDF/UA standard predates the widespread adoption of WCAG 2.1 and does not address the reflow requirement. A PDF/UA-certified legal document can fail an EAA audit.
This is not a hypothetical risk. Accessibility auditors using WCAG 2.1 AA as their checklist will flag Reflow failures as non-conformances regardless of PDF/UA status.
The solution: EPUB3 as the accessible format for legal content
EPUB3 is built on HTML5 and CSS. It reflows by design. A legal text converted to EPUB3:
- Renders in a single column at any viewport width
- Works with screen readers (NVDA, JAWS, VoiceOver) natively via the EPUB reading system
- Can be validated with ACE by DAISY for EPUB Accessibility 1.1 conformance
- Provides defensible WCAG 2.1 AA compliance documentation via the ACE report
For legal publishers already producing EPUB3 for their consumer ebook division, extending this to legal reference PDFs via conversion is straightforward. For organisations without EPUB3 infrastructure, toolkit.bot provides conversion as a service.
Converting legal PDFs with toolkit.bot
toolkit.bot handles the specific challenges of legal document conversion:
Multi-column layouts
Footnote-heavy legal texts with two-column layouts are the hardest conversion case for most tools. We use spatial clustering to reconstruct reading order across columns before generating the EPUB structure.
Footnotes and endnotes
Footnote references are detected and linked as EPUB notes. Footnote text is relocated to the end of the section rather than rendered mid-paragraph.
Heading hierarchy
Legal document headings (Parts, Chapters, Sections, Articles, Clauses) are detected from typographic signals and mapped to EPUB semantic heading structure (H1–H4).
How to convert:
- Upload a legal PDF at toolkit.bot/pdf2epub
- Download EPUB3 (typically under 30 seconds)
- Validate with ACE by DAISY for compliance documentation
- Serve EPUB3 alongside or instead of PDF for EU-accessible distribution
For bulk backlist conversion:
The toolkit.bot REST API handles batches of legal documents. See pricing for API plans and enterprise volume pricing.
Practical priority guidance for legal organisations
Immediate priority (within 30 days):
- Client-facing documents served via web portals or email to EU clients
- Public court judgments and procedural guides
- Newly published legal content (post June 28, 2026)
Medium priority (within 90 days):
- Recent backlist (last 3 years) available on digital platforms
- High-traffic reference materials (frequently downloaded documents)
Longer-term:
- Full backlist conversion via API
- Integration with document management system for automated EPUB3 generation at publication
Getting started
Free evaluation: toolkit.bot/pdf2epub — upload a legal PDF, get EPUB3 in 30 seconds. No account, no credit card.
API for bulk workflows: toolkit.bot/pricing — API plan includes bulk conversion.
Enterprise / volume pricing: toolkit.bot/premium — custom SLAs for large backlist projects.
EAA enforcement is live. For the legal sector, the combination of complex PDF layouts and high document volume makes format conversion — not remediation — the practical path to WCAG 1.4.10 compliance.