EPUB Accessibility 1.2: The Publisher Release Checklist
W3C issued a September 2026 draft of EPUB Accessibility 1.2. Use this release gate for content, conformance, metadata, evaluation, and reader support.
Direct answer: EPUB Accessibility 1.2 combines accessible-content requirements with metadata that lets readers and distribution systems discover a book’s accessibility. The September 12, 2026 document is a W3C Candidate Recommendation Draft, so publishers can adopt its workflow improvements now while describing the specification accurately as a work in progress.
An ebook can be accessible and still fail the reader who needs that accessibility if the metadata never says what the file can do.
That is the central operational lesson of EPUB Accessibility 1.2. W3C’s September 12 Candidate Recommendation Draft covers both the accessibility of the publication itself and the information that makes those qualities discoverable to readers, retailers, libraries, procurement systems, and reading platforms.
For publishers, accessibility is therefore not one QA test at the end of production. It is a linked system of content structure, evaluation, metadata, evidence, and reader support.
First: describe the status correctly
EPUB Accessibility 1.2 was published on September 12, 2026 as a Candidate Recommendation Draft. W3C explicitly identifies it as a draft that may be updated, replaced, or obsoleted. Publishers should not call it a final Recommendation.
That does not make it irrelevant to production. Candidate-stage work can provide a strong picture of the direction of the standard. The professional approach is to use the draft to improve workflows while monitoring future changes and making conformance claims only when they are actually supported.
Accessibility has two halves: content and discoverability
The first half is the book itself: meaningful structure, correct reading order, navigation, text alternatives, appropriate landmarks, usable links, understandable tables, page navigation when needed, and conformance with the selected WCAG level and version.
The second half is discoverability: metadata that communicates access modes, accessibility features, hazards, sufficient access modes, conformance information, evaluator details, an accessibility summary, and other machine-readable information.
A publisher that solves only the first half leaves retailers and readers guessing. A publisher that solves only the second half risks making claims the actual EPUB cannot support.
WCAG level: record exactly what you tested
The 1.2 draft requires at least Level A for the selected WCAG 2 version and strongly recommends Level AA. It also explains that legal, procurement, or distributor requirements may impose a higher or more specific threshold. Publishers should therefore record the exact WCAG version and level used rather than writing a vague “accessible” claim.
Where feasible, targeting the latest applicable WCAG 2 version at Level AA is a stronger production goal, but the formal claim must match the evidence.
The EPUB Accessibility Release Gate
| Gate | Evidence required |
|---|---|
| Structural validation | EPUB validation and package review. |
| Accessibility testing | Automated report plus documented manual checks. |
| Conformance claim | Exact specification, WCAG version, and level, only when verified. |
| Evaluator record | Name, date, credentials where applicable, and report link or retained report. |
| Discoverability metadata | Access modes, features, hazards, sufficient modes, summary, and related fields. |
| Reader support | Accessibility contact email and correction/remediation route. |
| Distribution parity | Accessibility data mapped accurately into ONIX and retailer feeds where supported. |
Automated checking is necessary, but not enough
Validators can catch many structural and technical problems, but they cannot reliably judge whether alternative text communicates the meaning of an image, whether a table is understandable, whether reading order makes sense, or whether navigation works well in representative reading systems.
Manual review should include keyboard or equivalent navigation, headings and landmarks, reading order, links, tables, alt text quality, page lists where present, media alternatives, and the behavior of the book in representative reading systems and assistive technology workflows.
Write an accessibility summary that helps a reader
An accessibility summary should add useful context rather than merely repeat coded metadata in prose. It can explain strengths, limitations, and known deficiencies in plain language. If a book has a feature that cannot be fully remediated, the summary is the place to make that limitation understandable.
The standard also introduces an accessibility contact mechanism so readers can request additional information or report problems. That turns accessibility from a one-time certification exercise into an accountable support process.
Keep the evaluator record with the title
The accessibility evaluation should not disappear into a vendor email or one person’s local drive. Keep the evaluator name, evaluation date, credentials when relevant, report, conformance basis, exceptions, and remediation history with the title-level production record.
That evidence belongs beside the title’s identifiers and rights records. See the rights-provenance standard for the broader title record.
Map accessibility metadata into distribution feeds
Publishing metadata loses value if it remains trapped inside the EPUB. Where ONIX, retailer, library, or distributor systems support accessibility fields, map the information accurately so it travels with the book.
This is the same principle that applies to web discoverability and AI-use transparency: production information should be machine-readable and portable. The AI Discovery Register handles a different discovery layer, while the AI disclosure standard addresses how production transparency survives publication.
Do not make unsupported conformance claims
“Passed an automated checker” is not the same as “conforms to EPUB Accessibility 1.2 and WCAG 2.2 Level AA.” A formal conformance statement should be made only after the required evaluation supports it.
Re-evaluate when substantive content, CSS, navigation, media, packaging, or metadata changes could affect conformance. Accessibility is not a badge applied once and forgotten.
FAQ: EPUB Accessibility 1.2
Is EPUB Accessibility 1.2 final?
No. The September 12, 2026 publication is a W3C Candidate Recommendation Draft and should be described as a work in progress.
Does EPUB Accessibility 1.2 require WCAG 2.2 Level AA?
The draft allows conformance using supported WCAG 2 versions and requires at least Level A, while strongly recommending Level AA. Other laws, buyers, or distributors may require a different threshold.
What makes an accessible EPUB discoverable?
Accurate accessibility metadata, including access modes, sufficient modes, features, hazards, conformance information, summary information, and related evaluator/support data.
What should an accessibility summary contain?
Useful human-readable context that complements the coded metadata, including important strengths or known limitations that help a reader judge whether the publication will work for them.
The Publishing Standards rule
No EPUB should be released until its accessibility content, metadata, evidence, exception record, and reader-support contact are reviewed together.
Accessibility is strongest when it is treated as a production system, not a late-stage repair. The file must work, the metadata must describe it accurately, the evidence must support the claim, and the reader must have a way to report a problem.
Primary Sources and Further Reading
- W3C: EPUB Accessibility 1.2
- W3C: EPUB Accessibility Techniques 1.2
- W3C: EPUB Accessibility 1.2 Explainer
The Four Records Every Modern Publisher Needs
This article is part of the September 19 Publishing Standards mini-series. The four records work together: discovery, rights, AI-use transparency, and accessibility.