accessibility

Identify and fix web accessibility gaps using WCAG 2.2 guidelines.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Fabianrzs/car-wash --skill accessibility-fabianrzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Fabianrzs/car-wash/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/Fabianrzs/car-wash --skill accessibility-fabianrzs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.2 guidelines. This guide covers the POUR principles (Perceivable, Operable, Understandable, Robust) and practical patterns to ensure content is usable by people with disabilities.

Core Features & Use Cases

  • Provides comprehensive WCAG-aligned guidelines and practical examples for text alternatives, keyboard navigation, color contrast, ARIA usage, and Lighthouse checks.
  • Supports audits, design reviews, and implementation tasks to improve accessibility across websites, apps, and components.
  • Use case: Run an accessibility audit on a product page and generate a prioritized list of fixes aligned with WCAG 2.2 success criteria.

Quick Start

Inspect the current page for accessibility gaps and propose actionable fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my web project?

To run a WCAG 2.2 accessibility audit, you inspect your web project against the POUR principles to identify gaps and generate a prioritized list of fixes aligned with success criteria. This ensures inclusive experiences across your interfaces.

What's the best way to fix keyboard navigation and screen-reader gaps?

The best way to fix keyboard navigation and screen-reader gaps is by applying established accessibility patterns and ARIA usage guidelines. This ensures your interfaces are operable and perceivable for users relying on assistive technologies.

How does Lighthouse check web accessibility?

Lighthouse checks web accessibility by evaluating your page against established audit criteria to identify gaps. It complements manual reviews by verifying perceivable, operable, understandable, and robust interface patterns.

Can I use this for design reviews and implementation tasks?

Yes, you can use this for design reviews and implementation tasks. It applies WCAG 2.2 guidelines across audits and development workflows to ensure content is usable by people with disabilities throughout the entire lifecycle.

What are the POUR principles for inclusive web interfaces?

The POUR principles for inclusive web interfaces are Perceivable, Operable, Understandable, and Robust. They form the core framework to ensure all users can effectively navigate and comprehend digital content.

Why does my web component fail color contrast success criteria?

Your web component fails color contrast success criteria because it does not meet WCAG 2.2 guidelines for visual accessibility. You must adjust your color choices to ensure content is perceivable for users with visual impairments.