skills.rest
Sumeet138
Sumeet138COMMUNITY
Explore all skills by this author →
Website𝕏@SumitGond28GitHub

accessibility-compliance

Audit and implement WCAG 2.2 accessibility across web and mobile interfaces.

1|Updated Apr 14, 2026
Search Tags:#accessibility#usability#wcag#screen-reader#aria#inclusive-design
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill accessibility-compliance-sumeet138
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/ui-design/skills/accessibility-compliance
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill accessibility-compliance-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web and mobile interfaces often fail accessibility checks, excluding users with disabilities and risking non-compliance.

Core Features & Use Cases

  • ARIA patterns and WCAG 2.2 guideline mapping to real UI components
  • Screen reader and keyboard navigation compatibility across forms, modals, and navigation
  • Inclusive design patterns and best practices with practical checklists

Quick Start

Audit and implement WCAG 2.2 accessibility across digital interfaces.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I make my web interface WCAG 2.2 compliant?▼

To make a web interface WCAG 2.2 compliant, audit and implement guidelines using ARIA patterns, screen reader compatibility, and inclusive design checklists across forms, navigation, and content.

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

The best ARIA patterns for screen reader compatibility map WCAG 2.2 guidelines directly to real UI components, ensuring keyboard navigation and inclusive design across forms, modals, and navigation.

Does WCAG 2.2 accessibility auditing work for mobile interfaces?▼

WCAG 2.2 accessibility auditing applies to both web and mobile interfaces, providing reference guidelines and practical patterns to ensure inclusive design and screen reader compatibility across platforms.

How do I implement keyboard navigation for modals and forms?▼

Implement keyboard navigation for modals and forms by applying WCAG 2.2 ARIA patterns and inclusive design best practices, ensuring full screen reader compatibility and focus management across elements.

Why does my inclusive design fail accessibility checks?▼

Inclusive design fails accessibility checks when UI components lack proper WCAG 2.2 guideline mapping, missing ARIA patterns, or insufficient keyboard navigation and screen reader compatibility.

Do I need ARIA patterns for all digital interface elements?▼

You need ARIA patterns for interactive digital interface elements like forms, modals, and navigation to meet WCAG 2.2 compliance, ensuring screen reader compatibility and keyboard navigation.

Related Skills

Explore More Design & Creative Skills→
thc1006thc1006
20

accessibility-compliance

Audit web and mobile interfaces against WCAG 2.2 and implement ARIA fixes.

Community
Intermediate
Omar-CcOmar-Cc

accessibility

Audit web interfaces against WCAG 2.2 criteria and resolve accessibility issues.

Community
Advanced
JaivishChauhanJaivishChauhan
6

accessibility

Apply WCAG-compliant semantics to portfolio pages for keyboard and screen reader accessibility.

Community
Intermediate
leonardoteodorooleonardoteodoroo

accessibility-compliance

Guides teams to implement WCAG 2.2 compliant accessibility across web interfaces.

Community
Intermediate