accessibility

Audit web accessibility against WCAG 2.2 guidelines and generate fixes.

1|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/carlosalberto05/perritos-refugio-frontend --skill accessibility-carlosalberto05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/carlosalberto05/perritos-refugio-frontend/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/carlosalberto05/perritos-refugio-frontend --skill accessibility-carlosalberto05

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.2 guidelines. The Skill provides a structured approach to ensure content is usable by everyone, including people with disabilities.

Core Features & Use Cases

  • Comprehensive checks aligned with WCAG 2.2 (POUR) and Lighthouse accessibility audits.
  • Guidance on keyboard navigation, screen reader support, color contrast, focus management, and ARIA usage patterns.
  • Use cases include auditing existing pages, retrofitting accessibility during development, and creating accessibility checklists for teams.

Quick Start

Ask the AI to audit a webpage for WCAG 2.2 conformance and generate actionable fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my website for WCAG 2.2 conformance?

Audit web accessibility for WCAG 2.2 conformance by checking POUR principles, keyboard navigation, screen reader support, and color contrast. This generates actionable fixes and a practical checklist to guide your implementation.

How do I fix Lighthouse accessibility audit failures?

Fix Lighthouse accessibility audit failures by addressing identified color contrast, keyboard navigation, and screen reader support issues. Apply correct ARIA usage patterns and focus management to meet WCAG 2.2 conformance levels.

What is the best way to add screen reader support and ARIA patterns?

Add screen reader support by implementing correct ARIA usage patterns and managing focus. Follow WCAG 2.2 guidelines to ensure proper conformance levels and ensure web content is accessible to all users.

Does this WCAG 2.2 checklist work for auditing existing web apps?

This WCAG 2.2 checklist works for auditing existing pages and retrofitting accessibility during development. It provides comprehensive checks for keyboard navigation, color contrast, and screen reader support for teams.

When do I need to manually check keyboard navigation beyond automated audits?

You need to manually check keyboard navigation when automated audits cannot verify logical tab order and focus management. Ensure all interactive elements are operable without a mouse to meet POUR principles.