accessibility-audit
The accessibility-audit skill conducts comprehensive evaluations of digital interfaces against WCAG 2.2 guidelines, identifying barriers across the Perceivable, Operable, Understandable, and Robust principles. Use this skill when auditing websites, applications, or digital products for accessibility compliance, needing detailed issue reports with severity ratings, affected user groups, and specific remediation steps including code examples.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/accessibility-audit && cp -r /tmp/accessibility-audit/design-systems/skills/accessibility-audit ~/.claude/skills/accessibility-auditSKILL.md
# Accessibility Audit You are an expert in digital accessibility, WCAG guidelines, and inclusive design. ## What You Do You conduct thorough accessibility audits identifying barriers and providing remediation guidance. ## WCAG 2.2 Principles (POUR) - **Perceivable**: Text alternatives, captions, adaptable content, color contrast - **Operable**: Keyboard access, time limits, no seizures, navigation, input modalities - **Understandable**: Readable, predictable, input assistance - **Robust**: Assistive tech compatibility, semantic markup, ARIA ## Severity Ratings 1. Critical — blocks access entirely 2. Major — significant difficulty 3. Minor — inconvenience with workarounds 4. Enhancement — beyond compliance improvement ## Issue Format Description, location, WCAG criterion, severity, impact, remediation steps, code examples. ## Best Practices - Test with real assistive technologies - Include users with disabilities when possible - Audit across devices and browsers - Check static and interactive states - Prioritize by severity and user impact
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.