wcag-compliance-checker_skill

This skill helps you verify WCAG 2.1 Level AA accessibility, identify violations, and generate remediation guidance for web projects.

TypeScript

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dexploarer/claudius-skills --skill wcag-compliance-checker

SKILL.md12.7 KB

Overview

This skill audits websites for WCAG 2.1 Level AA compliance, identifies accessibility violations, and delivers practical remediation guidance. It combines automated scans, manual checklists, and actionable fixes so teams can prioritize and resolve accessibility issues quickly.

How this skill works

The checker runs automated tools (axe-core, pa11y, Lighthouse) to surface programmatic violations and produces categorized results (critical, serious, moderate, minor). It pairs those results with manual testing guidance (keyboard, screen reader, visual checks) and code-level fixes for common issues like missing alt text, poor contrast, and form-labeling problems.

When to use it

Perform a pre-release accessibility audit on a public site or feature
Validate WCAG 2.1 Level AA compliance for legal or procurement requirements
Investigate reported accessibility violations or user feedback
Integrate accessibility checks into CI/CD or pull request workflows
Run screen reader and keyboard testing during manual QA

Best practices

Start with semantic HTML and add ARIA only when necessary
Run automated scans early and re-run after fixes
Combine automated results with manual keyboard and screen reader tests
Fix high-impact issues first: alt text, contrast, labels, keyboard traps
Integrate checks into CI/CD and document accessibility decisions

Example use cases

Generate a WCAG 2.1 Level AA compliance report for stakeholders with prioritized fixes
Add automated pa11y/axe checks to GitHub Actions to block regressions
Run a component-level jest-axe test suite during unit testing
Perform a manual checklist-driven audit before a major release
Train a dev team using real violations and code fixes from the scan

FAQ

It leverages axe-core for in-depth rules, pa11y for CI-friendly scans, and Lighthouse for an overall accessibility score.

Will automated scans catch everything?

No. Automated tools catch many issues but miss context-sensitive problems. Manual keyboard, screen reader, and visual tests are required to reach true compliance.