a11y-tester

Run axe-core accessibility tests on web pages via Playwright MCP.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-tester
Source: https://github.com/joe-watkins/a11y-devkit/tree/main/packages/a11y-tester
Command: npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated accessibility testing by running axe-core against web pages or HTML content to identify WCAG 2.2 AA violations, reducing manual review time and improving conformance.

Core Features & Use Cases

  • Automated accessibility testing: run axe-core on URLs or HTML to detect violations.
  • Flexible output modes: raw violations for programmatic use, or formatted issues delegated to the a11y-issue-writer.
  • Trigger-based usage: activated by requests like "test accessibility", "check for WCAG violations", "audit this URL", "is this page accessible".
  • Integration ready: works with MCP Playwright servers to load pages and capture results.

Quick Start

Run an accessibility test on a URL or HTML content. Example: test accessibility on https://example.com.

Frequently Asked Questions about a11y-tester

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

FAQPage Schema
How do I automate accessibility testing for WCAG 2.2 AA conformance?

Automated accessibility testing for WCAG 2.2 AA conformance is achieved by running axe-core via Playwright against URLs or HTML content to identify violations. This skill automates the process, returning raw violations for programmatic use or formatted issue reports.

Can I use Playwright to check for WCAG violations on web pages?

Yes, you can use Playwright to check for WCAG violations. This skill integrates with an active Playwright MCP server to load web pages and execute axe-core, capturing accessibility results automatically.

What is the best way to run axe-core tests on HTML content?

The best way to run axe-core tests on HTML content is by triggering an automated accessibility audit. This skill processes URLs or raw HTML, detecting WCAG 2.2 AA violations and outputting raw data for programmatic use.

Does automated accessibility testing require an active MCP server?

Yes, automated accessibility testing with this skill requires an active MCP server. You must have a Playwright MCP setup configured to load pages and capture the axe-core test results.

How do I get formatted issue reports from axe-core violations?

To get formatted issue reports from axe-core violations, the skill can delegate output to the a11y-issue-writer. This provides structured reporting instead of raw programmatic violation data.