skills.rest
leonardoteodoroo
leonardoteodorooCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-compliance

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

Updated Feb 3, 2026
Search Tags:#accessibility#a11y#wcag#screen-reader#aria#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill accessibility-compliance-leonardoteodoroo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/accessibility-compliance
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill accessibility-compliance-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility gaps hinder inclusive user experiences and legal compliance. This Skill provides a structured approach to implementing WCAG 2.2 guidelines, ARIA patterns, and assistive tech support across web and mobile interfaces.

Core Features & Use Cases

  • WCAG 2.2 alignment, focus management, and keyboard navigation across applications.
  • ARIA patterns and screen-reader friendly component design.
  • Mobile accessibility features and audits to fix violations in forms, navigation, and content.

Quick Start

Audit your UI against WCAG 2.2 and begin implementing ARIA patterns to build accessible interfaces.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I implement WCAG 2.2 compliance for my web interface?▼

To implement WCAG 2.2 compliance, audit your UI against current guidelines and apply structured ARIA patterns, focus management, and keyboard navigation improvements across your web interfaces.

What is the best way to fix keyboard navigation and screen-reader compatibility issues?▼

Fix keyboard navigation and screen-reader compatibility by implementing proper ARIA patterns and focus management, ensuring all interactive elements are operable and announced correctly to assistive technologies.

Can I use this approach for mobile accessibility audits and inclusive design?▼

Yes, you can apply this approach for mobile accessibility audits to identify and fix violations in forms, navigation, and content while implementing inclusive design across both web and mobile apps.

When do I need ARIA patterns for accessible component design?▼

You need ARIA patterns for accessible component design when native HTML elements cannot convey semantic relationships, requiring screen-reader friendly markup to ensure WCAG 2.2 alignment and proper assistive tech support.

Does this WCAG compliance method require specific dependencies or frameworks?▼

No specific dependencies are required. The method provides a structured approach to evaluating and implementing accessibility guidelines, focusing on ARIA usage and operability across standard web and mobile platforms.

Related Skills

Explore More Legal & Compliance Skills→
AI-Foundry-CoreAI-Foundry-Core
4

wcag-audit-patterns

Audit WCAG 2.2 accessibility with automated testing and remediation guidance.

Official
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
doanchienthangdevdoanchienthangdev
4

implementing-accessibility

Implement WCAG 2.1 AA compliant React interfaces with ARIA and keyboard navigation.

Community
Intermediate
InnerScopeHearingInnerScopeHearing

wcag-audit-patterns

Audit web content for WCAG 2.2 compliance with automated testing and remediation guidance.

Official
Intermediate