WoluTools

PDF & Documents

Check an EPUB for basic accessibility problems

Upload an EPUB. It flags missing language tags and image alt text and gives you a worksheet for the checks a person has to do. It does not replace Ace or a WCAG audit.

or drop it here

One EPUB · up to 100 MB

No file at hand? See an example result

Free: 3 checks a day with a free account · Pro €12.99/month for up to 200 a day

Example resultmy-novel.epubSample data showing what the report looks like
  • 3 structure checks passed
  • 3 warnings
  • 3 manual checks

findings.csv

  • Warningchapter3.xhtml image without alt attribute
  • Warningchapter7.xhtml image without alt attribute
  • Warningnav.xhtml no language attribute on <html>

Passed: mimetype first, container.xml present, package document found

manual-review.csv

  • Reading order
  • Alternative text quality
  • Color meaning

Download: findings.csv · epub-inventory.csv · manual-review.csv · manifest.json

BringEPUB
GetBasic accessibility findings, package inventory, manual-review worksheet and manifest
PrivacyEncrypted source · 24-hour result

How the check works

  1. 1

    Add the EPUB

    One file up to 100 MB. There are no settings to choose.

  2. 2

    The package is read

    Structure, language attributes, image alt attributes and scripts are checked in every content document.

  3. 3

    Download four files

    Findings, a file inventory, the manual-review list and a manifest.

A first accessibility pass on an EPUB file

Upload the EPUB

You upload one EPUB of up to 100 megabytes. The tool reads the package instead of rendering pages. It checks that the mimetype, container.xml and package document are in place, flags content documents with no language attribute or with images that have no alt attribute, marks scripts for review, and lists every file in the package with its size and SHA-256 hash. A fixed-layout title gives you the inventory and those attribute findings, but little more. It does not run Ace by DAISY. There are no settings to choose.

The four files you download

You get findings.csv with the missing attributes, epub-inventory.csv with every file in the package, and manual-review.csv. A manifest.json file records the source and a summary, including the note that no automated conformance claim was made. Your EPUB is not changed. Use the inventory to spot stray or missing files, work through findings.csv first, and then move on to the manual list.

The checks only a person can make

The manual-review.csv file lists what has to be checked by reading the book: reading order, the quality of alternative text and whether color alone carries meaning. Markup cannot say whether an alt text is meaningful, so that stays on the list. Heading structure and tables are not checked, so review them as well. An empty findings file only means the attribute checks passed. It does not mean the book is accessible or meets WCAG. A full accessibility review by a person is still needed.

Questions before you run it

Does this replace Ace by DAISY?

No. Ace is not run here and no WCAG conformance is claimed. This checks a small set of machine-readable attributes and hands everything else to the manual-review worksheet.

Which accessibility problems does it actually detect?

Missing language attributes on HTML content documents, images with no alt attribute and scripts that need review. It also checks the basic package structure (mimetype, container.xml, package document) and lists every file. Whether an alt text is meaningful cannot be decided from markup, so it stays on the manual list.

What is in manual-review.csv?

Three checks a person has to make by reading the book: reading order, alternative text quality and color meaning. Headings, tables and anything else markup cannot settle also need a human review.

Can I upload a fixed-layout or a large EPUB?

Any EPUB up to 100 megabytes is accepted. The tool reads the package rather than rendering pages, so a fixed-layout title yields an inventory and attribute findings but little more.

If findings.csv comes back empty, is my book accessible?

No. An empty findings file means the attribute checks passed. The manifest records that no automated conformance claim was made, and the manual worksheet is still outstanding.