accessibility

Audit web accessibility compliance using WCAG 2.2 patterns and Lighthouse.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chapter42/42-SEO-Skills --skill accessibility-chapter42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/chapter42/42-SEO-Skills/tree/main/skills/references/web-quality/accessibility
Command: npx skills add https://github.com/chapter42/42-SEO-Skills --skill accessibility-chapter42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web content often misses accessibility expectations, leaving users with barriers to perceiving, navigating, and interacting with digital products. This Skill provides WCAG 2.2–aligned guidelines, practical patterns, and evaluation prompts to help teams identify and fix accessibility gaps.

Core Features & Use Cases

  • WCAG-aligned audit guidance and checklists for perceivable, operable, understandable, and robust content.
  • Concrete patterns for text alternatives, keyboard navigation, focus management, color contrast, and error handling, plus Lighthouse pattern references.
  • Real-world use cases during design reviews, development sprints, and accessibility remediation projects.

Quick Start

Run an accessibility check on your page using the included WCAG patterns to begin prioritizing improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit web accessibility compliance for my website?

Audit web accessibility compliance by applying WCAG 2.2 aligned guidelines and checklists to identify perceivable, operable, understandable, and robust content gaps. Use practical patterns for text alternatives, keyboard navigation, focus management, color contrast, and error handling to remediate identified issues.

What WCAG 2.2 patterns should I check during a web accessibility review?

Check WCAG 2.2 patterns for text alternatives, keyboard navigation, focus management, color contrast, and error handling during web accessibility reviews. Apply these practical patterns during design reviews, development sprints, and accessibility remediation projects to ensure perceivable, operable, understandable, and robust content compliance.

Can I use Lighthouse audits to guide web accessibility implementation?

Yes, you can use Lighthouse audits to guide web accessibility implementation with included pattern references. Combine Lighthouse audit results with WCAG 2.2 guidelines to prioritize improvements and apply concrete patterns for text alternatives, keyboard navigation, focus management, and color contrast fixes.

What is the best way to fix keyboard navigation and focus management issues?

Fix keyboard navigation and focus management issues by applying WCAG 2.2 aligned practical patterns for operable content. Implement concrete code examples for keyboard navigation and focus management to ensure perceivable, operable, understandable, and robust content compliance during development sprints.

When do I need to run an accessibility check during the development process?

Run an accessibility check during design reviews, development sprints, and release stages to identify and fix accessibility gaps early. Apply WCAG 2.2 patterns and Lighthouse audit references to prioritize improvements for perceivable, operable, understandable, and robust content compliance.

How do I handle color contrast and error handling for accessible web apps?

Handle color contrast and error handling for accessible web apps by applying WCAG 2.2 aligned concrete patterns. Use practical code examples to guide implementation of color contrast and error handling fixes, ensuring perceivable, operable, understandable, and robust content compliance for websites and web apps.