Skip to main content
Category: Document Accessibility

Accessible EPUB

Also known as: Accessible ePub, Born-accessible EPUB, Accessible EPUB publication
Simply put

An accessible EPUB is a digital publication in the EPUB format that is designed so people with disabilities can read and navigate it, often using assistive technologies. To be considered accessible, an EPUB generally needs to meet a defined set of requirements, including making its accessibility features discoverable to readers. A publication created to be accessible from the start is sometimes described as 'born-accessible.'

Formal definition

Under the W3C's EPUB Accessibility specification, an accessible EPUB publication is one that conforms to defined accessibility requirements. EPUB Accessibility 1.0 (2017) defined an accessible EPUB as a publication meeting all discovery requirements, WCAG 2.0, and EPUB-specific accessibility requirements, with conformance defined in the specification. EPUB Accessibility 1.1 (2024) continues to frame accessibility around meeting explicit discovery, WCAG, and EPUB-specific requirements while emphasizing that an accessible publication should serve the accessibility needs of individual users through the provision of rich, structured content and metadata. The specification distinguishes discoverability requirements (which surface accessibility metadata so readers can evaluate a publication) from accessibility conformance; a publication may be discoverable while still not meeting full accessibility requirements for a given audience. Practitioners should confirm which WCAG version and conformance level a given specification revision references, and note that this entry describes technical publishing standards rather than legal compliance obligations, which vary by jurisdiction and evolve through regulation and case law. This is not legal advice.

Why it matters

Digital publications reach readers across education, government, and commercial contexts, and an EPUB that is not built with accessibility in mind can effectively exclude people who rely on assistive technologies such as screen readers, refreshable braille displays, or text-to-speech tools. When accessibility is treated as an afterthought and retrofitted later, the process is often more costly and less complete than building it in from the start, which is why the concept of a 'born-accessible' EPUB has gained traction among publishers and standards bodies.

Discoverability is a distinct and important dimension of accessible publishing. The EPUB Accessibility specification separates discoverability requirements, which surface accessibility metadata so readers and distributors can evaluate a publication before acquiring it, from the underlying accessibility conformance of the content itself. This distinction matters in practice: a publication may expose accurate metadata and be classed as discoverable while still not meeting full accessibility requirements for a given audience. Metadata that honestly describes what a title does and does not support allows readers to make informed choices rather than encountering barriers only after purchase or download.

This entry describes technical publishing standards rather than legal compliance obligations. Whether and how accessible publishing requirements apply to a particular organization depends on jurisdiction and evolves through regulation and case law. Readers with legal questions should consult qualified counsel and monitor current agency rulemaking; producing a conforming EPUB is not by itself a guarantee of legal compliance in any jurisdiction.

Who it's relevant to

Publishers and content producers
Organizations creating EPUB titles are responsible for deciding whether to build accessibility in from the start ('born-accessible') or retrofit it later. Understanding the distinction between discoverability requirements and accessibility conformance helps producers publish accurate metadata and set realistic expectations about what a title supports.
Educational institutions and textbook providers
Accessible EPUBs are a significant concern in education, where students who use assistive technologies need equivalent access to course materials. Institutions procuring or producing digital textbooks can use accessibility metadata to evaluate titles against the needs of their audiences.
Accessibility engineers and QA testers
Those verifying EPUB accessibility need to work from the specification's defined requirements, confirm which WCAG version and level a revision references, and combine automated checks with manual and assistive technology testing, since automated tools detect only a portion of issues.
Assistive technology users and readers
People who read with screen readers, braille displays, or text-to-speech benefit directly from structured content and accurate accessibility metadata, which allow them to evaluate whether a publication meets their needs before acquiring it.
Compliance officers and legal counsel
Those assessing organizational obligations should treat EPUB accessibility as a technical publishing standard and separately evaluate legal requirements, which vary by jurisdiction and evolve through regulation and case law. Conformance to the specification does not by itself establish legal compliance, and qualified counsel should be consulted for specific obligations.

Inside Accessible EPUB

EPUB Accessibility Specification
Accessible EPUB conformance is defined by the W3C's EPUB Accessibility specification (versions such as 1.0 and 1.1), which sets out discovery, WCAG-based content, and EPUB-specific requirements for a publication to be considered accessible.
WCAG Conformance for Content
The specification references the Web Content Accessibility Guidelines (WCAG) as the benchmark for the accessibility of the content itself. WCAG Level AA is the level most commonly cited as a target, though practitioners should confirm the specific version and level referenced by the EPUB Accessibility version they are following.
Accessibility Metadata (Discoverability)
Accessible EPUBs are expected to include machine-readable accessibility metadata that describes features such as text alternatives, navigation, and hazards. This discovery information helps users and distribution systems determine whether a publication meets their needs before acquiring it.
EPUB-Specific Structural Requirements
Beyond WCAG, the specification includes requirements particular to the EPUB format, such as logical reading order, navigational structures (for example a table of contents), and page navigation where applicable, so assistive technologies can traverse the publication effectively.
User-Needs Emphasis
In its non-normative discussion, the specification frames accessibility around meeting the accessibility needs of individual users, alongside the explicit normative discovery, WCAG, and EPUB-specific requirements that define conformance.

