Repository navigation
Documentation
One package of Agent Skills, read natively by Claude Code, Codex, GitHub Copilot, Gemini CLI and Antigravity. This index is the front door; every page below is reachable from here, and every section says what kind of page it holds so you can skip what you do not need.
Four places to begin, matched to what you are trying to do.
| If you want to | Read |
|---|---|
| Install it and run a first audit | Getting started |
| Understand what the six entry points do | Skills reference |
| See what it conforms to and what proves it | Conformance |
| Know how it fits together and why | Architecture |
Getting started - install on each client, run a first audit, apply a first fix, and what to expect from the enforcement gate.
Guides - one task per page: troubleshooting, browser tools, scanning workflows, custom skills, context management, authoritative sources.
Reference - the facts, generated where they can be:
-
Skills catalog, every skill by tier and domain,
built from frontmatter by
scripts/build-docs.mjs - Per-skill pages, when to use each, what it catches, how to launch it
- Knowledge domains, the reference-tier skills and which reviewers cite them
- MCP tools, all 39 with their annotations
- Hooks, the enforcement gate and its client manifests
- Configuration, scan config files, workspace preferences, budgets, settings
- Tools, Playwright, veraPDF, the PDF form converter
Standards - one page per standard this package conforms to, each with the version relied on, the clauses that matter, how conformance is checked, and any deviation stated plainly:
- Agent Skills
- AGENTS.md
- Agent Plugins 1.0
- Model Context Protocol
- WCAG 2.2
- Hooks, by client
- Conformance dossier, the gates and the measured results
- Citation policy and research sources
Architecture - the tier model, the dispatch contract, the findings pipeline, and the decisions behind them.
Accessibility of this project - how Accessibility Agents tests and tracks its own accessibility, apart from what it does for yours:
- Testing the core flows, the keyboard, screen reader, manual and documentation checks and every run
- Progress updates, monthly
- Open Source Accessibility Framework record, action by action with evidence
- Resources other projects can reuse
Releases - release notes, one file per version.
History - the records of how 7.0 and 7.1 came to be. Older plans, audits, prompt files and superseded guides were removed after 7.1; they remain in the git history.
The records kept, and what each holds:
- The 7.0 modernization, what changed and why
- The 7.1 standards audit, how it was checked, what was decided, where to go next
- The first real audit, what nine specialists found against a fixture with a known answer key, and the merge defect that only a real run could expose
- The conformance audit of September 2026, the pre-7.0 audit the modernization answered
- The legacy drift report, the lines that differed between the six per-client copies at migration time
-
history/context-*.json, the context-cost measurements before, during and after the migration, cited by the conformance dossier
No emoji, no decorative Unicode, plain ASCII punctuation, a sentence before
every table. This is an accessibility project and its documentation is read
aloud. npm run verify:markdown holds the line.
node scripts/build-docs.mjs # skills catalog and MCP tools reference
node scripts/build-dispatch-matrices.mjsBoth have a --check mode that CI runs, so a generated page cannot drift from
the source it describes.
- Agents Overview
- Accessibility Lead
- Web Accessibility Wizard
- Document Accessibility Wizard
- Markdown Assistant
- Developer Hub
- GitHub Hub