accessibility-checker

Audit web UI against WCAG 2.1 AA using axe-core via Playwright.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill accessibility-checker-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/accessibility-checker
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill accessibility-checker-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures web UI accessibility by automatically auditing against WCAG 2.1 AA standards with axe-core integrated into Playwright, catching violations early in the development process.

Core Features & Use Cases

  • Automated WCAG 2.1 AA audits across pages and components using axe-core.
  • Severity-based reporting with actionable remediation guidance and selectors for each violation.
  • Blocking policy for critical or serious issues to gate feature completion and maintain accessibility standards.

Quick Start

Run automated WCAG 2.1 AA audits on your UI using axe-core via Playwright to identify accessibility issues.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I automate WCAG 2.1 AA audits for web UI using Playwright?

Automate WCAG 2.1 AA audits by running axe-core via Playwright to scan pages and components, identifying color contrast failures, keyboard navigation gaps, ARIA mistakes, and missing alt text. You receive a structured violation report with element selectors, severity levels, and remediation guidance.

What is the best way to catch ARIA mistakes and color contrast failures during development?

Run axe-core audits integrated with Playwright during design, development, and review phases to catch ARIA mistakes and color contrast failures early. This automated WCAG 2.1 AA auditing delivers actionable remediation guidance with specific element selectors for each violation found.

Can I block feature completion on critical accessibility violations?

Yes, you can gate feature completion using a blocking policy for critical or serious WCAG 2.1 AA violations. The audit identifies severe accessibility issues with axe-core via Playwright, preventing progression until standards are met.

Does axe-core integrated with Playwright detect keyboard navigation gaps and missing alt text?

Yes, axe-core integrated with Playwright detects keyboard navigation gaps and missing alt text by auditing against WCAG 2.1 AA standards. It catches these accessibility issues across pages and components, delivering a structured violation report with remediation guidance.

How does automated accessibility auditing identify which elements violate WCAG rules?

Automated accessibility auditing identifies violating elements by evaluating the UI against WCAG 2.1 AA rules using axe-core. It generates a structured violation report containing specific element selectors, the violated rules, severity, and actionable remediation guidance.

When should I run axe-core accessibility audits in my development workflow?

Run axe-core accessibility audits during the design, development, and review stages to catch violations early. Integrating these checks via Playwright throughout the workflow ensures color contrast, keyboard navigation, and ARIA standards are continuously validated.