skills.rest
vecear
vecearCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-auditor

Audit web applications for WCAG 2.1 accessibility issues.

Updated Jan 21, 2026
Search Tags:#accessibility#a11y#WCAG#semantic-html#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill accessibility-auditor-vecear
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/accessibility-auditor
Command: npx skills add https://github.com/vecear/Nipponverb --skill accessibility-auditor-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web accessibility is essential for inclusive web experiences, and this skill helps teams identify and fix accessibility gaps to meet WCAG 2.1 standards.

Core Features & Use Cases

  • Audit existing web interfaces for WCAG 2.1 conformance and ARIA pattern recommendations.
  • Improve keyboard navigation, screen reader compatibility, and color contrast across components.
  • Provide actionable guidance and checklists to implement accessible UI changes in real projects.

Quick Start

Run an accessibility audit on your project and apply WCAG 2.1 compliant fixes.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I audit my web application for WCAG 2.1 compliance?▼

To audit your web application for WCAG 2.1 compliance, run an accessibility audit that checks ARIA patterns, keyboard navigation, screen reader compatibility, and color contrast. This process provides actionable guidance and checklists to implement accessible UI changes.

What is the best way to fix keyboard navigation and screen reader compatibility issues?▼

The best way to fix keyboard navigation and screen reader compatibility issues is to apply semantic HTML recommendations and ARIA attribute guidance. This ensures your components meet WCAG 2.1 criteria through practical testing workflows.

Can I use automated and manual checks to validate color contrast across components?▼

Yes, you can validate color contrast across components using practical testing workflows with automated and manual checks. This identifies accessibility gaps and provides actionable guidance to satisfy WCAG 2.1 standards.

Does WCAG 2.1 conformance require ARIA patterns and semantic HTML for accessible UI changes?▼

Yes, WCAG 2.1 conformance requires ARIA patterns and semantic HTML to implement accessible UI changes. These recommendations ensure your web interfaces pass both automated and manual accessibility checks.

When do I need to run an accessibility audit on my codebase?▼

You need to run an accessibility audit on your codebase when identifying accessibility gaps to meet WCAG 2.1 standards. It is applied to projects requiring ARIA patterns, keyboard navigation, screen reader support, and color contrast validation.

Related Skills

Explore More Software Engineering Skills→
mouayadakelmouayadakel

accessibility-checker

Check UI components and forms for accessibility attributes and markup suggestions.

Community
Intermediate
lexicalninjalexicalninja
2

accessibility-design-checker

Identify accessibility issues in UI designs, wireframes, and prototypes.

Community
Intermediate
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
Anuj23105Anuj23105
1

accessibility-auditing

Tests web page and UI component accessibility compliance with WCAG 2.1 AA/AAA standards.

Community
Advanced