What is the EAA 2026 deadline?

The European Accessibility Act entered full enforcement on 28 June 2025. The June 2026 anniversary marks one full year of active enforcement by national bodies in Germany (BFIT-Bund), France (ARCOM), and the Netherlands (ACM), among others. Any organisation distributing digital documents — including PDFs — to EU customers without meeting WCAG 2.2 AA is currently at risk of complaint and enforcement action.

Do PDFs pass EAA accessibility requirements?

Almost never. PDFs fail WCAG 1.4.10 (reflow at 400% zoom) by design — fixed page dimensions cannot reflow. Multi-column and complex layout PDFs also fail WCAG 1.3.2 (reading order) because PDF content object sequence rarely matches visual reading order. Tagged PDFs improve some issues but cannot fix the reflow failure and require expensive manual tagging to produce correctly.

What is the fastest way to make PDFs EAA-compliant?

Convert them to EPUB3. toolkit.bot converts a PDF to EPUB3 in 15–60 seconds at toolkit.bot/pdf2epub — free, no account required. EPUB3 satisfies WCAG 1.4.10 (reflow), 1.3.2 (reading order), 1.3.1 (heading structure), and 3.1.1 (language) by design. Validate the output with ACE by DAISY before distribution.

Who does the EAA apply to?

Any private-sector organisation with 10 or more employees or €2 million or more in annual revenue that sells digital products or services in the EU — regardless of where the organisation is based. Covered document types include ebooks, digital publications, and PDFs distributed as part of a service (reports, course materials, compliance documents, white papers). Microenterprises (fewer than 10 employees and under €2M revenue) are exempt.

What are the EAA penalties for non-compliant PDFs?

EU member states set their own penalties, which must be effective, proportionate, and dissuasive per the Directive. Enforcement bodies can issue formal warnings, require withdrawal of non-compliant documents, and impose fines scaled to organisation size and turnover. Affected users and advocacy organisations can file complaints directly, creating reputational and legal risk beyond regulatory fines.

EAA 2026 Deadline: Last-Minute PDF Accessibility Compliance Guide

The European Accessibility Act enforcement anniversary falls on June 28, 2026. Regulators across the EU are now a full year into active enforcement — and the most common non-compliance issue is still the same: organisations distributing PDFs that fail basic WCAG 2.2 AA requirements.

If your organisation is still distributing inaccessible PDFs in EU markets, this guide shows you how to get compliant this week using a free, no-install tool.

What the EAA requires — and why PDFs almost always fail

The EAA requires digital documents distributed in EU markets to meet WCAG 2.2 AA. The four failure points that affect virtually every PDF in circulation:

Reflow at 400% zoom (WCAG 1.4.10) — PDFs have fixed page dimensions. At high zoom or on mobile viewports, content overflows horizontally. This failure is structural: you cannot fix it with tagging.
Reading order (WCAG 1.3.2) — In multi-column, footnote-heavy, or complex-layout PDFs, screen readers parse content out of visual sequence. Tagged PDFs improve this only if the tag tree was manually corrected — which almost none are.
Heading structure (WCAG 1.3.1) — Most PDFs produced by standard office tools have no semantic heading tags. Navigation by heading — the primary method for screen reader users — is impossible.
Language declaration (WCAG 3.1.1) — Most PDFs lack correct language metadata. Screen readers cannot switch pronunciation correctly across language boundaries.

A "tagged PDF" satisfies some of these — but tagging is expensive, fragile on export, and still fails reflow. The EAA does not accept partial compliance.

Who is at risk right now

Enforcement bodies in Germany (BFIT-Bund), France (ARCOM), and the Netherlands (ACM) have been active since June 2025. Complaints can be filed by individual users with disabilities or by advocacy organisations. The complaint triggers an investigation; if non-compliance is confirmed, penalties can include fines scaled to turnover and orders to withdraw non-compliant publications.

Organisations at highest risk heading into the enforcement anniversary:

Publishers and academic presses distributing ebooks or journals to EU customers
Insurers, banks, and financial services distributing policy documents, reports, or KIDs
E-learning platforms providing course materials as PDF downloads
SaaS companies whose onboarding, terms, or deliverables include PDF exports

The threshold for EAA scope: 10 or more employees, or €2 million or more in annual revenue, selling any digital product or service in the EU. You do not need to be based in the EU.

The fastest path to EAA-compliant documents: PDF to EPUB3

EPUB3 is built on HTML5 and CSS — the same technologies that power accessible web content. It satisfies every WCAG requirement that PDFs structurally cannot:

Reflow is native: EPUB3 text wraps at any viewport or zoom level. WCAG 1.4.10 passes by design.
Reading order is explicit: HTML source order defines reading order. Screen readers always receive content in the correct sequence.
Navigation is required: Every EPUB3 file must include a navigation document (nav.xhtml) providing a table of contents. Heading tags map to ARIA landmarks.
Language is mandatory metadata: EPUB3 package specification requires a language declaration. WCAG 3.1.1 passes by spec.

The EPUB Accessibility 1.1 specification formalises conformance claims that procurement tools and enforcement bodies can verify independently.

Emergency compliance workflow: convert today

Prioritise your highest-risk PDFs — documents currently distributed to EU customers, public-facing downloads, and anything referenced in service agreements.
Go to toolkit.bot/pdf2epub — no account, no install, no payment required for the first conversion.
Upload your PDF (up to 50 MB). The converter extracts text, detects heading structure, handles tables, and builds EPUB3 with semantic HTML5 in 15–60 seconds.
Download and validate — open the EPUB3 in ACE by DAISY to generate a WCAG 2.2 AA report. ACE is free and runs locally.
Replace the PDF distribution point — update your website, portal, or delivery system to serve the EPUB3 instead of (or alongside) the PDF.

For back-catalogue conversion at scale, the toolkit.bot API supports batch processing of up to 500 files per month. See the Python quickstart for a ready-to-run script.

After conversion: three verification steps

ACE by DAISY — generates a WCAG 2.2 AA compliance report for each EPUB file. Flags specific failure points and verifies accessibility metadata.
EPUBCheck — validates structural conformance to EPUB3 specification. Required before submission to any distribution channel.
Screen reader spot-check — for high-priority documents, navigate by heading in NVDA + Firefox or VoiceOver + Safari. Confirm reading order in any table or multi-column section.

toolkit.bot output includes EPUB3 semantic structure, heading hierarchy, and reading order preservation. After conversion, run ACE by DAISY to verify accessibility metadata and identify any issues before distribution.

Convert your first PDF to accessible EPUB3 — free, no account, no install.

Convert a PDF now →