Accessibility Audit
Run a structured WCAG-oriented accessibility audit with severity tiers, criterion mapping, and actionable remediation for shipping inclusive UI.
Overview
accessibility-audit is an agent skill most often used in Ship (also Build frontend, Launch geo/SEO surfaces) that conducts WCAG-guided audits with severity ratings and remediation steps.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-auditWhat is this skill?
- WCAG 2.2 POUR coverage: Perceivable, Operable, Understandable, Robust
- Four severity ratings from Critical (blocks access) through Enhancement
- Structured issue format: location, criterion, severity, impact, remediation, code examples
- Guidance to test assistive tech, multi-device states, and static vs interactive UI
- Prioritization by severity and real user impact
- WCAG 2.2 POUR four principles
- Four severity levels: Critical, Major, Minor, Enhancement
Adoption & trust: 572 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship UI but lack a consistent way to find WCAG barriers, rank severity, and hand engineers fix-ready guidance.
Who is it for?
Indie SaaS, marketing sites, and extensions needing a structured a11y pass before launch or after major UI changes.
Skip if: Formal VPAT or legal compliance certification without human experts, or backend-only changes with no user-facing UI.
When should I use this skill?
You need a comprehensive accessibility audit against WCAG with severity ratings and remediation steps for UI you plan to ship or recently changed.
What do I get? / Deliverables
You receive a prioritized audit with criterion-linked issues, impact notes, remediation steps, and code examples ready for implementation tickets.
- Prioritized issue list with WCAG criterion references
- Remediation steps and code examples per finding
- Severity-ranked backlog suitable for engineering tickets
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because audits gate release quality, though the same checklist applies while building screens and before launch compliance checks. Review subphase matches pre-release evaluation of UX barriers, contrast, keyboard paths, and semantic markup—not net-new feature coding.
Where it fits
Audit a new checkout flow for focus order and form labels before merging the PR.
Produce a Critical-to-Enhancement report blocking release until contrast and keyboard traps are fixed.
Review marketing landing pages for readable structure and alternatives that help humans and AI summaries alike.
How it compares
Human-style WCAG audit checklist—not a substitute for axe-only CI gates or generic code review without inclusive design criteria.
Common Questions / FAQ
Who is accessibility-audit for?
Solo builders and designers shipping web or mobile UI who want WCAG-aligned findings with severity and remediation without running ad-hoc prompts.
When should I use accessibility-audit?
In Ship (review) before release; during Build (frontend) on new flows; at Launch when public pages need inclusive, crawlable, usable experiences—especially after redesigns or keyboard/contrast complaints.
Is accessibility-audit safe to install?
It guides review of your UI artifacts; review the Security Audits panel on this Prism page and avoid pasting production secrets into audit threads.
SKILL.md
READMESKILL.md - Accessibility Audit
# 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