wcag-compliance

Audit and implement WCAG 2.2 AA accessibility patterns for web applications.

2|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/haotool/app --skill wcag-compliance-haotool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag-compliance
Source: https://github.com/haotool/app/tree/main/.agents/skills/wcag-compliance
Command: npx skills add https://github.com/haotool/app --skill wcag-compliance-haotool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web accessibility and WCAG 2.2 AA compliance patterns are often neglected, leading to inaccessible UIs and potential legal risk.

Core Features & Use Cases

  • Semantic HTML and landmark structure guidance for accessible layouts
  • ARIA patterns and focus management techniques for dynamic content
  • Comprehensive checklists, examples, and best practices for audits and implementation

Quick Start

Audit a web project for WCAG 2.2 AA patterns and implement the recommended fixes.

Frequently Asked Questions about wcag-compliance

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

FAQPage Schema
How do I audit a web application for WCAG 2.2 AA compliance?

Audit web apps for WCAG 2.2 AA compliance by checking semantic HTML structures, ARIA patterns, focus management, color contrast, and keyboard navigation against established accessibility checklists and code-ready examples.

What ARIA patterns and focus management techniques work best for dynamic SPA content?

For dynamic SPA content, use robust ARIA patterns, precise focus management techniques, and live regions to handle updates seamlessly while maintaining keyboard navigation and semantic HTML structures.

Do I need semantic HTML landmarks for accessible UI production?

Semantic HTML landmarks are essential for accessible UI production, providing foundational layout structures that screen readers navigate, which ARIA patterns then enhance for dynamic web application interactions.

What is the best way to implement keyboard navigation and color contrast for WCAG compliance?

Implement keyboard navigation and color contrast for WCAG compliance by applying semantic HTML, ARIA patterns, and focus management checklists during component design and development workflows across modern web apps.

Can this accessibility guidance be applied to modern web app component design?

Yes, these WCAG 2.2 AA accessibility patterns apply directly to component design and development workflows across modern web apps, SPAs, and accessible UI production with code-ready examples and checklists.