a11y-role-auditlisted

# Accessibility Role Audit Review a component, page, or design from the responsibility perspective of specific team roles. Each role brings a distinct vantage point with explicit blind spots — what it CAN see and what it CANNOT. Running multiple roles catches barriers that no single role would find alone. ## Relationship to Other Skills | Skill | Dimension | Question | |-------|-----------|----------| | `a11y-critic` | Design decisions | "Is the accessibility approach sound?" | | `perspective-audit` | Access methods | "Who is blocked?" (users with disabilities) | | `a11y-role-audit` (this) | Team responsibilities | "Who on the team owns preventing/fixing this?" | These three are complementary layers: 1. Critic identifies design gaps 2. Perspective audit identifies impact on specific user groups 3. Role audit identifies which team member is responsible and what each sees from their vantage point ## When to Use ### Mode 1: Design Review (before code) Run visual-design + ux-design lenses over mockups, wireframes, or design specs. Catches accessibility barriers before implementation hardens them. ``` /a11y-role-audit design <target> [--roles visual-design,ux-design] ``` ### Mode 2: Implementation Review (after code) Run all roles (or a subset) over implemented code. Each lens reviews from its domain-specific vantage point. ``` /a11y-role-audit code <target> [--roles all] /a11y-role-audit code <target> [--roles front-end-development,content-authoring] ``` ### Mode 3: F