accessibility-audit
owl-listener/designer-skills
Audit interfaces against WCAG 2.2 with severity ratings and remediation steps.
What is accessibility-audit?
Conducts thorough accessibility audits of existing designs and builds, identifying barriers against WCAG 2.2 principles and providing concrete remediation guidance. Use this when you have a live interface to assess now; for planning future assistive-technology testing sessions, use accessibility-test-plan instead.
- Identifies accessibility barriers across Perceivable, Operable, Understandable, and Robust (POUR) principles
- Rates issues by severity: Critical, Major, Minor, and Enhancement
- Provides remediation steps and code examples for each finding
- Checks static and interactive states across devices and browsers
- Includes impact assessment and WCAG criterion mapping for each issue
How to install accessibility-audit
npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-auditHow to use accessibility-audit
- 1.Provide the interface, design file, or live URL to audit
- 2.Specify the scope: full page, component, user flow, or specific features
- 3.Receive a structured report with findings organized by severity
- 4.Review remediation steps and code examples for each issue
- 5.Prioritize fixes based on severity ratings and user impact
Use cases
- Audit a completed web application or design before launch to catch accessibility gaps
- Review a redesigned component or page section against WCAG compliance
- Assess keyboard navigation, screen reader compatibility, and color contrast in an existing interface
- Evaluate form inputs, time limits, and interactive elements for accessibility barriers
- Prioritize remediation work by severity and user impact across a product
- Designers and developers conducting compliance reviews
- Product teams preparing for accessibility certification or audit
- Accessibility specialists evaluating existing interfaces
- Teams integrating accessibility into QA workflows
accessibility-audit FAQ
accessibility-audit evaluates an existing interface against WCAG now, producing findings and fixes. accessibility-test-plan helps plan future testing sessions with assistive-technology users for prototyping and validation.
This skill identifies barriers and best practices; for comprehensive validation, pair findings with testing using actual screen readers, voice control, and keyboard-only navigation across real devices.
This skill audits against WCAG 2.2, covering Perceivable, Operable, Understandable, and Robust principles.
Yes. Specify the scope—full page, component, user flow, or specific features—and the audit will focus on that area.
Each issue includes description, location, WCAG criterion, severity rating, impact, remediation steps, and code examples where applicable.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: accessibility-audit
description: 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).
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
- Critical — blocks access entirely
- Major — significant difficulty
- Minor — inconvenience with workarounds
- 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
Related skills
More from owl-listener/designer-skills and the wider catalog.
accessibility-test-plan
Plan comprehensive accessibility testing with assistive technologies, WCAG criteria, and real user participation.
aesthetic-usability
Apply the Aesthetic-Usability Effect to build trust through visual consistency and polish.
affinity-diagram
Cluster qualitative research data into themed insights across multiple interviews and sources.
animation-principles
Apply animation principles—easing, staging, follow-through—to tune how a single UI motion feels.
card-sort-analysis
Analyze card sort results into proposed groupings and labels for information architecture.
case-study
Craft compelling portfolio case studies with narrative arc, process evidence, and measurable outcomes.