a11y-playwright-testing

Automate WCAG 2.1 AA accessibility scans in Playwright tests with axe-core.

215|38|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fugazi/test-automation-skills-agents --skill a11y-playwright-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-playwright-testing
Source: https://github.com/fugazi/test-automation-skills-agents/tree/main/skills/a11y-playwright-testing
Command: npx skills add https://github.com/fugazi/test-automation-skills-agents --skill a11y-playwright-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility testing for modern web apps is time-consuming and error-prone; this skill automates a11y checks within Playwright tests using axe-core to catch regressions early.

Core Features & Use Cases

  • Automated WCAG 2.1 AA scans across pages and components using Playwright and axe-core.
  • Keyboard navigation, focus management, landmarks, ARIA validation, and screen reader compatibility checks.
  • Reusable patterns and references to standard a11y testing workflows for QA automation.

Quick Start

Start by running automated a11y scans over your Playwright tests to detect violations and generate reports.

Frequently Asked Questions about a11y-playwright-testing

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

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

Automate accessibility testing by integrating axe-core scans into your Playwright test suite to validate WCAG 2.1 AA compliance. This skill provides reusable patterns to run scans across pages and components, generating violation reports automatically during test execution.

What accessibility checks can I run using Playwright test automation?

Playwright test automation can validate keyboard navigation, focus management, landmarks, ARIA roles, and screen reader compatibility. It also checks color contrast to ensure your web application meets WCAG 2.1 AA standards across components.

Do I need TypeScript to run axe-core accessibility scans in Playwright?

Yes, TypeScript setup is required to use this skill. You also need @playwright/test and @axe-core/playwright installed in your project, along with an existing Playwright test configuration to execute the accessibility scans.

What is the best way to catch WCAG 2.1 AA regressions in web applications?

The best way to catch WCAG 2.1 AA regressions is to integrate automated a11y checks directly into your Playwright test pipeline. Running axe-core scans during continuous integration identifies accessibility violations early before deployment.

Can I generate accessibility violation reports for specific web page components?

Yes, you can generate accessibility violation reports for specific components. The skill applies axe-core scans to individual components or full pages within your Playwright tests to isolate and document accessibility issues.