accessibility-compliance

Implement WCAG 2.2 standards for digital interfaces and accessibility.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/yusufcmg/Antigravity-Agents-Workflows --skill accessibility-compliance-yusufcmg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/yusufcmg/Antigravity-Agents-Workflows/tree/main/.agent/skills/design/accessibility-compliance
Command: npx skills add https://github.com/yusufcmg/Antigravity-Agents-Workflows --skill accessibility-compliance-yusufcmg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your digital interfaces are usable by everyone, regardless of ability, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG Compliance: Implement guidelines for perceivable, operable, understandable, and robust interfaces.
  • Assistive Technology Support: Build for screen readers, keyboard navigation, and other assistive tools.
  • Use Case: You need to ensure a new web application meets WCAG 2.2 AA standards before launch, including proper ARIA implementation for custom components and robust keyboard navigation.

Quick Start

Use the accessibility-compliance skill to audit the provided component code for WCAG 2.2 violations.

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.2 AA compliance?

To audit for WCAG 2.2 AA compliance, evaluate your component code against perceivability, operability, understandability, and robustness standards. This includes checking ARIA implementation for custom components and verifying robust keyboard navigation support.

What is the best way to implement ARIA patterns for screen reader support?

Implementing ARIA patterns for screen reader support involves applying Web Content Accessibility Guidelines (WCAG) 2.2 standards to digital interfaces. This ensures custom components are properly announced and interactable via assistive technologies.

How do I ensure mobile accessibility and inclusive design for custom interfaces?

Ensuring mobile accessibility and inclusive design requires addressing perceivability, operability, understandability, and robustness on mobile platforms. Focus on keyboard navigation, screen reader interactions, and assistive technology support.

Can I use this approach to fix keyboard navigation issues in custom components?

Yes, addressing keyboard navigation issues in custom components is a core part of ensuring operability under WCAG 2.2 standards. You must implement inclusive design patterns that guarantee interfaces are fully usable without a mouse.

Do I need assistive technology support testing to meet inclusive design standards?

Yes, assistive technology support testing is essential for inclusive design. You must build for screen readers and keyboard navigation to ensure your interfaces are operable and robust for all users regardless of ability.

What are the limitations of relying solely on automated accessibility audits?

Relying solely on automated audits misses contextual perceivability and understandability issues. Implementing WCAG 2.2 standards requires manual evaluation of ARIA patterns, keyboard navigation flows, and inclusive design patterns to ensure true compliance.