Ebook accessibility isn't optional. The EU European Accessibility Act became enforceable in June 2025, requiring all ebooks sold in Europe to meet accessibility standards. The US ADA and Section 508 have applied to digital publications in educational and government contexts for years. Canada's Accessible Canada Act covers ebooks. This isn't future planning — it's current legal obligation.
Beyond legal compliance, accessible ebooks reach more readers. 15% of the global population has some form of disability. Screen reader users, people with low vision, dyslexic readers, and those with motor impairments all benefit from accessible ebook design. An accessible EPUB works better for everyone — it has cleaner structure, better navigation, and proper semantic markup that improves rendering across all devices.
The EPUB Accessibility Specification
EPUB Accessibility 1.1 (a W3C specification) defines two conformance levels: EPUB Accessibility (meeting WCAG 2.1 Level AA for content) and EPUB Accessibility + Optimized (additional ebook-specific enhancements). The spec builds on WCAG but adds requirements specific to digital publications.
The core requirements:
- WCAG 2.1 Level AA — All content must meet WCAG success criteria applicable to ebook content (not all WCAG criteria apply — keyboard navigation, for instance, applies differently in reading apps)
- Discoverability — Accessibility metadata must be present so users can determine the book's accessibility features before purchasing
- Content accessibility — Semantic markup, navigation, alternative text, reading order, and logical structure
- Distribution — DRM must not block assistive technology. If DRM prevents screen reader access, the book fails accessibility requirements regardless of content quality
Semantic Markup: The Foundation
Accessible ebooks start with correct HTML semantics. Screen readers interpret content based on HTML elements, not visual appearance. A heading styled with <p class="big-bold"> looks like a heading visually but is invisible to screen readers as a heading.
Heading Hierarchy
Use <h1> through <h6> in proper hierarchical order. Each content document should have one <h1> (the chapter title). Subsections use <h2>, sub-subsections use <h3>, and so on. Never skip heading levels — going from <h1> to <h3> without an <h2> confuses screen reader navigation.
Screen reader users navigate by heading. In a well-structured book, they can jump to any chapter, section, or subsection instantly using the heading list. Without headings, they must listen to the entire book sequentially to find content — the digital equivalent of reading every page to find a chapter.
EPUB Semantic Inflection (epub:type)
EPUB 3 provides the epub:type attribute for marking structural roles beyond HTML semantics:
epub:type="bodymatter"— Main contentepub:type="frontmatter"— Title page, dedication, prefaceepub:type="backmatter"— Appendices, index, bibliographyepub:type="chapter"— Chapter sectionsepub:type="footnote"— Footnotes (screen readers can announce these specially)epub:type="pagebreak"— Print page references (for synchronized page citations)epub:type="noteref"— Footnote reference links
Pair epub:type with ARIA roles for maximum compatibility: <section epub:type="chapter" role="doc-chapter">. The epub:type is processed by EPUB-aware readers; the ARIA role is processed by screen readers. Some reading apps (Apple Books) use epub:type to enhance the reading experience — footnotes marked with epub:type="footnote" appear as popovers instead of inline text.
Navigation for Accessibility
EPUB navigation goes beyond the table of contents. Three navigation structures are important for accessibility:
Table of Contents (Required)
The EPUB 3 nav document must include a <nav epub:type="toc"> element with links to all major content sections. For accessibility, the TOC should be comprehensive — not just chapter titles, but sections and subsections. A user who can't visually scan a page depends on the TOC for finding specific content.
The TOC must be properly nested: chapters containing sections containing subsections, reflected in nested <ol> elements. Flat TOCs (all entries at the same level) lose structural information that screen reader users need.
Page List (Strongly Recommended)
The page list (<nav epub:type="page-list">) maps EPUB positions to print edition page numbers. This enables:
- Synchronized page citations between print and digital editions
- Classroom use where teachers reference page numbers
- Academic citation using page numbers
Each page break is marked in the content with <span epub:type="pagebreak" id="pg42" title="42" role="doc-pagebreak"></span>. The page list nav links to these markers. Without a page list, a student told to "read pages 42-50" cannot navigate a reflowable EPUB. The EPUB Accessibility spec strongly recommends page lists for any book with a print equivalent.
Landmarks (Required for Conformance)
The landmarks nav (<nav epub:type="landmarks">) provides top-level navigation to structural regions of the book:
<nav epub:type="landmarks">
<ol>
<li><a epub:type="toc" href="nav.xhtml">Table of Contents</a></li>
<li><a epub:type="bodymatter" href="chapter01.xhtml">Start of Content</a></li>
<li><a epub:type="backmatter" href="appendix.xhtml">Appendices</a></li>
<li><a epub:type="loi" href="illustrations.xhtml">List of Illustrations</a></li>
</ol>
</nav>Landmarks let users jump directly to the start of content (skipping front matter), the table of contents, the bibliography, or the index. For screen reader users, landmarks are the equivalent of a book's physical structure — the thickness of front matter they can skip, the appendices they can feel at the back.
Image Accessibility: Alt Text and Descriptions
Every image in an accessible EPUB needs alternative text. The level of detail depends on the image's purpose:
- Decorative images (ornamental dividers, background textures):
alt=""(empty alt) to tell screen readers to skip them - Simple informational images (author photo, cover): Brief alt text describing content —
alt="Author portrait: Frank Herbert, 1984" - Complex images (charts, diagrams, maps): Brief alt text PLUS extended description. Use
aria-describedbypointing to a detailed description or<figcaption>with full text equivalent - Text in images (signs, labels, screenshots with text): Full transcription of all text in the alt attribute
For complex images, the extended description should provide the same information the image conveys visually. A chart alt text might be: "Bar chart showing annual revenue" with an extended description listing each bar's value. A map might need textual description of the geographic relationships shown.
EPUB 3 supports the <figure> and <figcaption> elements for structured image + caption associations. Use them:
<figure>
<img src="chart.png" alt="Revenue growth 2020-2025"
aria-describedby="chart-desc"/>
<figcaption id="chart-desc">
Annual revenue grew from $2.1M in 2020 to $8.7M in 2025,
with the steepest growth between 2023 and 2024 (42% increase).
</figcaption>
</figure>Text-to-Speech Compatibility
TTS is the most common assistive technology for ebook readers. Ensuring TTS compatibility means:
- Language declaration: Set
xml:langon the<html>element of every content document, and usexml:langon inline elements when the language switches (e.g., a French phrase in an English book). TTS engines use language tags to select the correct pronunciation model - Abbreviation markup: Use
<abbr title="World Health Organization">WHO</abbr>so TTS can announce the full form. Without this, TTS might say "who" instead of spelling out "W-H-O" - Reading order: Ensure the DOM order matches the intended reading order. Sidebars, pull quotes, and footnotes should appear in the HTML where they logically belong, not where CSS positions them visually. Screen readers follow DOM order, not visual order
- Pronunciation hints: EPUB 3 supports SSML (Speech Synthesis Markup Language) via the
ssml:phattribute for pronunciation guidance on difficult words, proper nouns, or domain-specific terms
Media Overlays for Accessibility
Media overlays (synchronized audio narration with text highlighting) are the gold standard for accessible ebooks. They enable:
- Read-along experience — Text highlights as the corresponding audio plays, supporting users who benefit from simultaneous visual and auditory input
- Dyslexia support — Hearing words while seeing them highlighted helps dyslexic readers track position and decode text
- Language learning — Hearing pronunciation while reading supports language learners
- Low vision support — Large-text display with audio narration provides dual-channel information delivery
Creating media overlays requires: a professional audio narration of the text, time-aligned transcription (mapping audio timestamps to text segments), and SMIL documents linking the two. Tools like Tobi (from the DAISY Consortium) and Readium facilitate media overlay creation. Forced-alignment tools (Aeneas, Gentle) can automate the timestamp alignment from existing audio and text.
Apple Books renders media overlays natively. Kobo supports them on some devices. Most other readers either ignore overlays or provide partial support. Despite limited reader support, media overlays are the most complete accessibility solution for ebooks and are increasingly expected for educational content.
Accessibility Metadata
EPUB accessibility metadata declares the book's accessibility features so users can make informed decisions before purchasing. This metadata is included in the OPF:
<meta property="schema:accessibilityFeature">structuralNavigation</meta>
<meta property="schema:accessibilityFeature">alternativeText</meta>
<meta property="schema:accessibilityFeature">readingOrder</meta>
<meta property="schema:accessibilityFeature">longDescription</meta>
<meta property="schema:accessibilityFeature">pageNavigation</meta>
<meta property="schema:accessibilityHazard">noFlashingHazard</meta>
<meta property="schema:accessibilityHazard">noSoundHazard</meta>
<meta property="schema:accessibilityHazard">noMotionSimulationHazard</meta>
<meta property="schema:accessMode">textual</meta>
<meta property="schema:accessMode">visual</meta>
<meta property="schema:accessModeSufficient">textual</meta>
<meta property="schema:accessibilitySummary">
This publication conforms to WCAG 2.1 Level AA.
All images have alt text. Page list navigation is provided.
</meta>ONIX Accessibility Metadata
ONIX (ONline Information eXchange) is the publishing industry standard for metadata exchange between publishers, distributors, and retailers. ONIX 3.0 includes accessibility fields that map to EPUB's schema.org properties:
- List 196 (E-publication Accessibility Details): codes for features like full alternative text (09), table of contents navigation (11), page navigation (29), ARIA roles (10), and TTS optimized (17)
- List 143 (ONIX for Books): conformance statements (e.g., "EPUB Accessibility 1.1 - WCAG 2.1 Level AA")
ONIX metadata travels through the supply chain to retailers. Amazon, Apple, Kobo, and distributors like IngramSpark ingest ONIX feeds. If your ONIX record declares accessibility features, stores can surface your book in accessibility-filtered searches and display accessibility information on the product page.
Legal Requirements: EAA, ADA, and Beyond
The legal landscape for ebook accessibility has teeth:
EU European Accessibility Act (EAA)
Directive 2019/882, the European Accessibility Act, became enforceable on June 28, 2025. It requires ebooks and ebook reading software sold in the EU to be accessible. Specifically: ebook content must meet EPUB Accessibility 1.1 conformance, DRM must not block assistive technology, reading apps must support screen readers and user customization, and publishers must provide accessibility metadata.
The EAA applies to anyone selling ebooks in the EU, regardless of where the publisher is based. Micro-enterprises (fewer than 10 employees AND annual turnover under EUR 2 million) are exempt from some requirements, but larger self-publishers and all traditional publishers are covered. Penalties are determined by each EU member state — expect fines similar to GDPR enforcement (significant enough to motivate compliance).
US: ADA and Section 508
The Americans with Disabilities Act (ADA) applies to public accommodations, which courts have increasingly interpreted to include digital content. Educational institutions receiving federal funding are covered by Section 504 and Section 508, which explicitly require accessible digital publications. Multiple US universities have faced legal action (and lost) over inaccessible ebook content in course materials.
For commercial ebook publishers, ADA compliance is less explicitly defined than the EAA but the legal trend is toward broader applicability. Making ebooks accessible now is both the right thing to do and a proactive legal strategy.
Testing Ebook Accessibility
Tools for validating ebook accessibility:
- Ace by DAISY — The primary EPUB accessibility checking tool. Runs automated checks for EPUB Accessibility conformance: semantic structure, alt text presence, reading order, accessibility metadata, and WCAG violations. Produces HTML reports with specific findings. Install via npm:
npm install -g @daisy/ace, run:ace book.epub - epubcheck — General EPUB validation includes some accessibility checks (missing alt text, broken navigation). Not a substitute for Ace, but a first-pass filter
- Manual testing — Automated tools catch structural issues but can't evaluate alt text quality, reading order logic, or whether extended descriptions adequately convey image content. Manual review with a screen reader (VoiceOver on Mac, NVDA on Windows) is essential for thorough testing
- SMART by DAISY — Manual testing guide that walks evaluators through the checks Ace can't automate
Accessible ebook design is good ebook design. Proper heading hierarchy, semantic markup, complete navigation, and alternative text make books work better for all readers — not just those using assistive technology. A well-structured EPUB with accessibility features is also easier to convert between formats, renders more consistently across devices, and passes platform quality checks without issues.
The legal requirements are clear and enforceable. The tools exist (Ace, epubcheck, Calibre). The technical standards are well-documented (EPUB Accessibility 1.1, WCAG 2.1). The gap is implementation — most publishers haven't caught up with the law. If you're publishing ebooks, start with semantic markup and alt text. Add page lists and landmarks. Include accessibility metadata. These aren't aspirational goals; they're minimum requirements in 2026.