accessibility-audit

Audit web components for WCAG 2.1 AA accessibility issues.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill accessibility-audit-aroido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/accessibility-audit
Command: npx skills add https://github.com/aroido/vibesmith --skill accessibility-audit-aroido

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and designers identify and fix accessibility issues in their web components, ensuring compliance with WCAG 2.1 AA standards and making digital products usable for everyone.

Core Features & Use Cases

  • WCAG 2.1 AA Auditing: Provides a comprehensive checklist and guidance based on the four POUR principles (Perceivable, Operable, Understandable, Robust).
  • Code Examples: Demonstrates correct and incorrect implementations for keyboard accessibility, semantic HTML, ARIA attributes, color contrast, alt text, and form accessibility.
  • Tool Integration: Recommends and shows how to use automated tools like jest-axe, ESLint plugins, and Lighthouse for efficient auditing.
  • Manual Testing Guidance: Outlines essential manual testing steps using keyboard-only navigation, screen readers, and zoom functionality.
  • Use Case: When building a new UI component, use this Skill to proactively ensure it meets accessibility requirements from the start, preventing costly rework later.

Quick Start

Run an accessibility audit on the current project's codebase to identify and suggest fixes for WCAG 2.1 AA violations.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I check my web components for WCAG 2.1 AA compliance?

Check WCAG 2.1 AA compliance by auditing keyboard navigation, semantic HTML, ARIA attributes, and color contrast. This Skill provides a comprehensive checklist based on the four POUR principles and offers code examples to fix identified violations.

What is the best way to automate accessibility testing in my web development workflow?

Automate accessibility testing by integrating tools like jest-axe, ESLint plugins, and Lighthouse. This Skill demonstrates how to configure these automated tools to efficiently detect WCAG 2.1 AA violations during your development process.

Does manual testing matter for web accessibility if I already use automated tools?

Manual testing is essential for web accessibility because automated tools cannot catch all issues. This Skill outlines manual testing procedures using keyboard-only navigation, screen readers, and zoom functionality to ensure full operability and perceivability.

How do I fix form accessibility and keyboard navigation issues?

Fix form accessibility and keyboard navigation issues by implementing correct semantic HTML and ARIA attributes. This Skill provides specific code examples demonstrating correct and incorrect implementations for focus management and form accessibility.

Can I use jest-axe and Lighthouse to detect ARIA attribute violations?

Yes, you can use jest-axe and Lighthouse to detect ARIA attribute violations. This Skill recommends and shows how to integrate these automated tools to identify incorrect ARIA usage and other WCAG 2.1 AA standard failures.