skills.rest
lemu
lemuCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

Implement WCAG 2.2 conformance across UI components and documentation.

Updated Oct 22, 2025
Search Tags:#accessibility#wcag#screen-readers#a11y-testing#keyboard-navigation#inclusive-design#aria-patterns
One-click install
npx skills add https://github.com/lemu/sea-prototype-template --skill accessibility-compliance-lemu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/lemu/sea-prototype-template/tree/main/.agents/skills/accessibility-compliance
Command: npx skills add https://github.com/lemu/sea-prototype-template --skill accessibility-compliance-lemu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implementing WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support can be challenging across products; this skill provides a structured approach and patterns to integrate accessibility from design to deployment.

Core Features & Use Cases

  • WCAG 2.2 conformance patterns including semantic HTML, ARIA roles, keyboard navigation, and focus management.
  • Accessibility auditing guidance, ARIA mapping, and screen reader compatibility for teams building web and mobile experiences.
  • Use Case: Integrate accessibility checks into UI development and testing to ensure inclusive experiences for users with disabilities.

Quick Start

Audit a web UI for WCAG 2.2 conformance and identify actionable ARIA improvements.

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

To audit a web UI for WCAG 2.2 conformance, you evaluate semantic HTML, ARIA roles, keyboard navigation, and focus management to identify actionable accessibility improvements and ensure POUR principles are satisfied.

What is the best way to implement ARIA patterns for screen reader compatibility?▼

The best way to implement ARIA patterns for screen reader compatibility is mapping ARIA roles to semantic HTML, managing live regions properly, and ensuring proper labeling to provide accurate assistive technology support.

Does this approach to inclusive design work for both web and native mobile apps?▼

Yes, this inclusive design approach works for both web and native mobile apps by applying WCAG 2.2 conformance patterns, mobile accessibility testing, and screen reader readiness across the respective platforms.

How do I fix keyboard navigation and focus management issues in accessible interfaces?▼

Fixing keyboard navigation and focus management issues requires implementing proper ARIA patterns, semantic HTML structuring, and logical tab order to ensure inclusive interfaces are fully operable without a mouse.

When do I need to use live regions and color contrast checks for accessibility compliance?▼

You need live regions to announce dynamic content changes to screen readers and color contrast checks to ensure text readability, satisfying WCAG 2.2 POUR principles for perceivable and robust accessible interfaces.

Related Skills

Explore More Design & Creative Skills→
concept2cureconcept2cure

accessibility-enforcement

...

Community
Advanced
buiphucminhtambuiphucminhtam
47

accessibility-engineer

Audit web and mobile interfaces for WCAG 2.2 AA/AAA conformance and ARIA readiness.

Community
Advanced
mauriciodelriomauriciodelrio
3

a11y-rules

Audit React and Next.js components for WCAG 2.2 AA accessibility violations.

Community
Intermediate
bdbchbdbch
2

accessibility-review

Audit web applications for WCAG 2.1/2.2 accessibility compliance in Chrome.

Community
Advanced