How do you create accessible EPUBs?

An accessible ePub3 is built on a set of interlocking technical requirements defined by EPUB Accessibility 1.1 and the WCAG 2.1 success criteria it references. Meeting these requirements is not a single task but a set of practices that must be applied consistently across authoring, production, and quality assurance.

Structure and semantics form the foundation. Every element of content must be marked up with the correct HTML5 semantic element: headings use the heading hierarchy (h1 through h6 in logical order), lists use ul or ol, figures use the figure element, tables use thead and th for headers, and so on. Presentational markup, meaning elements used for visual effect rather than for meaning, breaks assistive technology and must be avoided. The EPUB 3 specification supports ARIA roles and epub:type attributes for additional semantic precision in navigation landmarks and structural elements.

Navigation is a distinct and critical requirement. An accessible ePub3 must have an HTML5 nav element providing a table of contents that reflects the full structure of the content. A page list nav element allows readers to synchronise their position with the print edition, which is essential for academic, educational, and reference titles used alongside print. Landmark navigation (using epub:type attributes on the cover, toc, bodymatter, and backmatter) allows assistive technology to jump to major sections directly.

Images and media require careful handling. Every image that conveys meaning must have a descriptive alt attribute. Decorative images, those that add visual interest but convey no information, must have an empty alt attribute (alt="") so screen readers skip them. Complex images such as charts, diagrams, and maps need extended descriptions, either as long descriptions in the markup or as visible captions with sufficient detail. Audio and video content must have captions and transcripts. MathML is required for mathematical expressions; MathML renders equations in a way that screen readers and braille translators can process, whereas images of equations cannot be made accessible.

Colour and contrast must meet WCAG 2.1 success criteria. Text and images of text must have a contrast ratio of at least 4.5:1 against their background (3:1 for large text at 18pt or 14pt bold). Information must not be conveyed by colour alone: if a chart uses colour to distinguish data series, the series must also be distinguishable by pattern, label, or shape. Links must be distinguishable from surrounding text by means other than colour alone.

Finally, the ePub must include accessibility metadata in the package document (OPF file) using schema.org accessibility properties. This metadata declares what features the title has (such as "tableOfContents", "readingOrder", "alternativeText", "MathML") and what hazards it does not have (such as "noFlashingHazard"). Validation of all these requirements uses EPUBCheck for structural validity and ACE by DAISY for accessibility-specific checks.

The approved copy also has to cover EPUB accessibility, Accessible ePub 3 sample, Introduction to accessible ePubs, EPUB best practices, How to make an EPUB accessible, EPUB reading order, EPUB semantic structure, Adobe InDesign to accessible EPUB, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover EPUB accessibility, Accessible ePub 3 sample, Introduction to accessible ePubs, EPUB best practices, How to make an EPUB accessible, EPUB reading order, EPUB semantic structure, Adobe InDesign to accessible EPUB, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover EPUB accessibility, Accessible ePub 3 sample, Introduction to accessible ePubs, EPUB best practices, How to make an EPUB accessible, EPUB reading order, EPUB semantic structure, Adobe InDesign to accessible EPUB, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover EPUB accessibility, Accessible ePub 3 sample, Introduction to accessible ePubs, EPUB best practices, How to make an EPUB accessible, EPUB reading order, EPUB semantic structure, Adobe InDesign to accessible EPUB, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover EPUB accessibility, Accessible ePub 3 sample, Introduction to accessible ePubs, EPUB best practices, How to make an EPUB accessible, EPUB reading order, EPUB semantic structure, Adobe InDesign to accessible EPUB, each of which a publisher expects answered plainly rather than named in passing.

Provisional paragraph. An approved version explains how accessible epub is decided in practice, who signs it off, and what a publisher has to supply before the work can start.

Provisional paragraph. It will set out where accessible epub sits in the production line, which steps depend on it, and what goes wrong downstream when it is skipped.

Provisional paragraph. The approved text names the file formats involved in accessible epub, the checks each one needs, and the point at which a title is considered finished.

Provisional paragraph. Here the approved copy answers the cost question about accessible epub honestly: what drives the price, what a publisher can do in-house, and what is worth buying.

Provisional paragraph. It compares the common approaches to accessible epub, says which suits a small list and which suits a large one, and does not pretend the answer is the same for both.

Provisional paragraph. This is where the approved copy handles the edge cases in accessible epub — tables, formulas, footnotes, illustrations — rather than leaving them to a support ticket.

Provisional paragraph. The approved version records what a publisher should ask a supplier about accessible epub, and which answers should end the conversation.

Provisional paragraph. It explains how accessible epub is measured, what a reasonable turnaround looks like, and how a publisher can tell a good result from a merely finished one.

Provisional paragraph. An approved version explains how accessible epub is decided in practice, who signs it off, and what a publisher has to supply before the work can start. (2)

Provisional paragraph. It will set out where accessible epub sits in the production line, which steps depend on it, and what goes wrong downstream when it is skipped. (2)

Provisional paragraph. The approved text names the file formats involved in accessible epub, the checks each one needs, and the point at which a title is considered finished. (2)

Provisional paragraph. Here the approved copy answers the cost question about accessible epub honestly: what drives the price, what a publisher can do in-house, and what is worth buying. (2)

Provisional paragraph. It compares the common approaches to accessible epub, says which suits a small list and which suits a large one, and does not pretend the answer is the same for both. (2)

Provisional paragraph. This is where the approved copy handles the edge cases in accessible epub — tables, formulas, footnotes, illustrations — rather than leaving them to a support ticket. (2)

Provisional paragraph. The approved version records what a publisher should ask a supplier about accessible epub, and which answers should end the conversation. (2)

Provisional paragraph. It explains how accessible epub is measured, what a reasonable turnaround looks like, and how a publisher can tell a good result from a merely finished one. (2)

Provisional paragraph. An approved version explains how accessible epub is decided in practice, who signs it off, and what a publisher has to supply before the work can start. (3)

Provisional paragraph. It will set out where accessible epub sits in the production line, which steps depend on it, and what goes wrong downstream when it is skipped. (3)

Provisional paragraph. The approved text names the file formats involved in accessible epub, the checks each one needs, and the point at which a title is considered finished. (3) Provisional note 1: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 2: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 3: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 4: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 5: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 6: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 7: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 8: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 9: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 10: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 11: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 12: the approved copy will say more here about accessible epub than a placeholder can. Provisional note 13: the approved copy will say more here about accessible epub than a placeholder can.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.