skills.rest
milith0kun
milith0kunCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

Audit web and mobile interfaces for WCAG 2.2 conformance and implement ARIA patterns.

Updated Aug 23, 2026
Search Tags:#accessibility#screen-reader#keyboard-navigation#inclusive-design#aria-patterns#wcag-2.2
One-click install
npx skills add https://github.com/milith0kun/Judiscribe --skill accessibility-compliance-milith0kun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/milith0kun/Judiscribe/tree/main/.claude/skills/accessibility-compliance
Command: npx skills add https://github.com/milith0kun/Judiscribe --skill accessibility-compliance-milith0kun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams deliver web and mobile interfaces that meet WCAG 2.2, ARIA practices, and inclusive design, reducing barriers for users with disabilities.

Core Features & Use Cases

  • WCAG 2.2 conformance guidance and accessibility audits for digital products.
  • ARIA patterns, keyboard navigation, and screen reader compatibility optimization.
  • Mobile accessibility considerations and best practices for inclusive design across platforms.
  • Use Case: Audit a complex form or navigation structure to identify and fix accessibility gaps, then implement fixes and re-test.

Quick Start

Audit a UI for WCAG 2.2 conformance and implement ARIA patterns to improve accessibility.

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 web interface for WCAG 2.2 conformance?▼

To audit a web interface for WCAG 2.2 conformance, you evaluate semantic HTML, robust ARIA usage, keyboard operability, focus management, color contrast, and mobile accessibility standards to identify and close accessibility gaps.

What ARIA patterns should I use to fix screen reader compatibility issues?▼

Fixing screen reader compatibility issues requires implementing robust ARIA patterns and semantic HTML to ensure complex forms and navigation structures are properly announced and operable by assistive technologies.

How do I harden keyboard navigation for complex web forms?▼

Harden keyboard navigation by applying focus management techniques and semantic HTML, ensuring all interactive elements are fully operable without a mouse and meet WCAG 2.2 keyboard access requirements.

Does this approach cover mobile accessibility standards and inclusive design?▼

Yes, this approach covers mobile accessibility standards and inclusive design, applying best practices across platforms to reduce barriers for users with disabilities on both web and mobile interfaces.

When do I need to check color contrast for WCAG compliance?▼

You need to check color contrast during an accessibility audit to ensure text and interactive elements meet WCAG 2.2 visual requirements, preventing barriers for users with visual impairments.

What is the best way to close accessibility gaps in digital products?▼

The best way to close accessibility gaps is to conduct a thorough audit of UI components, implement ARIA patterns and keyboard navigation fixes, then re-test to verify WCAG 2.2 conformance.

Related Skills

Explore More Software Engineering Skills→
suhwansuhwan

web-design-guidelines

Analyze UI source code for accessibility, semantic HTML, and keyboard navigation issues.

Community
Intermediate
Higashi-KotaHigashi-Kota

a11y

Audits UI components for WCAG 2.2 AA and ARIA compliance.

Community
Intermediate
Community-AccessCommunity-Access
387

Contrast Master

Audit color contrast and visual accessibility for WCAG AA compliance.

Official
Advanced
NITRR-OfficialNITRR-Official
4

Accessibility Auditor

Evaluate website accessibility against WCAG 2.1 AA/AAA standards and ARIA implementation.

Official
Advanced