skills.rest
matteocervelli
matteocervelliCOMMUNITY
Explore all skills by this author →
Website𝕏@matteocervelliGitHub

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

25|2|Updated Oct 26, 2025
Search Tags:#accessibility#a11y#WCAG#Playwright#axe-core
One-click install
npx skills add https://github.com/matteocervelli/llms --skill accessibility-checker-matteocervelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/matteocervelli/llms/tree/main/.claude/skills/accessibility-checker
Command: npx skills add https://github.com/matteocervelli/llms --skill accessibility-checker-matteocervelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates WCAG 2.1 AA compliance and accessibility best practices across UI components.

Core Features & Use Cases

  • Automated WCAG Checks: Automated validations with Playwright/axe-core.
  • Manual Verification Guidance: Checklists and manual test steps.
  • Remediation Templates: Practical fixes for common accessibility issues.

Quick Start

Run automated accessibility checks and review the results for remediation.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I check if my website meets WCAG 2.1 AA accessibility standards?▼

WCAG 2.1 AA compliance validates that web content is accessible to users with disabilities. Use automated scanning with Playwright and axe-core to identify violations like missing alt text, color contrast failures, and keyboard navigation issues across your pages, then review results for remediation.

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

Yes. Automated accessibility testing with Playwright and axe-core scans web pages for WCAG violations, runs per-page and batch checks, and produces violation reports. This approach detects structural and style-based accessibility issues without manual inspection of every component.

What accessibility checks does automated scanning catch?▼

Automated scanning detects alt text omissions, color contrast violations, keyboard navigation barriers, missing ARIA labels, and other WCAG 2.1 AA failures. Manual verification guidance complements automated results to catch issues requiring human assessment.

When should I run accessibility audits during development?▼

Run accessibility checks during regression testing and pre-release validation to catch violations before production. Per-page and batch scans fit into CI/CD pipelines or manual audit workflows to validate UI components meet WCAG 2.1 AA conformance continuously.

Do I need manual verification after automated accessibility scans?▼

Automated scans identify many WCAG violations but miss context-dependent issues. Manual verification checklists and remediation templates complement automated results to ensure full accessibility compliance and provide actionable fix guidance.

What output do accessibility compliance reports include?▼

Reports list identified WCAG violations with severity, affected elements, and remediation guidance. Deliverable outputs support accessibility audits and stakeholder communication by documenting violations, compliance status, and corrective actions needed.

Related Skills

Explore More Design & Creative Skills→
xxihxxih
1

e2e-testing

Execute Playwright web app tests and generate HTML reports with CI/CD compatibility.

Community
Advanced
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate
emiljuchnikowskiemiljuchnikowski

a11y-audit

Integrate Playwright with axe-core to audit web pages for WCAG 2.1 AA violations.

Community
Intermediate
4lerman4lerman

a11y-audit

Scan web application code for WCAG 2.2 violations and suggest fixes.

Community
Advanced