Accessibility
EPUB Accessibility Checker
Check an EPUB for the accessibility basics that can be read from its files. The checker looks for images without alt text, skipped heading levels, pages with no declared language or no title, a missing navigation document or table of contents, and missing accessibility metadata (the schema.org accessMode, accessibilityFeature, accessibilityHazard and accessibilitySummary properties). Use the report to fix gaps before a full audit.
Written by Jay Sudha · Published · Last updated
Input formats
Output formats
Common uses
- Check whether images have alt text for screen readers
- Find skipped heading levels that make navigation by heading harder
- Check that the book and every page declare a language
- Check that accessibility metadata is declared in the package
- Identify accessibility gaps before submitting to library or institutional distributors
Limitations
- It checks accessibility basics, not full WCAG 2 or EPUB Accessibility 1.1 conformance.
- It confirms that an alt attribute exists, not that the description is meaningful.
- Color contrast cannot be checked from EPUB source files.
- For a full audit, use Ace by DAISY and a human review.
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, an editor sending files to a library, or a developer checking a conversion. It targets gaps that matter to screen-reader users and can be read from the files: missing alt attributes, skipped heading levels, pages without a language or title, a missing table of contents, and missing accessibility metadata.
Validate the structure first with the EPUB Validator, use this checker for accessibility, then open the EPUB Inspector to find the file a page or image lives in.
Running a check and reading the report
Drop a single .epub; it is parsed in your browser and never uploaded. DRM-protected files are refused.
The report groups checks into metadata (book title, language, author, and the schema.org accessibility properties accessMode, accessibilityFeature, accessibilityHazard and accessibilitySummary), navigation (an EPUB 3 navigation document and a table of contents), structure (the mimetype file and the reading order), images, and text. Every page in the spine is opened: images are counted with and without an alt attribute, heading levels are followed to find skips such as an h2 followed by an h4, and each page is checked for a lang or xml:lang declaration and a title. Each line is marked pass, warning or fail, and a text report can be downloaded.
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 compare the reading order with the visual layout, and does not verify full WCAG 2 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 element in the book's pages; alt="image1" still passes, and alt="" is counted separately because it marks an image as decorative, which is right for an ornament but wrong for a chart. Images drawn with SVG or set as CSS backgrounds are not counted.
Heading checks are per page: a page that starts at h2 is fine, but a jump from h2 to h4 within a page is reported. Pages with no heading are listed as normal for covers and copyright pages; only a book in which no page has a heading is flagged. The accessibility metadata check confirms the four properties are declared, not that their values are true.
A passing report is a floor, not a certificate. The screen-reader experience also depends on a sensible reading order, meaningful link text, table markup, and marked language changes within a page, none of which this checker evaluates.
Verifying your result before you publish
Fix failures first, such as a missing title or language or images with no alt attribute, then work through the warnings. Write alt text that says what an image shows or why it matters, and use alt="" only for decoration. If the accessibility metadata is missing, add it to the package file; the EPUB Accessibility specification lists the expected values.
Because this is a basic automated screen, re-run it after each fix so you can see counts move, and treat a passing image check as a prompt to 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 person verify navigation and reading order before release.
Frequently asked questions
EPUB Accessibility 1.1 is a W3C specification that sets out how an EPUB meets the WCAG 2 accessibility guidelines and how to describe its accessibility in metadata. In the EU, the European Accessibility Act has covered e-books since 28 June 2025.
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.
Images with no alt attribute (and how many have an empty alt, which marks them decorative), skipped heading levels and a book with no headings at all, pages that do not declare a language or have no title, a missing navigation document or table of contents, a missing book title, language or author, and missing accessibility metadata. It does not check color contrast, judge alt text quality, or test full WCAG 2 or EPUB Accessibility 1.1 conformance: 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: September 27, 2026 · Report a problem