Accessibility Audit

owl-listener/designer-skills/design-systems/skills/accessibility-audit

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Instructions onlySecurity
AI-generated overview

Audits an existing interface against WCAG 2.2, producing severity-rated findings with remediation steps.

What it does
Guides an accessibility audit of an existing design or build against the WCAG 2.2 POUR principles: perceivable, operable, understandable and robust. It reports issues in a fixed format covering description, location, WCAG criterion, severity, impact, remediation steps and code examples. Findings are rated critical, major, minor or enhancement and prioritized by severity and user impact.
When to use it
Use it when you already have a design or build to assess and need documented accessibility findings. It is not intended for planning future sessions with assistive-technology users, which the document assigns to a separate test-planning skill.
Requirements
No scripts or tools are required; it is an instructions-only skill. The document recommends testing with real assistive technologies and across devices and browsers.

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

Source and attribution

Source:owl-listener/designer-skillsindesign-systems/skills/accessibility-auditat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal