E-Books & Publishing Hub
E-books and dedicated e-reading software are explicitly listed in Annex I of the EAA. Publishers, distributors, and reading platform providers must ensure digital publications are born accessible — not retrofitted — and that the software used to read them never blocks accessibility features.
- ›European Accessibility Act (Directive 2019/882) — Annex I Section V
- ›EN 301 549 v3.2.1
- ›EPUB Accessibility 1.1 (W3C/IDPF)
- ›EPUB 3.3 (W3C)
- ›EPUB Accessibility 1.1
- ›WCAG 2.2 Level AA (for web-based readers)
- ›DAISY 3 / DAISY 4 (audio and braille formats)
- ›PDF/UA-1 (ISO 14289-1)
Compliance Requirements
EPUB 3.3 Structural Accessibility
All new e-book titles must be produced to EPUB 3.3 standard. This requires: a logical reading order defined in the spine, semantic HTML5 markup for chapters and sections, an accessible table of contents (both NCX and nav element), page list navigation markers, language declarations, and ARIA landmark roles where helpful. Content must reflow at all viewport sizes without loss of content or functionality.
EPUB Accessibility 1.1 Metadata
Every e-book must carry accessibility metadata conforming to the EPUB Accessibility 1.1 specification. This includes: accessMode (textual, visual), accessModeSufficient, accessibilityFeature (e.g., alternativeText, readingOrder, structuralNavigation), accessibilityHazard, and an accessibilitySummary in plain language. This metadata enables discovery platforms to surface accessibility information to readers before purchase.
Images & Non-Text Content
All images, figures, charts, and diagrams must carry alt text or, for complex content, an extended description. Decorative images must be marked as such (empty alt or role=presentation). Complex data visualisations should be supplemented by a structured table or prose description. Mathematical content must use MathML 3 for screen-reader compatibility.
DRM & Accessibility Non-Interference
Digital Rights Management (DRM) systems applied to e-books must not block or degrade accessibility features. Specifically: screen readers must be permitted to read aloud (TTS) regardless of copy protection; font resizing and reflow must not be prevented; high-contrast and colour inversion modes must work; and the DRM must not require inaccessible activation steps.
E-Reading Software Accessibility
Reader applications (iOS, Android, Windows, macOS, dedicated e-ink devices) must comply with EN 301 549 Chapter 11. The reader interface — library, bookmarks, annotations, settings — must be keyboard-accessible and screen-reader-compatible. Text-to-speech playback within the app must be controllable with accessible playback controls.
Navigation & Landmarks
Readers must be able to navigate e-books by: chapter/section headings, page numbers (print page equivalents), footnote references, table of contents, and reading position restore. Navigation menus within the reading interface must be accessible. Search functionality (if provided) must support keyboard-only use and announce result counts.
Accessible Discovery & Purchase
E-book retail platforms and library discovery portals must present accessibility metadata (from EPUB Accessibility 1.1) to users at point of discovery. Product pages must allow users to filter or identify titles that meet accessibility requirements. The checkout and library borrowing flows must themselves meet WCAG 2.2 Level AA.
Practical Steps to Compliance
- 1
Audit your publishing workflow — introduce EPUB 3.3 and EPUB Accessibility 1.1 metadata at source
- 2
Use the Ace by DAISY automated checker on all new EPUB outputs before distribution
- 3
Review your DRM contract to confirm TTS read-aloud and font resizing are explicitly permitted
- 4
Test your reading app with VoiceOver and TalkBack — navigation and TTS controls are common failures
- 5
Add accessibility filtering to your catalogue or library portal search interface
- 6
Create an accessibility metadata policy for your editorial and production teams
- 7
Establish a process for readers to report accessibility issues in specific titles
Exemptions & Proportionate Burden
Microenterprises are exempt. Individual authors self-publishing via platforms (not acting as publishers) may have limited obligations. Back-catalogue titles published before June 2025 have a transitional period but must not be re-published or substantially updated without accessibility remediation.
Recommended Tools for This Sector
These AccessibilityRef tools are specifically relevant to your compliance needs. Use them to test, assess, and document your accessibility posture.
E-Book & Publishing Checklist
EAA Annex I §VIII checklist — EPUB metadata, content structure, MathML, reflowable text, DRM, and reading system compatibility.
Open tool →Document Auditor
Audit EPUB and PDF publications for heading structure, alt text, language declaration, and table accessibility.
Open tool →Readability Checker
Check that publication summaries and marketing copy meet accessible reading levels.
Open tool →Contrast Checker
Verify default text and background colours in publications meet 4.5:1 contrast ratio.
Open tool →Alt Text Checker
Check that all images in web-based publication catalogues have meaningful alt text.
Open tool →Hardware Checklist
E-reader devices must meet physical accessibility requirements — text-to-speech, screen magnification, tactile controls.
Open tool →Accessibility Statement Wizard
Generate the mandatory EAA accessibility statement for your e-book or publishing service.
Open tool →Self-Assessment Pipeline
Run a full WCAG 2.2 / EAA self-assessment of your publishing platform.
Open tool →Important Legal Disclaimer
This tool is a self-assessment aid only and does not constitute legal advice or a formally certified compliance assessment. Outputs — including reports, scores, checklists, and accessibility statements — are for internal use and should be reviewed by a qualified legal representative or independent accessibility auditor before being relied upon for regulatory, procurement, or public-disclosure purposes. All assessment risk lies with the internal assessor. accessibilityref, its developers, and staff accept zero liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority.