accessibility-audit

Audits digital products against WCAG 2.1/2.2 and produces violation inventories and remediation roadmaps.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill accessibility-audit-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/accessibility-audit
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill accessibility-audit-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams shipping web products often lack a structured way to assess WCAG 2.1/2.2 conformance, combine automated and manual accessibility testing, and turn findings into a prioritized remediation plan. ## Core Features & Use Cases - WCAG Conformance Assessment: Evaluates products against the four POUR principles (Perceivable, Operable, Understandable, Robust) at A, AA, or AAA target levels. - Violation Inventory & Remediation Roadmap: Classifies findings by severity and user impact, then prioritizes quick wins, medium-term fixes, and structural changes. - A11y Testing Strategy: Combines automated tools (axe-core, Lighthouse, WAVE) with manual keyboard and screen reader testing (NVDA, VoiceOver, JAWS). - Use Case: Ask it to audit an ecommerce checkout against WCAG 2.2 AA and receive a scorecard, violation table with WCAG criterion references, and a prioritized remediation roadmap. ## Quick Start Ask the assistant to audit your checkout flow against WCAG 2.2 AA, covering keyboard navigation, screen reader behavior, focus order, and color contrast.

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 2.2 compliance?▼

Define the scope and target conformance level, run automated tools like axe-core, Lighthouse, or WAVE, then perform manual keyboard and screen reader testing. Findings are classified by severity and compiled into a scorecard and prioritized remediation roadmap.

What accessibility testing tools does a WCAG audit use?▼

The audit combines automated tools (axe-core, Lighthouse, WAVE) with manual testing using screen readers such as NVDA, VoiceOver, or JAWS, plus keyboard-only navigation and zoom testing. Automated tools alone detect only about 30-40% of issues.

Can automated tools alone certify WCAG compliance?▼

No. Automated tools detect only roughly 30-40% of accessibility issues, so manual testing with assistive technologies is essential. Declaring conformance from automated scans alone is explicitly rejected by this audit approach.

Should I target WCAG AA or AAA conformance?▼

AA is the standard legal and regulatory target for most products. AAA is aspirational and generally not achievable across an entire product, so audits frame AA as the default goal and treat AAA claims with caution.

How are accessibility violations prioritized for remediation?▼

Violations are rated by severity and user impact, then ranked by critical user impact first, followed by legal exposure and effort-to-impact ratio. The roadmap separates quick wins like CSS and ARIA fixes from structural architecture changes.