EPUB Accessibility 1.1 is the W3C standard that defines how an ebook must be built and tagged so people using screen readers, screen magnifiers, or other assistive technology can actually read it. The World Wide Web Consortium published it as an official Recommendation on October 17, 2024, and it now sits at the center of how publishers meet new legal deadlines.
That matters well beyond large publishing houses. Indie authors and small presses producing their own files — the audience our guide to publishing digital editions is written for — now need to know what the standard actually asks for, not just that it exists.
The urgency isn't theoretical. A separate deadline, tied to European law rather than the standard itself, has already passed: new digital products and services sold in the EU, including ebooks, were required to meet accessibility requirements starting June 28, 2025. EPUB Accessibility 1.1 is the technical route publishers use to get there.
What does EPUB Accessibility 1.1 actually require?
EPUB Accessibility 1.1 requires two things at once: that an ebook's content conforms to the Web Content Accessibility Guidelines (WCAG), and that the file carries metadata describing its accessibility so retailers and reading systems can surface that information before purchase. Both requirements, spelled out in full in the EPUB Accessibility 1.1 Recommendation, apply to the publication as a whole, not to individual pages in isolation.
On the content side, the standard sets WCAG 2.0 Level A as the floor for conformance, with Level AA "strongly recommended" rather than mandatory. On the technical side, it layers EPUB-specific rules on top of WCAG: page navigation that maps digital locations to a print edition's page numbers where one exists, and synchronized text-to-audio playback (EPUB's "media overlays") that conforms to the EPUB 3 specification when a title includes narrated audio. A conformance claim is also expected to name who evaluated the file.
Key takeaway: EPUB Accessibility 1.1 doesn't replace WCAG — it applies WCAG to the whole publication and adds EPUB-native requirements like navigation and synchronized audio on top of it.
Which accessibility metadata fields does every ebook need?
Every EPUB file needs schema.org accessibility properties in its package document — this is the metadata that lets a retailer or library catalog show a title's accessibility features before a reader downloads it. Five properties do most of the work, and the DAISY Consortium, which helps maintain the specification alongside the W3C, documents what each one is for in its schema.org accessibility metadata guide.
| Property | What it tells a retailer or reading system | Example value |
|---|---|---|
| accessMode | Which senses are needed to take in the content | textual, visual |
| accessibilityFeature | Specific accessible elements built into the file | alternative text, structural navigation, MathML |
| accessibilityHazard | Potential hazards the file does or doesn't contain | no flashing, no sound-based hazards |
| accessModeSufficient | Which single mode is enough on its own to use the whole book | textual |
| accessibilitySummary | A short, human-readable overview statement | "Conforms to WCAG 2.0 Level AA" |
Think of these fields the way you'd think of a nutrition label rather than a marketing claim: they describe what's actually in the file, so a screen-reader user or a librarian buying for a low-vision patron doesn't have to guess. Per the DAISY guide, the point is that accessibility information can be discovered "no matter how the publication is distributed or consumed" — the same five properties can be expressed in EPUB 3, EPUB 2, and audiobook manifests alike.
Key takeaway: Metadata isn't decoration — it's how accessibility information travels with the file into stores and catalogs that never open the book itself.
Why does the European Accessibility Act change the timeline?
The European Accessibility Act changes the timeline because it turns a voluntary best practice into a legal requirement for products sold into the EU. The Act itself was adopted in 2019, but its accessibility requirements for digital products and services, including ebooks and e-readers, took effect on June 28, 2025. The W3C has since published a formal note mapping EPUB Accessibility 1.1 directly onto the Act's requirements, to show publishers that conforming to the EPUB standard is a workable path to legal compliance.
Mary Elliott, a partner in Fox Williams LLP's publishing practice, told Publishers Weekly that companies "that haven't yet done so should familiarize themselves with the EAA." Cristina Mussinelli, secretary general of Fondazione LIA, made the case that compliance can't be partial: "if one segment is not in compliance, all the work done by the publishers won't make any difference" — a point that applies as much to a single-author small press as to a major imprint, since the Act reaches across publishers, e-tailers, and e-reader makers alike.
Not every publisher is covered the same way. Micro-enterprises with fewer than 10 employees and under €2 million in annual turnover are exempt, and companies that can show compliance would create a "disproportionate burden" may also qualify for exceptions. There's also a transition allowance: services already on the market before the deadline can keep running in their existing form until 2030, though the W3C's own mapping note stresses that publishers shouldn't treat that as a reason to delay.
Key takeaway: If you sell ebooks into the EU and don't qualify for the micro-enterprise exemption, June 28, 2025 has already passed — building to EPUB Accessibility 1.1 is the documented way to meet the Act's requirements.
How do you add accessibility metadata to an EPUB file?
Retrofitting accessibility after a book is finished is always harder than building it in from the start, so the fixes below are ordered the way they should happen in your production process, not the way you'd discover problems after the fact.
- Structure before styling. Use real semantic headings, a logical reading order, and descriptive alternative text for images while you're still building the file — not as a pass added after layout is locked.
- Check against WCAG 2.0, at minimum Level A. Treat Level AA as the target rather than the exception; it's what the standard recommends and what EU compliance discussions increasingly assume.
- Add the five schema.org properties to the package document. Fill in accessMode, accessibilityFeature, accessibilityHazard, accessModeSufficient, and accessibilitySummary based on what the file actually contains — not what you hope it contains.
- Handle media overlays and page navigation if they apply. If your edition includes narrated audio or mirrors a print edition's page numbers, confirm those features conform to the EPUB 3 specification before publishing.
- Test with an accessibility checker before you claim conformance. A conformance claim is expected to note who evaluated the file — don't assert WCAG AA in your metadata unless someone has actually checked for it.
Key takeaway: Accessibility metadata should describe a file you've actually verified, in that order — structure, WCAG check, metadata, EPUB-specific features, then a real conformance test.
Common mistakes when preparing an accessible EPUB
- Treating alt text as optional polish. It's one of the accessibility features the metadata is supposed to report — skipping it and still claiming the feature is inaccurate.
- Leaving accessibilityHazard blank. An empty field reads as unknown, not as "no hazards." State explicitly that a title contains no flashing, sound, or motion hazards if that's true.
- Claiming AA conformance without testing. A summary statement is a claim a retailer and a reader will rely on; only write it after checking.
- Assuming backlist titles are automatically covered by the EAA transition allowance. The W3C's own guidance treats the 2030 allowance for existing services as a reason to plan, not a reason to wait.
Frequently Asked Questions
When did the European Accessibility Act's ebook requirements take effect?
New digital products and services sold in the EU, including ebooks, were required to meet the Act's accessibility requirements starting June 28, 2025. The Act itself was adopted in 2019, giving the industry a multi-year runway to prepare.
Are any publishers exempt from the European Accessibility Act?
Micro-enterprises with fewer than 10 employees and under €2 million in annual turnover are exempt. Publishers facing a genuine "disproportionate burden" in complying may also qualify for exceptions, but that determination isn't automatic.
What's the minimum WCAG level EPUB Accessibility 1.1 requires?
The standard sets WCAG 2.0 Level A as the required floor for the publication as a whole, while describing Level AA as strongly recommended rather than mandatory.
Does EPUB Accessibility 1.1 replace WCAG for ebooks?
No. It applies WCAG conformance to the entire publication and adds EPUB-specific requirements on top — including accessibility metadata, page navigation, and synchronized audio playback where applicable.
For more context, read Where goth fashion's darkness actually comes from.
For more context, read How Four Councils Set the Spring 2027 Fashion Week Calendar.
For more context, read Dominika Wycech, High Fashion Model..