EPUB Accessibility Metadata Lint (EAA)
Runs the same checker as the npm package
@readystack/epub-a11y-metadata-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
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
Install
epub-a11y-metadata-lint file
Node 18+. The same 18 rules as the VS Code extension, from a terminal or CI.
Free
- Lints the .opf you have open with all 18 rules and names every missing, mistyped or self-contradicting accessibility metadata value with the exact line to paste. The sample file returns 12 findings, 9 of them errors, 6 of them invented or malformed values such as altText, sight and noFlashing.
--ruleslists every rule
With a licence ($29 once)
- Sweeps every .opf in a catalogue folder in one run and writes a dated pass/fail report per title, the document a distributor or retailer asks for. Different axis from the free layer: scope and a file you keep, not a bigger version of the same check.
@readystack/epub-a11y-metadata-lint --dir ./templates --report html --out report.html
An EPUB production freelancer bills $50 to $95 an hour.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "epub-a11y-metadata-lint": { "command": "npx", "args": ["-y", "@readystack/epub-a11y-metadata-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: EPUB Accessibility Metadata Lint (EAA)
run: npx -y @readystack/epub-a11y-metadata-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/epub-a11y-metadata-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-epub-a11y-metadata-lint
epub-a11y-metadata-lint --help
Metadata
Release files for readystack-epub-a11y-metadata-lint 1.0.7.post1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_epub_a11y_metadata_lint-1.0.7.post1.tar.gz | 17.3 kB | Without provenance | Details for readystack_epub_a11y_metadata_lint-1.0.7.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_epub_a11y_metadata_lint-1.0.7.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_epub_a11y_metadata_lint-1.0.7.post1-py3-none-any.whl |
Total release size: 37.0 kB
Release files / readystack_epub_a11y_metadata_lint-1.0.7.post1.tar.gz
| Download URL | readystack_epub_a11y_metadata_lint-1.0.7.post1.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf8547fbd6685fdde9cce9510075e98a254b5d7ff11a59faa69b47b45081a956
|
|
BLAKE2b-256 checksum How to use checksums |
f1ef1d88e782c4fbc7e63690418cb9c44a1858d3cf05000291f1e852e5fd215d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_epub_a11y_metadata_lint-1.0.7.post1-py3-none-any.whl
| Download URL | readystack_epub_a11y_metadata_lint-1.0.7.post1-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a0b9e7bad1dfa543c0a93474b971c80b37c0ec1db5a8c6baf06a2802f160aa3
|
|
BLAKE2b-256 checksum How to use checksums |
df013c34f2ebdb5f0a47cf12d3562022e4d1ec538999671c0f6597584d15295e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-epub-a11y-metadata-lint 1.0.7.post1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.