skills.rest
ArogyaReddy
ArogyaReddyCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

Audit user interfaces for WCAG 2.2 compliance and implement ARIA patterns.

Updated Apr 19, 2026
Search Tags:#accessibility#screen-readers#keyboard-navigation#inclusive-design#aria-patterns#wcag-2.2
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill accessibility-compliance-arogyareddy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/ui-design/skills/accessibility-compliance
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill accessibility-compliance-arogyareddy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support to ensure inclusive experiences.

Core Features & Use Cases

  • ARIA pattern guidance and best practices for screen reader compatibility.
  • Accessibility auditing templates for WCAG 2.2 conformance across web and mobile interfaces.
  • Use Case: When auditing accessibility, implementing ARIA patterns, and ensuring inclusive experiences.

Quick Start

Audit a UI for WCAG 2.2 compliance and implement ARIA patterns to improve screen reader support.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit a user interface for WCAG 2.2 compliance?▼

To audit a user interface for WCAG 2.2 compliance, identify accessibility gaps and map them directly to specific WCAG 2.2 criteria. This process generates clear documentation and reusable patterns to guide developers and testers in resolving issues.

What are the best ARIA patterns for screen reader compatibility?▼

The best ARIA patterns for screen reader compatibility involve applying specific ARIA guidance to dynamic content and forms. This ensures dynamic interface changes are properly announced and navigable by assistive technologies.

How do I implement keyboard navigation for accessible web forms?▼

Implement keyboard navigation for accessible web forms by applying established ARIA patterns and keyboard interaction improvements. This ensures all form inputs and dynamic elements are fully operable without a mouse.

Does inclusive design require mobile accessibility considerations?▼

Yes, inclusive design requires mobile accessibility considerations to ensure broad access. Applying mobile-specific WCAG 2.2 criteria guarantees dynamic content and forms function correctly across various mobile platforms.

Why does my dynamic content fail WCAG 2.2 conformance checks?▼

Dynamic content fails WCAG 2.2 conformance checks when accessibility gaps exist in ARIA implementation or keyboard navigation. Mapping these gaps to WCAG criteria highlights missing inclusive design patterns for assistive technologies.

Related Skills

Explore More Design & Creative Skills→
dodygdodyg

cognitive-accessibility

Evaluate web interfaces against WCAG 2.2 cognitive criteria and COGA guidance.

Community
Intermediate
zinohomezinohome
1

accessibility-auditor

Audit web pages for WCAG 2.1 compliance and implement accessibility fixes.

Community
Advanced
sigmadigitalzasigmadigitalza
1

frontend-accessibility-review

Audit web frontends for WCAG 2.2 AA conformance with static and live checks.

Official
Advanced
The-AIOSThe-AIOS
15

accessibility-compliance

Implement WCAG 2.2 compliant interfaces with ARIA patterns and accessibility audits.

Official
Intermediate