Implementation guide / Accessible publishing
EPUB accessibility metadata: a publisher’s practical guide.
A focused guide to EPUB accessibility metadata for publishers: what to capture, how to make claims responsibly, how metadata supports discovery, and how to test its delivery across reader and distribution workflows.
Scope and review note
Accessibility metadata describes the accessibility characteristics of a particular publication. It does not by itself establish full legal compliance or guarantee every reader’s experience. Use the current EPUB Accessibility specification, appropriate legal guidance, specialist testing and title-level evidence when making claims.
01 / The guide
01
Metadata helps readers find the access information that matters.
EPUB Accessibility defines content-conformance and accessibility-metadata requirements intended to make the accessible qualities of an EPUB publication discoverable. The point is practical: a reader, library, bookseller or other distribution partner needs reliable information to decide whether a title meets a particular need. Metadata should therefore be produced from the publication’s real accessibility evidence, not copied from a generic template.
- Treat metadata as title-level information that can be checked against the supplied EPUB and its supporting evidence.
- Decide who owns the accessibility facts, who enters them and who approves changes before distribution.
- Carry the same verified information into distribution records and reader-facing product information where the channel supports it.
02
Start with the metadata fields that describe how the publication can be used.
EPUB Accessibility 1.1 requires conforming EPUB publications to include schema.org accessibility metadata for access mode, accessibility features and accessibility hazards in the package document. It recommends an accessibility summary and sufficient access modes where applicable. These fields answer different questions: what sensory or cognitive modes are needed, which features or adaptations are present, whether relevant hazards exist, and whether a reader can access the essential content through a defined combination of modes.
- Record `accessMode`, `accessibilityFeature` and `accessibilityHazard` from the actual publication rather than a publisher-wide default.
- Use `accessModeSufficient` to describe the combination of modes that provides access to the essential content when appropriate.
- Use an `accessibilitySummary` only to clarify relevant strengths or known limitations that the other fields do not already communicate.
03
Make conformance claims only when the evidence supports them.
Accessibility metadata is not a shortcut to a conformance claim. W3C’s techniques are advisory and explain that they cannot be used in isolation to make one. A responsible publisher workflow separates automated checks, editorial quality assurance, specialist testing, known exceptions and the wording of any public claim. The evidence and metadata should be re-reviewed whenever the EPUB, its reading features or its distribution version changes.
- Keep the accessibility review record, test results, known limitations and metadata together for the title version being distributed.
- Distinguish a verified conformance statement from a description of individual features such as alternative text, table of contents or display transformability.
- Use precise language about gaps or limitations; do not use metadata to hide content that remains difficult to access.
04
Deliver and display metadata so it survives the distribution journey.
Accessibility information has less value if it remains only inside a production file. The W3C display guidance describes ways to turn package-document metadata into reader-facing information such as ways of reading, conformance, navigation, rich content and hazards. Publishers should decide how the information moves to their sales, library and direct-reader channels, how it is displayed, and how readers can raise questions when the description does not match their experience.
- Test the package metadata, distribution metadata and the reader-facing display as one publishable set.
- Present reader-facing information in plain language, retaining the title-specific facts and any relevant limitations.
- Define a correction route for reported metadata errors and update the title, feeds and channels in a controlled way.
02 / Take this to the meeting
EPUB accessibility metadata release checklist
Use this as a working agenda with decision owners, not a box-ticking exercise.
- 01The title’s package document, accessibility review evidence and applicable content version are identified together.
- 02Required access-mode, accessibility-feature and hazard metadata is populated from verified title-level facts.
- 03Sufficient access modes, accessibility summary and conformance information are included only where they add accurate, non-duplicative information.
- 04Accessibility claims, certification details and known limitations have an accountable approver and supporting evidence.
- 05Metadata moves consistently into relevant distribution records, library/sales feeds and reader-facing product information.
- 06The EPUB, metadata display, real reader journey and error-correction process are tested before and after distribution changes.
03 / Questions
09 Questions publishers ask
It is structured information in an EPUB package document that describes accessibility characteristics such as access modes, features and hazards. It helps readers and distribution partners discover whether a title may meet particular reading needs.
No. Metadata describes characteristics and can support a conformance claim when backed by appropriate evidence, but it does not replace title-level accessibility review, testing or the broader requirements of the EPUB Accessibility specification.
Use a summary to add useful, title-specific clarification that the other metadata fields do not already express—for example, a relevant limitation or a concise description of complex accessibility support. Keep it accurate, plain-language and non-duplicative.
It should be present in the EPUB package document and carried into relevant distribution records and reader-facing product information where the channel supports it. Test what a reader actually sees, not only what is stored in a production system.
More questions? Answers arranged by role — finance, IT, editorial, marketing, operations.
04 / Sources and next reading
