skills.rest
thc1006
thc1006COMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-compliance

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

20|3|Updated Jul 26, 2025
Search Tags:#accessibility#a11y#wcag#screen-reader#aria#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/thc1006/nephoran-intent-operator --skill accessibility-compliance-thc1006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/thc1006/nephoran-intent-operator/tree/main/.claude/skills/accessibility-compliance
Command: npx skills add https://github.com/thc1006/nephoran-intent-operator --skill accessibility-compliance-thc1006

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams build and verify accessible interfaces that meet WCAG 2.2 standards, reducing barriers for users with disabilities.

Core Features & Use Cases

  • Accessibility pattern implementation, keyboard navigation, screen reader compatibility, and mobile accessibility best practices.
  • Auditing and remediation across forms, navigation, content semantics, and dynamic updates.
  • Use Case: A development team audits a web app and increases accessibility scores by implementing semantic HTML, proper labels, and ARIA attributes.

Quick Start

Audit a sample interface against WCAG 2.2 and implement ARIA patterns to fix detected accessibility violations.

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 compliance?▼

WCAG 2.2 compliance is achieved by evaluating semantic HTML, ARIA attributes, and keyboard operability across forms, navigation, and dynamic components to identify and rectify accessibility gaps for screen reader compatibility.

What are the WCAG 2.2 requirements for keyboard navigation and screen reader compatibility?▼

WCAG 2.2 requirements for keyboard navigation and screen reader compatibility involve implementing semantic HTML, accessible patterns, and proper ARIA attributes to ensure interactive elements are operable and announced correctly.

How do I fix ARIA roles and semantic HTML issues in dynamic web components?▼

Fixing ARIA roles and semantic HTML issues in dynamic components involves applying WCAG 2.2 accessible patterns, ensuring proper labels, and managing dynamic updates so screen readers accurately announce content changes.

Does this approach support mobile accessibility and inclusive design audits?▼

This approach supports mobile accessibility and inclusive design audits by applying WCAG 2.2 conformance requirements to mobile interfaces, verifying touch targets, and ensuring content semantics meet accessibility standards.

What is the best way to remediate accessibility violations in web forms?▼

The best way to remediate accessibility violations in web forms is to implement proper labels, semantic HTML, and ARIA attributes while verifying keyboard operability and screen reader interactions against WCAG 2.2 standards.

Why do I need semantic HTML and ARIA attributes for WCAG conformance?▼

Semantic HTML and ARIA attributes are essential for WCAG conformance because they provide the structural and contextual cues that screen readers rely on to navigate forms, content, and dynamic components accurately.

Related Skills

Explore More Design & Creative Skills→
AI-Foundry-CoreAI-Foundry-Core
4

accessibility-compliance

Audit and enforce WCAG 2.2 accessibility compliance for web and mobile UI components.

Official
Advanced
leonardoteodorooleonardoteodoroo

accessibility-compliance

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

Community
Intermediate
pelcherspelchers

ensuring-accessibility

Implement WCAG 2.1 AA-compliant accessibility patterns for web interfaces.

Community
Advanced
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced