accessibility-audit

Audits websites against WCAG 2.1 AA and produces a prioritized remediation plan.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill accessibility-audit-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/accessibility-audit
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill accessibility-audit-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Accessibility issues are easy to miss and hard to verify: automated scanners catch only 30 to 50 percent of problems, and teams often ship products that fail keyboard, screen reader, or contrast requirements without knowing it. This Skill runs a structured, five-stage WCAG audit and turns findings into a prioritized remediation plan. ## Core Features & Use Cases - Five-stage audit methodology: Combines automated scanning (axe, Lighthouse, WAVE, Pa11y), manual keyboard testing, screen reader testing, visual checks (contrast, zoom, reflow), and cognitive accessibility review. - WCAG 2.1 AA scoring: Maps every finding to specific success criteria across the four principles (Perceivable, Operable, Understandable, Robust) with P0-P3 severity classification. - Report and remediation outputs: Ships a fillable audit report template, a WCAG quick-reference checklist, and a decision-grade ARIA patterns guide covering modals, tabs, live regions, and labeling. - Use Case: Before launching a marketing site, run the audit across key user flows to catch a modal without focus management (P0), low-contrast body text (P1), and missing form labels, then hand engineering a sequenced fix roadmap. ## Quick Start Audit the checkout flow of my site for WCAG 2.1 AA compliance and produce a prioritized remediation report.

Frequently Asked Questions about accessibility-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a WCAG accessibility audit on my website?

Run a WCAG audit in five stages: automated scanning with axe DevTools or Lighthouse, manual keyboard-only navigation of key flows, screen reader testing with NVDA or VoiceOver, visual checks for contrast and 200% zoom, and cognitive review. Score each finding against WCAG 2.1 AA criteria and prioritize by severity.

What tools are used for automated accessibility testing?

The audit uses axe DevTools, Lighthouse accessibility audit, WAVE, and Pa11y for CLI batch scanning. Automated tools catch only 30 to 50 percent of issues, so they must be combined with keyboard, screen reader, and visual testing.

Can automated scanners alone verify WCAG compliance?

No. Automated scanners catch only 30 to 50 percent of accessibility issues. The remaining issues surface in keyboard navigation, screen reader behavior, focus management, and cognitive testing, which require manual verification.

What is the difference between WCAG AA and AAA conformance?

WCAG AA is the practical baseline for most products, requiring 4.5:1 text contrast and full keyboard operability. AAA adds stricter targets like 7:1 contrast and is rarely the right goal; the audit anchors to AA with AAA noted where relevant.

Why do modals fail accessibility audits so often?

Modals commonly fail because focus is not moved into the dialog on open, Tab escapes into background content, or focus is not returned to the trigger on close. The fix requires role="dialog", aria-modal="true", focus trapping, and Escape-to-close behavior.

When should I not use a full accessibility audit?

Skip the full audit for routine post-deploy QA, component-level accessibility implementation, or design-token contrast checks. Those cases are better served by lighter QA testing or component build workflows rather than a site-wide WCAG assessment.