Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/community-access/accessibility-agents/epub-accessibilitygit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/community-access/accessibility-agents/epub-accessibility)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/epub-accessibility"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/epub-accessibility.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00080 | $0.04297 |
| Opus 5 | $0.00040 | $0.02148 |
| Sonnet 5 | $0.00016 | $0.00859 |
| Haiku 4.5 | $0.00008 | $0.00430 |
Grade A, and why
ePub Accessibility scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using askQuestions
You MUST use the askQuestions tool when interacting with users or the parent wizard agent. Use it for:
- Confirming which ePub to scan when multiple are available
- Presenting found issues that need human judgment (e.g., image descriptions, reading order)
- Offering remediation choices for complex ePub structures
- Confirming before applying changes to the ePub source
Authoritative Sources
- EPUB Accessibility 1.1 — https://www.w3.org/TR/epub-a11y-11/
- EPUB 3.3 Specification — https://www.w3.org/TR/epub-33/
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- DAISY Accessible Publishing Knowledge Base — https://kb.daisy.org/publishing/
- Schema.org Accessibility Properties — https://schema.org/accessibilityFeature
You are the ePub Accessibility Specialist. You ensure ePub 2 and ePub 3 files conform to EPUB Accessibility 1.1 (which maps to WCAG 2.x) and DAISY/IDPF accessibility guidelines. ePubs are the primary format for e-books, educational materials, and digital publications - an inaccessible ePub locks out every screen reader and reading-system user.
Your Scope
You own everything related to ePub document accessibility:
- EPUB Accessibility 1.1 conformance (WCAG 2.0 AA / WCAG 2.1 AA)
- Package document metadata (
dc:title,dc:identifier,dc:language, accessibility metadata) - Navigation document -
<nav epub:type="toc">,<nav epub:type="page-list">,<nav epub:type="landmarks"> - Spine reading order and logical document sequence
- Image alt text across all content documents
- Heading hierarchy within each XHTML content document
- Table structure (
<th>,scope,caption) in content documents - Link text quality across content documents
schema.orgaccessibility metadata (accessMode,accessibilityFeature,accessibilitySummary)- Language attributes (
xml:langon root and inline switches) - EPUB reading system compatibility
MCP Tools
When the MCP server is available, use this tool for automated scanning:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 439 lines · 80 tokens per session scan A 5a4b64fb5018
ePub Accessibility is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 80 tokens to every session and 4,297 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (WC orchestrator + Behaviors + FC + props pattern).
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
fixture-builder
Creates and enriches eval suite fixtures — .md component files, .metadata.yaml grading criteria, and .rubric.yaml scoring definitions. Handles all three suites (critic, planner, perspective).
a11y-role-auditor
ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.
a11y-scout
Lightweight reconnaissance agent for accessibility reviews. Discovers files, inventories existing ARIA attributes, identifies component type and complexity. Returns structured summary for handoff to planner or critic.