Has the European Accessibility Act been enforced yet?

Yes. EAA enforcement began on 28 June 2025. EU member states each have designated enforcement bodies that can investigate complaints and issue penalties. Any organisation distributing digital documents — including PDFs — in EU markets without meeting WCAG 2.2 AA is currently non-compliant and at risk of complaint or enforcement action.

Why do PDFs fail the EAA?

PDFs fail multiple WCAG 2.2 AA success criteria by design. They use fixed page dimensions that break reflow at 400% zoom (failing WCAG 1.4.10). Reading order in multi-column PDFs is rarely correct for screen readers (failing WCAG 1.3.2). Most PDFs lack semantic heading tags (WCAG 1.3.1) and language declarations (WCAG 3.1.1). Tagged PDFs improve some of this but are expensive to produce and still fail reflow requirements.

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

Convert them to EPUB3. toolkit.bot converts a PDF to EAA-compliant EPUB3 in 15–60 seconds — EPUB3 satisfies the reflow, reading order, navigation, and language requirements that PDFs cannot. For large collections, the toolkit.bot API supports batch conversion of up to 500 files per month. Validate each output with ACE by DAISY before distribution.

What are the EAA penalties for distributing inaccessible PDFs?

EU member states set their own penalties, which must be effective, proportionate, and dissuasive per the Directive. Germany (BFIT-Bund), France (ARCOM), and the Netherlands (ACM) are active enforcement bodies. Penalties can include fines scaled to organisation size, orders to withdraw non-compliant publications, and public reporting. Affected users can also file complaints directly, creating reputational risk beyond regulatory action.

EAA 2026: One Year of Enforcement — Are Your PDFs Still Non-Compliant?

The European Accessibility Act (EAA) entered enforcement on 28 June 2025. As of this week, that's one year of live legal obligation for any organisation distributing digital documents in EU markets.

Most organisations still distribute PDFs. Most of those PDFs fail the EAA's accessibility requirements. If yours is among them, here's what to do — and how quickly you can fix it.

What the EAA requires (and why PDFs almost always fail)

The EAA requires digital products and services sold in the EU to meet WCAG 2.2 AA. For digital documents, this means:

Reflow at 400% zoom (WCAG 1.4.10) — PDFs use fixed page dimensions and break under zoom. Screen reader users, low-vision users, and anyone on a mobile device are affected.
Correct reading order (WCAG 1.3.2) — PDF reading order depends on content object sequence in the file, which rarely matches visual order in multi-column or complex layouts. Screen readers frequently read columns out of sequence.
Programmatic heading structure (WCAG 1.3.1) — Most PDFs lack tagged heading elements. Navigation is impossible for assistive technology users.
Language declaration (WCAG 3.1.1) — PDF language metadata is absent or incorrect in the majority of office-generated documents.

A tagged PDF improves some of these, but tagged PDFs are expensive to produce, fragile to maintain, and still fail reflow on mobile viewports. The EAA does not accept "less bad" — it requires WCAG 2.2 AA conformance.

Who is in scope

The EAA applies to private-sector companies with 10 or more employees, or €2 million or more in annual turnover, that sell digital products or services in the EU — regardless of where the company is based. Covered document types include:

E-books and digital publications
Digital documents distributed as part of a service (reports, white papers, compliance documents, course materials)
Self-service portals that provide PDFs as deliverables

Public sector organisations in EU member states were already covered by the Web Accessibility Directive (WAD). The EAA extends equivalent obligations to the private sector.

What enforcement looks like one year in

EU member states have each established enforcement bodies responsible for investigating complaints and issuing penalties. Complaints can be filed by affected users — people with disabilities who cannot access a document — as well as by advocacy organisations.

Germany's enforcement body is the Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT-Bund). France has designated the ARCOM. The Netherlands has the Autoriteit Consument & Markt (ACM). All have published guidance indicating that enforcement actions are active, not theoretical.

For organisations distributing PDFs in volume — publishers, insurers, public-facing enterprises, academic presses — the risk is not just regulatory. Accessibility litigation is increasing across Europe, modelled in part on the US ADA Title III case law that produced thousands of demand letters per year.

EPUB3: the compliant alternative

EPUB3 is built on HTML5, CSS, and XML — the same technologies that underpin accessible web content. It satisfies WCAG 2.2 AA requirements that PDFs cannot:

Reflow is native: EPUB3 text wraps at any viewport size or zoom level. WCAG 1.4.10 passes by default.
Reading order is explicit: HTML source order defines reading order. Screen readers always present content in the correct sequence.
Navigation is mandatory: EPUB3 requires a nav.xhtml document providing a table of contents. Heading tags in HTML map directly to ARIA landmark navigation.
Language is required metadata: Every EPUB3 package must declare a language. WCAG 3.1.1 passes by spec requirement.

The EPUB Accessibility 1.1 specification formalises how to produce conformant EPUB3 files, including metadata claims that procurement tools and national accessibility bodies can verify.

How to convert PDFs to EAA-compliant EPUB3 in 30 seconds

Go to toolkit.bot/pdf2epub
Upload your PDF — max 50 MB, no account required
Wait ~30 seconds while the converter extracts text, detects heading structure, maps tables, and builds EPUB3 with semantic HTML5
Download the EPUB3. Open in Apple Books, Kobo, or Adobe Digital Editions, or validate with ACE by DAISY

For bulk back-catalogue conversion, the toolkit.bot API accepts up to 500 files per month on the API tier, with shell and Python examples in the API quickstart guide.

After conversion: three steps to verify compliance

ACE by DAISY: Run each EPUB through ACE by DAISY to generate a WCAG 2.2 AA report. ACE identifies specific failure points and verifies what metadata claims are substantiated.
Screen reader spot-check: For high-priority documents, test with NVDA + Firefox or VoiceOver + Safari. Navigate by heading, read a table, confirm reading order in a multi-column section.
EPUB Accessibility 1.1 metadata: Verify the output includes schema:accessibilityFeature, schema:accessMode, and schema:accessibilitySummary metadata using EPUBCheck.

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

Convert a PDF →