accessibility-compliance

Audit web interfaces for WCAG 2.2 accessibility compliance and implement ARIA patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/acabreragnz/dotfiles --skill accessibility-compliance-acabreragnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/acabreragnz/dotfiles/tree/main/.claude/skills/accessibility-compliance
Command: npx skills add https://github.com/acabreragnz/dotfiles --skill accessibility-compliance-acabreragnz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create digital products that are usable by everyone, regardless of ability, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG Compliance: Implement interfaces that meet WCAG 2.2 guidelines (A, AA, AAA).
  • Assistive Technology Support: Ensure compatibility with screen readers, keyboard navigation, and other assistive technologies.
  • Inclusive Design: Apply patterns that benefit all users, such as clear focus indicators and sufficient color contrast.
  • Use Case: Audit an existing web application for accessibility violations and refactor components to meet WCAG AA standards, ensuring screen reader users can navigate and interact with all features.

Quick Start

Review the provided code examples for implementing an accessible button component.

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 compliance?

To audit web interfaces for WCAG 2.2 compliance, you review existing components against accessibility standards, identify violations, and refactor elements like focus indicators and ARIA patterns to meet AA standards.

What are the best ways to implement ARIA patterns for screen reader compatibility?

Implementing ARIA patterns for screen readers involves applying inclusive design practices that ensure assistive technologies can accurately navigate and interact with digital interface features across web and mobile platforms.

Does this approach support mobile accessibility and assistive technology integration?

Yes, inclusive design and accessibility compliance techniques support mobile platforms by ensuring digital interfaces integrate seamlessly with assistive technologies like screen readers and keyboard navigation.

How do I refactor components to meet WCAG AA accessibility standards?

Refactoring components to meet WCAG AA accessibility standards requires updating interactive elements to ensure sufficient color contrast, clear focus indicators, and full screen reader navigation capabilities.

What is inclusive design and how does it improve screen reader navigation?

Inclusive design improves screen reader navigation by applying accessibility patterns that benefit all users, ensuring digital interfaces are usable regardless of ability through proper WCAG 2.2 guideline adherence.

Can I use these WCAG 2.2 guidelines for both web and mobile platforms?

Yes, WCAG 2.2 guidelines apply to both web and mobile platforms, ensuring inclusive user experiences by standardizing assistive technology integration and addressing accessibility challenges across environments.