The problem
Accessibility gets checked at the end, when fixes are expensive.
Audit reports say what failed but not how to fix it.
Automated tools give false confidence.
08
Is your service usable by everyone, equally? Find out before you ship.
Accessibility Analyst audits pages and designs against WCAG 2.2 AA, names the fix for every issue, ranks fixes by user impact, and tells you plainly what risk remains.
Or get all nine agents in the UCD Team bundle.
Accessibility gets checked at the end, when fixes are expensive.
Audit reports say what failed but not how to fix it.
Automated tools give false confidence.
Runs automated WCAG 2.2 AA checks on built pages
Reviews designs for contrast, focus order, labels and target size
Simulates a screen reader walk-through of your main journey
Lists the 2.2 criteria a person must still check
Ranks fixes by user impact and effort, with a plain-English risk summary
Get this on Gumroad and download the zip.
Unzip it into a project folder and open it in your AI tool.
Say `audit <URL, folder or design> for accessibility`.
It works one stage at a time and stops for your yes.
Audit scope
Automated audit, Design review, Screen reader walk-through (simulated), Manual checklist
Remediation ranking, Residual risk, Design annotations
WCAG 2.2 AA.
Every claim cites its source. Nothing is written to your tools without your approval.
Delivery managers, product owners and engineers who are not accessibility specialists but need audit-ready findings.
An AI tool that reads project instructions: Claude Code, Cursor, or a tool that reads AGENTS.md. Claude Projects and custom bots work too, with copy-and-paste outputs.
Your own AI subscription or API key. Nothing to host.
Optional connections: axe-core CLI, Playwright, Figma MCP, Miro MCP.
| File | What it does |
|---|---|
00-root-instructions.md | Who the agent is, the rules, the gates |
01-scope.md | Stage 1: Scope |
02-audit.md | Stage 2: Audit |
03-report.md | Stage 3: Report |
04-tools.md | Connections and permissions |
05-manifest.md | Which skill uses which tool |
06-adapters.md | How to load it in your tool |
LICENCE.md | What you may and may not do |
README.md | Start here: set-up in two minutes |
guardrails.md | Risks, controls and sign-off |
memory.md | What is kept and where |
adapters/AGENTS.md | Adapter for your AI tool |
adapters/CLAUDE.md | Adapter for your AI tool |
adapters/accessibility-analyst.mdc | Adapter for your AI tool |
adapters/chat-system-prompt.md | Adapter for your AI tool |
evals/eval-suite.md | Tests and pass marks |
samples/01-bad-form.html | Synthetic sample input |
samples/02-good-form.html | Synthetic sample input |
samples/03-design-brief.md | Synthetic sample input |
Designed before it was built
This agent was designed with the five-question method: purpose, boundaries, what it touches, when a person steps in, and how you know it works. [Read the design](./anatomy).
Designed by Vijay Kandhalu.