accessibility-testing

Automate accessibility testing with axe-core and Playwright for WCAG conformance.

64|12|Updated Mar 23, 2026

Search Tags:#accessibility #a11y #playwright #screen-reader #axe-core #keyboard-navigation #wcag-2-2

Ready to run

npx skills add https://github.com/petrkindlmann/qa-skills --skill accessibility-testing-petrkindlmann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/accessibility-testing
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill accessibility-testing-petrkindlmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and verify accessibility issues across web applications by combining automated axe-core scans with manual testing strategies to ensure WCAG compliance and inclusive experiences.

Core Features & Use Cases

Automated accessibility testing with axe-core integrated into Playwright end-to-end tests.
Keyboard navigation and screen reader evaluation to catch issues automated tests miss.
WCAG conformance checks and ARIA pattern validation for complex components.

Quick Start

Install axe-core for Playwright integration and run your end-to-end accessibility tests as part of your CI pipeline.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema

How do I automate accessibility testing with axe-core and Playwright?▼

Automate accessibility testing by integrating axe-core scans directly into Playwright end-to-end tests. This setup validates WCAG conformance and catches issues during CI pipeline execution or manual test cycles.

Can automated accessibility tests catch keyboard navigation and screen reader issues?▼

Automated axe-core scans alone do not fully cover keyboard navigation and screen reader behavior. This approach combines automated checks with manual testing strategies to evaluate keyboard navigation and screen reader interactions.

What is the best way to check WCAG 2.2 conformance in a CI pipeline?▼

Checking WCAG 2.2 conformance in a CI pipeline involves running automated axe-core scans integrated with Playwright end-to-end tests. This provides continuous validation of ARIA patterns and accessibility rules.

Do I need Playwright setup to run axe-core accessibility checks?▼

Yes, Playwright setup is required to execute these automated accessibility checks. You also need axe-core bindings and optional screen-reader validation coverage to perform thorough end-to-end audits.

How does ARIA pattern validation work for complex web components?▼

ARIA pattern validation works by running automated axe-core checks within Playwright tests to verify WCAG conformance. Manual test cycles are then used to evaluate keyboard and screen reader interactions for complex components.