Interactive eBook BuilderInteractive eBook Builder
$59 · unlimited access, unlimited eBooksGet it for $59

· Updated · By · 5 min read

EPUB Accessibility Metadata: Beginner’s Guide

epubaccessibilitymetadata

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.

PropertyWhat it saysSpec status
accessModeSenses needed to take in the content: textual, visual, auditory, tactileMust
accessibilityFeatureFeatures present, such as alternative text or extended descriptionsMust
accessibilityHazardFlashing, motion simulation or sound hazards, or their absenceMust
accessModeSufficientAccess modes that are enough to read the whole bookShould
accessibilitySummaryPlain-language note, including known gapsShould

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:

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:

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

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.

FAQ

Is accessibility metadata required for every EPUB?

EPUB Accessibility 1.1 says all EPUB publications must include accessMode, accessibilityFeature and accessibilityHazard metadata, regardless of whether they claim conformance.

Does adding metadata make my EPUB accessible?

No. It only describes the book. Image descriptions, reading order, headings and controls still have to be built and tested.

What is accessModeSufficient for?

It lists a set of access modes that is enough to consume the whole book. A book with both text and audio can list more than one set.

Ship niche eBooks with agents already built.

Get the Interactive eBook Builder for $59