accessibility-compliance

Audit web applications for WCAG 2.1/2.2 compliance with axe-core.

6|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill accessibility-compliance-repairyourtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skill-library/surface/web/accessibility-compliance
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill accessibility-compliance-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web applications usable by everyone, including people with disabilities, by adhering to accessibility standards.

Core Features & Use Cases

  • WCAG Compliance: Audits and guides implementation for WCAG 2.1/2.2 standards (A, AA, AAA).
  • ARIA Support: Provides correct ARIA patterns for custom components and dynamic content.
  • Keyboard Navigation: Ensures logical tab order and effective focus management.
  • Screen Reader Optimization: Guides implementation for live regions, visually hidden content, and semantic structure.
  • Color Contrast & Legibility: Offers guidance on meeting contrast ratios and readable text.
  • Use Case: Audit an existing e-commerce site to identify and fix accessibility barriers, ensuring compliance with ADA and EAA regulations before launch.

Quick Start

Use the accessibility-compliance skill to audit the current web page for WCAG 2.1 AA compliance.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit my web application for WCAG 2.1 AA compliance?

To audit for WCAG 2.1 AA compliance, evaluate semantic HTML, ARIA roles, keyboard navigation, and color contrast. Automated tools like axe-core and manual checklists identify barriers to ensure your web application meets ADA and Section 508 standards.

What ARIA patterns should I use for custom web components?

Correct ARIA patterns for custom components require managing ARIA roles, states, and properties to communicate dynamic content changes. Proper implementation ensures screen readers accurately interpret interactions that native semantic HTML cannot cover.

How do I ensure keyboard navigation and focus management work correctly?

Keyboard navigation requires a logical tab order and effective focus management across interactive elements. Managing focus ensures users navigating via keyboard can access all functionalities without relying on a mouse or losing their place.

Does this accessibility compliance approach address legal requirements like ADA and EAA?

Yes, this approach addresses legal requirements including ADA, Section 508, and EAA. By auditing and guiding WCAG 2.1/2.2 implementation, it ensures web applications meet necessary legal accessibility standards before launch.

What is the best way to optimize web applications for screen readers?

Screen reader optimization involves implementing live regions, visually hidden content, and semantic structure. These techniques ensure dynamic updates and page layouts are announced clearly to users relying on assistive technologies.

How do I fix color contrast issues to meet WCAG accessibility standards?

Fixing color contrast involves adjusting foreground and background colors to meet WCAG contrast ratios. Ensuring readable text and legible interfaces allows users with visual impairments to perceive content effectively.