EPUB Accessibility Metadata Lint (EAA)

Checks the accessibility metadata in an EPUB package .opf against EPUB Accessibility 1.1 and the EU Accessibility Act discovery rules, and gives you the exact line to paste. Runs entirely in your browser — nothing is uploaded.

Sweep a whole catalogue folder and keep the dated report — $29 once
$29 once · one licence key per person or team seat · 7-day full refund. An EPUB production freelancer bills $50 to $95 an hour.

Same engine as the VS Code extension, byte for byte.

Install free

Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.

npmDocker Hub
npx @readystack/epub-a11y-metadata-lint <file>
docker run --rm -v "$PWD:/w" getreadystack/epub-a11y-metadata-lint /w

Team? One key for every ReadyStack linter, 5 seats, $149 once

Get one email when this rule changes
We watch the regulation and vendor sources behind EPUB Accessibility Metadata Lint (EAA) every day. When a rule changes, you get a single email with what changed and the updated check. No newsletter.

Get the complete version $29

This page is the working piece. The full pack has everything below.

18 rules over the accessibility metadata in your .opf: 12 findings in the sample file, 9 of them errors, 6 of them invented or malformed values

An EPUB production freelancer bills $50 to $95 an hour.

Buy the full version — $29

Questions people ask

What does it actually check?

It runs 18 rules over the accessibility metadata in an EPUB package file: schema:accessMode, accessModeSufficient, accessibilityFeature, accessibilityHazard, accessibilitySummary, the dcterms:conformsTo conformance string, and a11y:certifiedBy. It reports each finding on its line with the replacement line to paste. The sample file returns 12 findings.

Who is it for?

Ebook production editors and EPUB developers at publishers selling into the EU, plus freelance conversion vendors. Since 28 June 2025 the European Accessibility Act covers e-books, and retailers read the accessibility claim out of the package metadata, so the person editing the .opf is the person who carries it.

Why will a chatbot or EPUBCheck not do this?

EPUBCheck validates structure, not vocabulary: altText and sight pass it. A chatbot writes those invented values in the first place. In the sample file 6 of the 12 findings are invented or malformed values, including a conformance string missing the word Level, which no structural validator objects to.

What is free and what is paid?

Checking the file you have open is free, unlimited, with all 18 rules and every fix line: that job finishes. The paid layer is a different axis, scope and ownership: sweep every .opf in a catalogue folder in one run and keep the dated pass/fail report per title for your distributor. $29 once, 7-day full refund.

What would this cost otherwise?

An EPUB production freelancer bills $50 to $95 an hour. Metadata review is an hour or two per title before a title goes out, and a backlist sweep is a day. The extension is $29 once with a 7-day full refund, and the single-file check stays free whether or not you ever hold a key.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

ENDEJAESPT

Find a tool