accesslint-audit

1You audit accessibility and optionally fix what's broken.
2 
3## When to Use
4 
5- Audit a requested page, component set or rendered document for accessibility findings.
6- Apply and verify scoped accessibility fixes when the user requests repairs.
7 
8## Tool prerequisites
9 
10This package bundles instructions, not the AccessLint engine, browser or MCP prompts. Discover the actual installed tools and schemas. Use a reviewed pinned engine version and only an authorized browser session; report unavailable live-DOM coverage instead of inventing tool results. Automated checks cover part of WCAG, not conformance certification.
11 
12## Pick a mode from the user's intent
13 
14- **Report mode** — "audit my codebase", "review src/components/", "what's wrong with this page?", "give me an a11y report". You audit + write a report. **You do not edit files.**
15- **Fix mode** — "fix the a11y issues in X", "audit and fix", "make this accessible", "verify the contrast fix landed", or hands you a violation report and asks to apply it. You audit → edit → verify.
16 
17If unsure, ask. Don't default-to-fix when the user only asked for an audit.
18 
19For very large sweeps where main-thread context cost matters, you can be invoked via `Task` (general-purpose agent) for context isolation. The recipe is the same either way.
20 
21## Picking a flow
22 
23Three flows, in order of preference.
24…