auditing-accessibility-wcag

Detects WCAG 2.1 accessibility violations in UI components and pages.

6|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/WesleySmits/agent-skills --skill auditing-accessibility-wcag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditing-accessibility-wcag
Source: https://github.com/WesleySmits/agent-skills/tree/main/.agent/skills/accessibility-auditor
Command: npx skills add https://github.com/WesleySmits/agent-skills --skill auditing-accessibility-wcag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies WCAG 2.1 accessibility violations in UI components and pages to help teams comply with accessibility standards.

Core Features & Use Cases

  • Automated audits using axe-core and Lighthouse
  • Violation categorization and remediation examples
  • Useful for audits on components, pages, or entire sites

Quick Start

Provide a URL or component and run automated accessibility checks to generate a remediation-ready report.

Frequently Asked Questions about auditing-accessibility-wcag

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

FAQPage Schema
How do I audit my web components for WCAG 2.1 accessibility violations?

To audit web components for WCAG 2.1 accessibility violations, provide a URL or component to run automated checks using axe-core and Lighthouse. This generates a report detailing violations, severity categorization, example fixes, and remediation guidance for compliant interfaces.

Can I run automated accessibility checks on a full website or just individual pages?

Automated accessibility checks can be run on individual UI components, specific pages, or full websites. The audit identifies WCAG 2.1 violations across your specified scope and outputs categorized remediation examples and guidance.

What is the best way to generate remediation guidance for Lighthouse and axe-core accessibility issues?

The best way to generate remediation guidance for axe-core and Lighthouse accessibility issues is to run an automated audit on your UI components. This categorizes violations by severity and provides targeted example fixes to ensure compliant interfaces.

Does this accessibility audit provide specific code fixes for WCAG 2.1 failures?

Yes, the accessibility audit provides specific code fixes for WCAG 2.1 failures. It outputs categorized violations alongside example fixes and remediation guidance to help developers correct identified accessibility issues efficiently.

How does automated WCAG 2.1 auditing work for UI testing?

Automated WCAG 2.1 auditing for UI testing works by scanning provided components or URLs using axe-core and Lighthouse checks. It identifies accessibility violations and outputs a remediation-ready report with severity categorization and example fixes.

What do I need to start an accessibility review using axe-core and Lighthouse?

To start an accessibility review using axe-core and Lighthouse, you need to provide a URL or UI component for scanning. The audit processes the input to identify violations and generates a remediation-ready report with severity levels and fix examples.