Skip to main content

Accessibility

EPUB Accessibility Checker

Check whether your EPUB meets basic accessibility requirements. The checker looks for missing image alt text, heading hierarchy issues, missing language metadata, navigation structure, and reading order. Use the report to improve accessibility for screen reader users before publishing.

Runs in your browserPrivate by designEPUB

Input formats

EPUB

Output formats

Accessibility Report

Common uses

  • Check whether images have alt text for screen readers
  • Verify heading structure is logical and navigable
  • Check that the book language is set correctly
  • Identify accessibility gaps before submitting to library or institutional distributors

Limitations

  • This tool checks common accessibility basics, not full WCAG 2.1 or EPUB Accessibility 1.1 compliance.
  • Color contrast cannot be checked from EPUB source files.
  • For full compliance, use an accessibility audit tool such as Ace by DAISY.

Your e-book files, handled privately

This tool runs entirely in your browser. On this site, your files are not uploaded to a server. This tool does not remove DRM or bypass copyright protection. Only upload files you own or have permission to process.

Where this checker fits in an EPUB workflow

This is a first-pass accessibility screen for anyone shipping a reflowable EPUB: a self-publisher preparing a title for a store, an editor handing files to a library or institutional distributor, or a developer who just ran a conversion and wants to confirm nothing structural broke. It targets the gaps that most often block screen-reader use — images with no alt attribute, a missing language declaration, no table of contents, an empty reading order — so you can catch them before a distributor's intake check or an end reader does.

It pairs naturally with the EPUB Validator and EPUB Inspector. Validate the file's structure first, use this checker to surface accessibility-specific issues, then open the Inspector if you need to see exactly which content file an image or heading lives in. For students and admins submitting coursework or reports as EPUB, it is a quick way to confirm the book is navigable and language-tagged before it goes into a shared collection.

It is not a publishing gate or a certification. Treat the output as a checklist that tells you where to look, not a stamp that says the book is compliant.

Running a check and reading the report

Drop or select a single .epub file. Everything runs locally in your browser — the file is parsed in memory, nothing is uploaded, and closing the tab discards it. DRM-protected files are detected and refused, since assistive technology cannot read them and the tool will not attempt to.

The checker unpacks the EPUB and runs grouped checks: Metadata (title, language, author), Navigation (an EPUB 3 nav.xhtml and a table of contents via nav or NCX), Structure (correct mimetype, a non-empty spine for linear reading order, DRM status, and file size), and Media (it parses each spine HTML file and counts img tags missing an alt attribute). Each result is marked pass, warning, or fail with a short explanation, and a summary tallies the three counts. You can download the whole thing as a plain-text report stamped with the filename and date.

What it does not do: it does not check color contrast (not derivable from EPUB source), does not judge whether existing alt text is meaningful, does not parse heading levels beyond what the listed checks cover, and does not verify full WCAG 2.1 or EPUB Accessibility 1.1 conformance.

Pitfalls and where it can mislead

The biggest trap is reading a clean alt-text result as 'images are described.' The check only confirms an alt attribute exists on each img tag in the spine — an empty alt="" or a useless value like alt="image1" still passes. It also only inspects img tags inside spine content, so images referenced by CSS, SVG, or files outside the reading order are not counted.

A 'No critical issues' summary means no failures among these specific basic checks, not that the book is accessible. Warnings (a missing nav.xhtml when only an NCX is present, a large file, a missing author) are easy to dismiss but often matter for distributors that require EPUB 3 navigation. Also remember this tool checks one EPUB at a time and only the .epub format — it will not open MOBI, AZW, or PDF.

Verifying your result before you publish

Open the downloaded report and confirm the failures first: a present and correct title, a declared dc:language, a working table of contents, a non-empty spine, and a valid mimetype. Then revisit every warning rather than skipping it, and for any image flagged as missing alt, open the actual content to write a description that conveys the image's purpose — not just to add an empty attribute that satisfies the count.

Because this is a basic automated screen, re-run it after each fix so you can see counts move, and treat a passing media check as a prompt to manually review alt-text quality yourself. For anything going to a library, an institutional collection, or a market with legal accessibility requirements, run a full audit with Ace by DAISY and have a human verify navigation and reading order before release; do not rely on this checker alone as evidence of compliance for official, contractual, or legally regulated distribution.

Frequently asked questions

EPUB Accessibility 1.1 is a W3C specification that defines how EPUB publications should meet WCAG 2 accessibility guidelines. It is increasingly required by publishers and distributors.

Ace by DAISY is the official open-source EPUB accessibility checker from the DAISY Consortium. It provides more comprehensive accessibility checking than this browser-based tool.

It checks common basics: images missing alt text, illogical or skipped heading levels, missing language metadata, the presence of a navigation document, and reading order. It does not check color contrast or perform full WCAG 2.1 or EPUB Accessibility 1.1 compliance — use Ace by DAISY for a complete audit.

No. The EPUB is read and analyzed in your browser. On this site, your files are not uploaded to our servers — the accessibility report is produced on your device.

Related tools

Tool last reviewed: June 30, 2026 · Report a problem