ARRM-based accessibility role audit — responsibility-based review lenses
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add zivtech/accessibility-skills --skill a11y-role-audit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of A11y Role Audit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/zivtech-a11y-role-audit)More formats (shields.io, HTML) on the badges page.
---
name: a11y-role-audit
description: "ARRM-based accessibility role audit — responsibility-based review lenses"
compatibility: Codex CLI mirror of .claude/skills/a11y-role-audit/SKILL.md
---
# Accessibility Role Audit (Codex Mirror)
Review a component, page, or design from the responsibility perspective of team roles derived from the W3C WAI ARRM framework.
## Roles
1. **Visual Design** — Contrast, zoom, focus indicators, target sizes, motion
2. **UX Design** — Interaction patterns, focus order, error flows, state communication
3. **Front-End Development** — Semantic HTML, ARIA, keyboard, live regions
4. **Content Authoring** — Alt text, headings, link text, captions, plain language
5. **Business Analysis** — CAPTCHA, time limits, requirements, metrics
6. **Testing** — AT validation, regression, coverage
## Usage
```
Review this component from the visual design role perspective:
[component code or description]
```
## Reference Files
- `roles/README.md` — overview and integration
- `roles/<role-name>.md` — per-role definition with checklist
- `roles/arrm-task-mapping.yaml` — WCAG SC → role mapping
## Output
Each role produces:
- Findings with severity, WCAG citation, evidence, and role ownership
- Blind spot escalations (areas needing other roles)
- Cross-role synthesis when multiple roles reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.
Use when the user wants to design a mobile app, create screens, build UI, or interact with their Sleek projects. Covers high-level requests ("design an app that does X") and specific ones ("list my projects", "create a new project", "screenshot that screen").
Creating and refining Mermaid diagrams with live reload. Use when users want flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, or any other Mermaid visualization. Provides best practices for syntax, styling, and the iterative workflow using mermaid_preview and mermaid_save tools.
SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.
Use when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback, or requesting user permissions. Apple Human Interface Guidelines for iOS compliance.
