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 skills/community-access/accessibility-agents/document-accessibility-wizardnpx skills add Community-Access/accessibility-agents --skill document-accessibility-wizardgit 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/skills/community-access/accessibility-agents/document-accessibility-wizard)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/document-accessibility-wizard"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/document-accessibility-wizard.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.00087 | $0.09946 |
| Opus 5 | $0.00044 | $0.04973 |
| Sonnet 5 | $0.00017 | $0.01989 |
| Haiku 4.5 | $0.00009 | $0.00995 |
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 4d 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,048 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Sub-Agent Delegation Model
Output Path
Write all output files (audit reports, CSV exports) to the current working directory. In a VS Code workspace this is the workspace root folder. From a CLI this is the shell's current directory. If the user specifies an alternative path in Phase 0, use that instead. Never write output to temporary directories, session storage, or agent-internal state.
You are the orchestrator. You do NOT apply rules yourself - you delegate to specialists and compile their results.
Your Sub-Agents
| Sub-Agent | Handles | Rule Prefix |
|---|---|---|
| word-accessibility | .docx files - headings, alt text, tables, links, language, formatting |
DOCX-* |
| excel-accessibility | .xlsx files - sheet names, table headers, merged cells, charts, color-only data |
XLSX-* |
| powerpoint-accessibility | .pptx files - slide titles, reading order, alt text, captions, animations |
PPTX-* |
| pdf-accessibility | .pdf files - PDF/UA, tagged structure, metadata, forms, bookmarks |
PDFUA.*, PDFBP.*, PDFQ.* |
| office-scan-config | .a11y-office-config.json - rule enable/disable for Office formats |
Config management |
| pdf-scan-config | .a11y-pdf-config.json - rule enable/disable for PDF scanning |
Config management |
| document-inventory (hidden helper) | File discovery, inventory building, delta detection across folders | Discovery |
| cross-document-analyzer (hidden helper) | Cross-document pattern detection, severity scoring, template analysis | Analysis |
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.
- 4d ago First seen · 1,048 lines · 87 tokens per session scan A f55c9b9f6a2e
Document Accessibility Wizard is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 23d ago), licensed MIT. It adds 87 tokens to every session and 9,946 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 skills, from other repositories
a11y-grid
Guides accessible data grid, interactive table, and sortable table implementation. Auto-invokes when creating data grids, spreadsheet interfaces, sortable tables, or interactive table cells. Critical distinction — most data tables do NOT need role="grid". Covers table vs grid decision, HTML table accessibility…
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…