qa-a11y-compliance

Scan web applications for WCAG 2.2 AA accessibility compliance.

Updated May 28, 2026

Search Tags:#accessibility #a11y #QA #web accessibility #WCAG 2.2

Ready to run

npx skills add https://github.com/SensLiao/Claude-code-setting --skill qa-a11y-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-a11y-compliance
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/qa-a11y-compliance
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill qa-a11y-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe-core, pa11y, puppeteer, playwright, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive solution for assessing and ensuring accessibility compliance for web applications, focusing on WCAG 2.2 AA standards.

Core Features & Use Cases

Automated Accessibility Scan: Utilizes tools like axe-core and pa11y to automatically scan web content for accessibility issues.
Manual Checks: Offers guidelines for manual checks such as keyboard navigation, focus order, and color contrast.
Integration with CI: Can be integrated into continuous integration pipelines for automated testing.
Detailed Reporting: Generates detailed reports on compliance status, including automated scan results and manual checks.

Quick Start

Run the qa-a11y-compliance skill to perform an accessibility scan on your web application.

Frequently Asked Questions about qa-a11y-compliance

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

FAQPage Schema

How do I automate web accessibility testing against WCAG 2.2 AA standards?▼

Automate web accessibility testing against WCAG 2.2 AA standards by running scans with axe-core and pa11y to detect issues, alongside manual checks for keyboard navigation, focus order, and color contrast.

Can I integrate pa11y and axe-core accessibility scans into my CI pipeline?▼

Yes, you can integrate accessibility scans into your CI pipeline to automate testing. This setup runs automated scans using axe-core and pa11y during continuous integration to generate detailed compliance reports.

What is the difference between automated accessibility scans and manual WCAG checks?▼

Automated accessibility scans use tools like axe-core to detect code-level issues, while manual WCAG checks verify interactive behaviors like keyboard navigation and focus order that automated tools cannot fully assess.

Does automated accessibility testing with axe-core catch all WCAG 2.2 violations?▼

No, automated accessibility testing with axe-core does not catch all WCAG 2.2 violations. It must be combined with manual checks for keyboard navigation, focus order, and color contrast to ensure full compliance.

How do I generate detailed reports for web accessibility compliance status?▼

Generate detailed reports for web accessibility compliance by running automated scans and manual checks. The process aggregates results from axe-core and pa11y to document compliance status against WCAG 2.2 AA requirements.

Do I need Puppeteer or Playwright to run automated web accessibility scans?▼

You need Puppeteer or Playwright to run automated web accessibility scans because they control headless browsers for testing. These dependencies enable axe-core and pa11y to evaluate dynamic web content.