skills.rest
TarasTsavolyk
TarasTsavolykCOMMUNITY
Explore all skills by this author →
GitHub

a11y-audit

Audit web UI components against WCAG 2.2 AA standards using axe and manual checks.

1|Updated Jun 4, 2026
Search Tags:#accessibility#a11y#WCAG#audit#UI components
One-click install
npx skills add https://github.com/TarasTsavolyk/claude-code-frontend --skill a11y-audit-tarastsavolyk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/TarasTsavolyk/claude-code-frontend/tree/main/.claude/skills/a11y-audit
Command: npx skills add https://github.com/TarasTsavolyk/claude-code-frontend --skill a11y-audit-tarastsavolyk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the accessibility audit process for web UI components, ensuring they meet WCAG 2.2 AA standards, and helps identify potential barriers for users with disabilities.

Core Features & Use Cases

  • Automated Accessibility Audit: Checks UI components against WCAG 2.2 AA standards.
  • Automated and Manual Checks: Combines automated testing with manual verification for comprehensive results.
  • Use Case: Before merging UI changes or as part of a continuous integration process, this Skill can be used to verify that all components meet accessibility requirements.

Quick Start

Run the a11y-audit skill on your component to ensure compliance with accessibility standards.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema
How do I audit UI components for WCAG 2.2 AA compliance?▼

You can audit UI components for WCAG 2.2 AA compliance by running automated axe checks alongside manual verification against a predefined checklist to identify accessibility barriers.

Can I integrate accessibility checks into a front-end development pipeline?▼

Yes, you can integrate accessibility checks into a front-end development pipeline to verify UI components meet WCAG 2.2 AA standards before merging changes or as part of a continuous integration process.

What is the difference between automated and manual accessibility testing for web components?▼

Automated accessibility testing uses axe to programmatically detect violations, while manual testing verifies against a checklist to catch nuanced UI barriers, ensuring comprehensive WCAG 2.2 AA compliance.

Do I need additional dependencies to run an accessibility audit?▼

No additional dependencies are required to run the accessibility audit, as the Skill operates independently with included scripts and references to perform automated axe checks and manual verification.

When should I run an accessibility audit on my UI components?▼

You should run an accessibility audit on your UI components before merging UI changes to ensure they meet WCAG 2.2 AA standards and prevent introducing new barriers for users with disabilities.

Related Skills

Explore More Software Engineering Skills→
OthmanAdiOthmanAdi

gmira-verify

Execute Playwright audits across five viewports to detect layout, accessibility, and performance regressions.

Community
Advanced
kinncjkinncj
23

a11y-audit

Run WCAG 2.2 AA audits on generated UI and post PR comments.

Community
Advanced
Serg28Serg28

pest-testing

Automate PHP unit, feature, browser, and architecture tests with Pest 4.

Community
Intermediate
SensLiaoSensLiao

qa-a11y-compliance

Scan web applications for WCAG 2.2 AA accessibility compliance.

Community
Advanced