accessibility-auditlisted

# Accessibility Audit ## Core Rule Test against WCAG 2.1 AA criteria with concrete user-impact. Never auto-edit semantic HTML or ARIA without explicit user approval. ## When to Use Invoke with `/accessibility-audit` when: - Building or reviewing user-facing UI components - Preparing for an accessibility compliance review - Fixing reported accessibility issues - Ensuring inclusive design for all users - Before launching a new feature with UI changes ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for accessibility / WCAG compliance, produce the full accessibility-audit report automatically using the Process and Output Format sections below. Do not require the user to specify fields. Only modify files when the user explicitly requests implement / fix / apply / refactor. By default, this skill is **report-only**. ## Process ### Phase 1: Inventory (first-pass leads) This pass produces **candidates**, not findings. Treat counts as leads for deeper inspection in later phases. Do not report Phase 1 raw output as the final result. Determine the UI technology: - **Web**: React, Vue, Angular, Svelte, plain HTML - **Mobile**: React Native, Flutter, native iOS/Android - **Desktop**: Electron, Tauri, native desktop Adapt checks to the framework's accessibility patterns. ### Phase 2: Semantic Structure Check that UI elements convey meaning: **HTML Semantics (Web)** - Use semantic elements (`<nav>`, `<main>`, `<article>`, `<button>`) ins