accessibility-audit

Audit digital products against WCAG 2.2 guidelines with severity ratings and remediation steps.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill accessibility-audit-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/accessibility-audit
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill accessibility-audit-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship interfaces with accessibility barriers that block users with disabilities, and they lack a structured way to find, classify, and fix these issues against WCAG standards. ## Core Features & Use Cases - WCAG 2.2 POUR Framework: Evaluates content against Perceivable, Operable, Understandable, and Robust principles including contrast, keyboard access, and ARIA usage. - Severity Classification: Rates every issue as Critical, Major, Minor, or Enhancement so teams can prioritize fixes by user impact. - Structured Issue Reports: Produces findings with description, location, WCAG criterion, severity, impact, remediation steps, and code examples. - Use Case: Before launching a new checkout flow, run an audit to catch missing form labels, insufficient color contrast, and keyboard traps, then hand developers a prioritized remediation list. ## Quick Start Audit this page's HTML for WCAG 2.2 accessibility issues and list each finding with its severity rating and remediation steps.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit a website for WCAG accessibility issues?

Evaluate the interface against the four WCAG 2.2 POUR principles: Perceivable, Operable, Understandable, and Robust. Document each issue with its location, WCAG criterion, severity rating, user impact, and concrete remediation steps with code examples.

What are the WCAG 2.2 POUR principles?

POUR stands for Perceivable, Operable, Understandable, and Robust. Perceivable covers text alternatives and contrast, Operable covers keyboard access and navigation, Understandable covers readability and input assistance, and Robust covers assistive technology compatibility.

How are accessibility issue severity levels classified?

Issues are rated on four levels: Critical blocks access entirely, Major causes significant difficulty, Minor is an inconvenience with workarounds, and Enhancement goes beyond compliance. Prioritize fixes by severity and user impact.

Does an accessibility audit require testing with real assistive technologies?

Yes, best practices include testing with real screen readers and other assistive technologies, and including users with disabilities when possible. Audits should also cover multiple devices, browsers, and both static and interactive states.

What are the limitations of a manual WCAG audit?

A manual audit depends on the auditor's coverage of pages, states, and interaction flows, so dynamic content and edge cases can be missed. It provides guidance and remediation steps but does not automatically apply fixes to the codebase.