accessibility-compliance

Implement WCAG 2.2 standards for accessible user interfaces.

38.6k|4.1k|Updated Jul 24, 2025
One-click install
npx skills add https://github.com/wshobson/agents --skill accessibility-compliance-wshobson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/wshobson/agents/tree/main/plugins/ui-design/skills/accessibility-compliance
Command: npx skills add https://github.com/wshobson/agents --skill accessibility-compliance-wshobson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your user interfaces meet the highest standards of accessibility, making them usable by everyone, including people with disabilities.

Core Features & Use Cases

  • WCAG 2.2 Compliance: Implement guidelines for perceivable, operable, understandable, and robust interfaces.
  • Assistive Technology Support: Ensure compatibility with screen readers, keyboard navigation, and other assistive technologies.
  • Inclusive Design: Apply patterns for mobile accessibility, high contrast modes, and reduced motion.
  • Use Case: Audit an existing web application for accessibility violations and refactor components to meet WCAG 2.2 AA standards, ensuring screen reader users can fully interact with forms and navigation.

Quick Start

Use the accessibility-compliance skill to audit the provided component code for WCAG 2.2 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.2 compliance?

Audit WCAG 2.2 compliance by evaluating component code against perceivability, operability, understandability, and robustness standards. This process identifies accessibility violations and guides refactoring to meet AA standards for screen reader compatibility.

What are the WCAG 2.2 requirements for screen reader compatibility?

WCAG 2.2 screen reader compatibility requires semantic HTML structure, correct ARIA patterns, and robust interfaces. These ensure assistive technologies can accurately perceive and interact with forms and navigation elements.

Can I use this to fix keyboard navigation issues in my interface?

Yes, you can fix keyboard navigation issues by implementing WCAG 2.2 operability standards. This ensures all interactive elements are fully accessible without a mouse, meeting inclusive design requirements.

Does this accessibility checker support mobile platforms?

Yes, this accessibility checker supports mobile platforms by applying inclusive design patterns specific to mobile accessibility. It ensures interfaces meet WCAG 2.2 standards across both web and mobile environments.

What's the best way to implement ARIA patterns for accessible forms?

The best way to implement ARIA patterns is by combining them with semantic HTML structure to ensure robust interfaces. This guarantees forms are perceivable and operable for assistive technology users under WCAG 2.2.

When do I need to adjust contrast ratios for high contrast modes?

Adjust contrast ratios for high contrast modes when interfaces fail WCAG 2.2 perceivability standards. Meeting specific ratio requirements ensures content remains readable for users with visual impairments.