accessibility_testing

Audit codebases and live URLs for WCAG compliance issues and accessibility barriers.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill accessibility-testing-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility_testing
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/accessibility_testing
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill accessibility-testing-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It identifies WCAG compliance violations and inclusive design barriers in codebases or live websites, producing structured audit reports that developers can act on directly. ## Core Features & Use Cases - Comprehensive WCAG Audits: Evaluates semantic HTML, ARIA implementation, keyboard navigation, color contrast, forms, alt text, and touch targets against WCAG 2.1/2.2 Levels A, AA, and AAA. - Visual Testing with Playwright MCP: Navigates live URLs, captures accessibility tree snapshots, tests keyboard flows, and measures rendered contrast with screenshot evidence. - Standardized Reports: Generates severity-ranked findings (A-001 format) with exact code locations, WCAG criterion references, and remediation code examples saved to /docs/accessibility/. - Use Case: Before a compliance certification, run an audit on your React app to find missing form labels, insufficient contrast ratios, and keyboard traps, then receive a prioritized remediation roadmap. ## Quick Start Audit this codebase for WCAG 2.2 Level AA compliance and generate a full accessibility report with remediation guidance.

Frequently Asked Questions about accessibility_testing

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

FAQPage Schema
How do I audit a website for WCAG compliance?

Provide a target URL or codebase along with the WCAG version (2.1 or 2.2) and conformance level (A, AA, or AAA). The audit analyzes document structure, ARIA, keyboard flow, contrast, and forms, then generates a severity-ranked report with remediation code.

How to test keyboard navigation accessibility on a live site?

With Playwright MCP tools available, the audit navigates to the URL, presses Tab through interactive elements, captures focus-state screenshots, and checks for keyboard traps and visible focus indicators with 3:1 contrast.

What contrast ratio is required for WCAG Level AA?

WCAG Level AA requires 4.5:1 contrast for normal text, 3:1 for large text (18pt+ or 14pt+ bold), and 3:1 for UI components and focus indicators. Level AAA raises these to 7:1 and 4.5:1 respectively.

Can automated accessibility testing replace screen reader testing?

No. Automated and Playwright-based testing cannot replace manual screen reader verification, and may miss semantic issues affecting assistive technology users, voice control, and some dynamic behaviors.

What does the accessibility audit report include?

The report includes an executive summary, an at-a-glance severity breakdown, a compliance score, findings numbered A-001 and up with exact code locations and WCAG criteria, remediation code examples, and a prioritized fix roadmap saved under /docs/accessibility/.