hatch3r-a11y-audit

# Accessibility Audit Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Read accessibility requirements from rules and specs - [ ] Step 2: Automated scan — run axe-core or similar on all pages/components - [ ] Step 3: Manual audit — load references/manual-audit-checklist.md - [ ] Step 4: Catalog findings by severity (critical/major/minor) - [ ] Step 5: Fix critical and major findings - [ ] Step 6: Verify fixes with re-scan and manual check ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: WCAG conformance target (A vs AA vs AAA), scope (single component vs full app), surfaces to audit (which routes), fix authority (audit-only vs audit-and-fix), and screen-reader pass scope (per release vs per audit). ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P8 B2; `agents/shared/efficiency-patterns.md`). Emit `sub_agents_spawned: { count, rationale, task_structure }` in your output. ## Relationship to the verification gates This skill is the accessibility audit-and-fix WORKFLOW — enumerat...