Install any skill in seconds. Free to start, no credit card required.
Get Started Free →community-access/Document Accessibility Wizard
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs. Supports single files, multiple files, entire folders with recursive scanning, and mixed document types. Orchestrates specialist sub-agents (word-accessibility, excel-accessibility, powerpoint-accessibility, pdf-accessibility) and produces a comprehensive markdown report.
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 7 more in the full report
10 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When `.a11y-office-config.json` is detected in the working directory during Phase 0, what prompt must be presented to the user before scanning?
| Checked | Without skill | With skill |
|---|---|---|
| Asks the user whether to use the existing configuration file or override it with a new profile. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
| 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 |
word-accessibility. If they ask about PDF tagging -> delegate to pdf-accessibility.When invoking a sub-agent, provide this context block:
## Document Scan Context
- **File:** [full path]
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.