accessibility-wcag

Enforce WCAG 2.2 AAA accessibility rules for web content.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace --skill accessibility-wcag-thephoenixagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-wcag
Source: https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace/tree/main/skills/accessibility-wcag
Command: npx skills add https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace --skill accessibility-wcag-thephoenixagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and designers ensure their web content meets the highest standards of accessibility, specifically WCAG 2.2 AAA, by providing guidelines and checks for keyboard navigation, semantic structure, color contrast, and ARIA implementation.

Core Features & Use Cases

  • Mandatory Rules Checklist: Verifies essential accessibility requirements like full keyboard navigation, correct semantic hierarchy, form label presence, alt text for images, and sufficient color contrast (AAA level).
  • ARIA Patterns: Provides examples of correct ARIA usage for dynamic content, states, and roles.
  • Use Case: A web development team can use this skill to audit a new feature before launch, ensuring it's usable by people with disabilities and meets stringent compliance standards.

Quick Start

Verify that the current web page adheres to all mandatory accessibility rules for WCAG 2.2 AAA compliance.

Frequently Asked Questions about accessibility-wcag

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

FAQPage Schema
How do I check my web page for WCAG 2.2 AAA accessibility compliance?

To check WCAG 2.2 AAA accessibility compliance, validate your web page against mandatory rules for keyboard navigation, semantic HTML hierarchy, form labels, alt text, and color contrast. This process enforces inclusive design standards and ensures assistive technology compatibility.

What keyboard navigation and ARIA patterns do I need for accessible web development?

Accessible web development requires full keyboard navigation support, correct semantic HTML, and proper ARIA patterns for dynamic states and roles. Implementing these ensures users with disabilities can interact with dynamic content using assistive technologies effectively.

Does my web application need AAA color contrast ratios to be accessible?

Meeting AAA color contrast ratios is a mandatory requirement for WCAG 2.2 AAA compliance. Your web application must pass contrast checks alongside keyboard navigation and semantic structure validations to achieve the highest inclusive design standards.

Why does my dynamic content fail assistive technology compatibility checks?

Dynamic content fails assistive technology compatibility checks when it lacks correct ARIA patterns for states and roles. Ensuring proper semantic HTML and ARIA implementation resolves these issues, meeting stringent accessibility compliance requirements.

When do I need to enforce WCAG 2.2 AAA standards during web development?

You need to enforce WCAG 2.2 AAA standards during web development when auditing a new feature before launch or targeting the highest level of inclusive design. This ensures all content is usable by people with disabilities and meets stringent compliance.