Yes — whether an ebook reads well aloud or lets a screen-reader user jump straight to chapter twelve comes down to the file itself, not the device. Per the W3C's EPUB Accessibility 1.1 specification, a conformant EPUB must meet at least WCAG 2.0 Level A, carry a defined set of accessibility metadata, and provide real structural navigation — requirements that sit inside the file long before any reading app opens it.
That distinction matters for two different readers of this site: the reader choosing an accessible reading app, and the indie author deciding whether accessibility work is worth the production time. Both questions have the same documented answer, and it starts with what the specification actually mandates.
What Does EPUB Accessibility 1.1 Actually Require?
Per the W3C specification, a conformant EPUB must meet Web Content Accessibility Guidelines (WCAG) at Level A as a floor, though the spec text notes Level AA delivers substantially better outcomes and is the recommended target. Publishers can claim conformance against WCAG 2.0, 2.1, or 2.2, at Level A, AA, or AAA, so two files can both be "accessible" and still differ sharply in what they actually deliver.
The spec also sets structural requirements beyond raw text access. Ebooks that mirror a print edition must provide a page list and page-break markers tied to that edition's ISBN or ISSN, so a reader can cite or navigate to the same page a print reader would use. Any synchronized audio narration included in the file must cover the full text, follow logical reading order, and let a listener skip secondary content — a requirement written specifically for readers who can't simply flip past a sidebar.
What Metadata Actually Has to Be in the File?
Per the specification, every conformant EPUB carries Schema.org accessibility metadata inside its package document, not as an external claim. That includes accessMode (which senses — textual, visual, auditory, tactile — the content requires), accessibilityFeature (the specific accommodations present, such as alt text or captions), and accessibilityHazard (flags for flashing, motion, or sound). The spec recommends adding accessibilitySummary, a plain-language overview, and accessModeSufficient, which spells out which combinations of senses are enough to read the whole book.
Conformance itself is declared as a specific metadata string — "EPUB Accessibility 1.1 – WCAG [version] Level [A/AA/AAA]" — paired with a certifiedBy property naming who evaluated the file: the publisher, the author, or a third party. None of this is cosmetic. A reading app that respects the standard uses exactly this metadata to decide, before opening the book, whether it can announce hazards, offer a page list, or route a screen reader correctly.
Who Actually Builds Reading Systems Around This Standard?
The organizations most active in applying it aren't retail bookstores. The DAISY Consortium, a nonprofit that has worked on accessible digital publishing standards for more than two decades, co-develops the EPUB specifications directly with the W3C's Publishing Maintenance Working Group — as of this writing, DAISY notes the W3C is inviting implementations of the next round, EPUB 3.4 and EPUB Accessibility 1.2, meaning the requirements above are a floor that keeps moving, not a fixed target.
On the reading-system side, Bookshare — an accessible ebook library run by the nonprofit Benetech and backed by the U.S. Department of Education — operates its own Bookshare Reader app across web browsers, smartphones, tablets, and Alexa-enabled smart speakers, built to read text aloud with karaoke-style highlighting, enlarge it, or render it in braille. The Library of Congress's National Library Service for the Blind and Print Disabled (NLS) runs a parallel track: a free audiobook and braille library for anyone with low vision, blindness, or a physical or reading disability, delivered through instant downloads on its BARD platform and the BARD Mobile app, with playback devices loaned out at no cost. Neither service is a general-purpose bookstore app, and neither one exists because a device maker decided to add a feature — both exist because the underlying files and metadata support it.
What Should Indie Authors Actually Do About This?
For self-published authors, the practical implication is upstream of any single retailer or device. The metadata fields above — accessMode, accessibilityFeature, accessibilityHazard, and a conformance string with a named evaluator — live in the EPUB's package document, which most modern ebook-production tools can generate or edit directly. Skipping them doesn't make a book unreadable; it makes it unreadable well by any tool built to respect the standard, from Bookshare Reader to any future reading app that checks the same metadata before rendering.
The specification does not require paying a certifying body to make an accessibility claim — the certifiedBy field explicitly allows the author or publisher to self-declare, alongside the third-party option. What the sources here don't establish is a specific cost figure for accessibility remediation or a list of which mainstream retail storefronts enforce the standard at intake; authors weighing that trade-off should treat those as open questions rather than assume either a fixed price tag or universal enforcement.
Conformance Levels at a Glance
| Level | What It Requires | Who Sets It |
|---|---|---|
| WCAG Level A | Minimum floor for EPUB Accessibility 1.1 conformance; kept for backward compatibility with older content | W3C, EPUB Accessibility 1.1 |
| WCAG Level AA | Recommended target; the spec states it delivers substantially better accessibility outcomes than Level A | W3C, EPUB Accessibility 1.1 |
| WCAG Level AAA | Highest declarable conformance level under the spec's conformance-claim metadata string | W3C, EPUB Accessibility 1.1 |
Frequently Asked Questions
Does an accessible EPUB cost more to produce than a standard one? The sources here don't establish a specific cost figure — the specification itself is free to implement, and the certifiedBy field allows self-declaration rather than requiring a paid third-party evaluation.
Does adding accessibility metadata break the file for regular reading apps? The metadata lives in the EPUB's standard package document per the W3C specification, so it doesn't require a separate file or format — apps that ignore it simply don't act on it.
Where can readers with print disabilities get accessible titles for free? Per NLS and Bookshare's own descriptions, NLS offers free audiobooks, braille, and loaned playback devices to eligible readers, and Bookshare offers 10,000 public-domain titles free to anyone worldwide, with full membership for broader access.
For a related tools perspective, read How to Check Your EPUB for Accessibility Before Publishing.