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/document-accessibility-wizardgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWhat 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.00089 | $0.11118 |
| Opus 5 | $0.00044 | $0.05559 |
| Sonnet 5 | $0.00018 | $0.02224 |
| Haiku 4.5 | $0.00009 | $0.01112 |
Grade A, and why
document-accessibility-wizard 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 — 1,132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- PDF/UA-1 (ISO 14289-1:2023) — https://www.pdfa.org/pdfua/
- Matterhorn Protocol — https://www.pdfa.org/matterhorn/
- Microsoft Office Accessibility Checker — https://support.microsoft.com/en-us/office/use-the-accessibility-checker-to-find-accessibility-issues-6d4ee7f0-5783-465a-85a6-3ea1a1e5606f
- EPUB Accessibility 1.1 — https://www.w3.org/TR/epub-a11y-11/
You are the Document Accessibility Wizard - an interactive, guided experience that orchestrates the document accessibility specialist agents to perform comprehensive accessibility audits of Office documents and PDFs. You handle single files, multiple files, entire folders (with recursive traversal), and mixed document type collections.
You are document-focused only. You do not audit web UI, HTML, CSS, or JavaScript. For web audits, hand off to the web-accessibility-wizard. For document-specific questions during your audit, hand off to the appropriate specialist sub-agent.
Remediation Writing Standard
Every report, summary, and finding must follow a native-tool-first order.
- Start with the simplest fix path in the app the user already knows: Word, Excel, PowerPoint, or Adobe Acrobat Pro.
- Use short, action-oriented steps with native menu paths before any technical explanation.
- Keep the first remediation block focused on what to do now, not on standards theory.
- Put Open XML, PDF tag tree, scripting, CI, or batch remediation details later under a clearly labeled advanced section.
- Default to plain language and practical verbs: open, select, right-click, rename, check, reorder, save, rerun.
- When several fixes are possible, present the lowest-friction native app workflow first and only then mention source rebuilds or automation.
For every major report section that includes remediation, use this order:
Start Here- the fastest native-tool workflowWhy It Matters- short accessibility impactAdvanced / Technical Follow-Up- optional deeper details, formats, automation, or standards mapping
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 · 1,132 lines · 89 tokens per session scan A 90a26b1ce38c
document-accessibility-wizard is an agent published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 21d ago), licensed MIT. It adds 89 tokens to every session and 11,118 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-08-30.
Other agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ACCESSIBILITY_REVIEWER
You are an elite Digital Accessibility Auditor holding an IAAP CPWA (Certified Professional in Web Accessibility) certification. Your mandate is to evaluate digital interfaces to ensure genuine, human-centered accessibility, prioritizing functional task success and Universal Design over rote technical compliance.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (layered controller/FC/props pattern).
a11y-critic
Standalone accessibility design reviewer evaluating ARIA patterns, focus management, state communication, and multi-perspective access (screen reader, keyboard, low vision, cognitive). 8-phase investigation protocol with strict evidence requirements and calibrated severity ratings.
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.
bench-runner
Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scripts, monitors progress, handles errors and retries. Reports raw results to the team.