Common questions

Answers to the questions practitioners most commonly ask about Accessible EPUB.

Does making an EPUB conform to WCAG automatically make it a fully accessible EPUB?
Not by itself. WCAG conformance addresses the content of an EPUB and is a core part of the requirements, but EPUB Accessibility specifications also define EPUB-specific requirements, including accessibility metadata for discovery. Meeting WCAG success criteria is necessary but generally not sufficient on its own to satisfy the full definition of an accessible EPUB, and conformance to technical requirements does not by itself guarantee a good experience for every user or immunity from legal claims. Manual and assistive technology testing are also commonly needed.
Is an accessible EPUB simply an EPUB that passes automated accessibility checks?
No. Automated testing detects only a portion of potential issues and cannot confirm all EPUB-specific requirements, such as the quality of alternative text or the presence and accuracy of accessibility metadata. An accessible EPUB is generally understood in terms of meeting explicit requirements defined by the applicable EPUB Accessibility specification, which include WCAG conformance, discovery metadata, and EPUB-specific provisions. Human review with assistive technologies is typically required to evaluate real-world usability.
What WCAG conformance level is commonly targeted for an accessible EPUB?
WCAG Level AA is the level most commonly cited as a target across digital accessibility contexts, including EPUB publishing. The applicable EPUB Accessibility specification references WCAG conformance, and publishers should confirm the specific version and level they are targeting against the current specification and any distributor or jurisdictional requirements. This entry is general guidance and not legal advice; consult qualified counsel or current standards documentation for definitive requirements.
What role does accessibility metadata play in an accessible EPUB?
Accessibility metadata supports discovery, allowing readers and distribution platforms to identify the accessibility features, hazards, and conformance of a publication before it is opened. It is a distinct requirement from content-level WCAG conformance. Providing accurate discovery metadata is a recognized part of the EPUB accessibility requirements, and publishers should ensure the metadata reflects the actual state of the publication.
How should images and other non-text content be handled in an accessible EPUB?
Non-text content generally requires text alternatives so it can be conveyed to users who cannot perceive it visually, consistent with WCAG requirements. This commonly includes descriptive alternative text for meaningful images and appropriate handling of decorative images. Because the adequacy of a description is a matter of judgment, human review is typically needed rather than reliance on automated tools alone.
What kind of testing is recommended to verify an accessible EPUB?
A combination of approaches is generally recommended. Automated checks can identify certain issues but detect only a portion of them. Manual review and testing with assistive technologies are commonly needed to evaluate reading order, navigation, alternative text quality, and the overall experience. Verifying accessibility metadata for accuracy is also part of a thorough review process.

Common misconceptions

An EPUB is 'accessible' simply because it meets WCAG success criteria.
EPUB Accessibility conformance is defined by more than WCAG alone. It also requires discovery (accessibility metadata) and EPUB-specific requirements. Meeting WCAG addresses the content layer but does not by itself satisfy the full specification, and automated checks detect only a portion of potential issues; manual and assistive technology testing are generally still needed.
Accessible EPUB is defined solely by meeting the accessibility needs of individual users.
While the specification's non-normative text emphasizes user needs, an Accessible EPUB is defined by explicit, normative requirements covering discovery, WCAG-based content, and EPUB-specific structure. Both the user-needs framing and the concrete conformance requirements are part of the picture.
Producing an Accessible EPUB guarantees legal compliance with the ADA or other laws.
Conformance to the EPUB Accessibility specification is a technical standard, not a legal determination. US legal obligations arise under authorities such as the ADA, Section 508, or Section 504 depending on context, and compliance is shaped by regulation and case law. Meeting the specification may support accessibility goals but does not guarantee immunity from legal claims. Consult qualified legal counsel for compliance questions.

Best practices

Identify which version of the EPUB Accessibility specification (for example 1.0 or 1.1) you are targeting and confirm the specific WCAG version and conformance level it references before beginning production.
Include complete, accurate accessibility metadata so that users and distribution systems can discover the publication's accessibility features before acquisition.
Address the content layer against the referenced WCAG criteria, with Level AA commonly cited as a target, while treating this as one part of overall EPUB conformance rather than the whole.
Implement EPUB-specific structural requirements such as logical reading order and navigational structures so assistive technologies can traverse the publication.
Supplement automated checking with manual review and testing using assistive technologies, since automated tools detect only a portion of accessibility issues.
Treat conformance as distinct from legal compliance; consult qualified legal counsel and current regulatory guidance for obligations under laws such as the ADA or Section 508.