EPUB accessibility metadata describes what your book supports. It does not make the book accessible. The metadata lives in the EPUB's package document (the OPF file), where readers' apps and stores can read it before purchase, so every claim in it should be something you have checked in the exported file.
Which metadata is required?
EPUB Accessibility 1.1, a W3C Recommendation published on 17 October 2024, says every EPUB publication must include schema.org accessMode, accessibilityFeature and accessibilityHazard metadata in the package document, whether or not it claims conformance. It adds that publications should also include accessibilitySummary and accessModeSufficient (W3C: EPUB Accessibility 1.1). So the practical split is three required properties and two strongly recommended ones.
| Property | What it says | Spec status |
|---|---|---|
accessMode | Senses needed to take in the content: textual, visual, auditory, tactile | Must |
accessibilityFeature | Features present, such as alternative text or extended descriptions | Must |
accessibilityHazard | Flashing, motion simulation or sound hazards, or their absence | Must |
accessModeSufficient | Access modes that are enough to read the whole book | Should |
accessibilitySummary | Plain-language note, including known gaps | Should |
What does the metadata look like?
The properties are meta elements inside the package metadata. A simple text book with images that have alternative text might use:
<meta property="schema:accessMode">textual</meta>
<meta property="schema:accessMode">visual</meta>
<meta property="schema:accessModeSufficient">textual</meta>
<meta property="schema:accessibilityFeature">alternativeText</meta>
<meta property="schema:accessibilityHazard">none</meta>
<meta property="schema:accessibilitySummary">Informative images have text alternatives. No hazards were identified.</meta>
Repeat the element for each value. This is an illustrative example, not a template to paste: only list a feature if the book actually has it.
What is a conformance claim?
A conformance claim is a stronger statement than descriptive metadata. The spec says that to claim conformance, a publication must carry a dcterms:conformsTo value that exactly matches a pattern such as "EPUB Accessibility 1.1 - WCAG 2.2 Level AA", and it must also name the evaluator in an a11y:certifiedBy property. If you have not completed an evaluation against WCAG, do not add a conformance string; descriptive metadata alone is the honest option.
Why does metadata not fix accessibility?
Metadata records claims. It does not add missing image descriptions, repair the reading order or fix headings. After you write the metadata, test the exported EPUB:
- Run EPUBCheck for package structure, and Ace by DAISY for machine-checkable accessibility issues.
- Read the book with a screen reader or a reading app's text-to-speech and check the heading outline, table of contents and image descriptions.
- Test any links, quizzes or media with a keyboard, and make sure a reader can leave an interactive element.
- Repeat the affected tests after every content change, and update the metadata to match.
We compare what tools can and cannot see in automated vs manual accessibility checks. If a validator fails first, read our fix for a spine idref error.
What makes a good accessibility summary?
The spec describes the summary as a human-readable note that complements, but does not duplicate, the other metadata, and that also describes known deficiencies. Its own examples show the tone to aim for: a summary for an audiobook-style publication says plainly that it "will not be usable by persons who cannot hear the audio", and one optimized for braille says who it is designed for. Write yours the same way, in one to three short sentences. Name what works, then name what does not.
Does the spec apply to every EPUB version?
Yes. EPUB Accessibility 1.1 says it does not target a single version of EPUB and applies to publications that conform to any version or profile. It also points to a companion document, EPUB Accessibility Techniques 1.1, which explains how to meet each requirement. If you want step-by-step methods for alt text, headings or page navigation, start with the techniques document rather than guessing (W3C: EPUB Accessibility Techniques 1.1).
What are the common beginner mistakes?
These are my own observations from reviewing exports, not spec text:
- Copying a metadata block from another book, including features that this book lacks.
- Listing
alternativeTextwhen only some images have descriptions. Say "partial" in the summary instead. - Leaving the metadata unchanged after adding a video or a quiz, which changes the access modes and hazards.
- Treating a passing EPUBCheck report as an accessibility result. It checks structure, not whether the content is usable.
How do you build a simple review log?
Start a table while drafting. List each text block, image, table, audio clip, video and interactive element, with its location and whether it needs an alternative. When you export, the log tells you which access modes apply (images mean visual; narration means auditory), which features you can truthfully list, and what to mention in the summary. Keep known limits in plain words, for example "charts have short descriptions but no data tables".
Where does a drafting workflow help?
Preparing content with accessibility in mind starts at the draft: short headings, real lists and a description for every image. Interactive eBook Builder helps you plan and draft in Notion with a Configuration Hub and Agents A, B and C (these run in Notion AI, a separate subscription), but it does not generate EPUB metadata or a conformance claim; your export tool and your testing do that. For format choices, see EPUB vs MOBI vs AZW3.
Final checklist
- The three required properties are present in the exported package file.
- Each value matches something you verified in the released EPUB.
- The summary mentions known gaps in plain language.
- No conformance string unless you evaluated against WCAG and named the evaluator.
- The metadata is updated after every content change.
Describe what the current file supports, not what you intended to build. For a repeatable preparation process, Interactive eBook Builder keeps drafts and notes in one workspace.