accessibility-compliance

Implement WCAG 2.2 compliant accessibility patterns and remediation guidance for web and mobile interfaces.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mrodrigues1/akachan --skill accessibility-compliance-mrodrigues1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/mrodrigues1/akachan/tree/main/.junie/skills/accessibility-compliance
Command: npx skills add https://github.com/mrodrigues1/akachan --skill accessibility-compliance-mrodrigues1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides actionable guidance, patterns, and checklists to eliminate accessibility barriers and achieve WCAG 2.2 compliance across web and mobile user interfaces, ensuring inclusive experiences for people with disabilities.

Core Features & Use Cases

  • WCAG 2.2 Guidance: Clear mapping of Perceivable, Operable, Understandable, and Robust principles with prioritized success criteria.
  • ARIA & Semantic Patterns: Examples and best practices for roles, states, properties, live regions, accordions, tabs, and comboboxes.
  • Keyboard & Focus Management: Focus trapping, focus indicators, logical tab order, and keyboard shortcuts for interactive components.
  • Screen Reader & Mobile Support: VoiceOver and TalkBack patterns, content descriptions, live regions, and dynamic announcements.
  • Visual & Interaction Requirements: Contrast ratio thresholds, touch target sizing, reduced motion handling, and text scaling strategies.
  • Testing & Audit Checklist: Automated and manual tool recommendations, audit steps, and common pitfalls to fix.

Quick Start

Use the accessibility-compliance skill to audit the main screen and produce a prioritized list of WCAG 2.2 issues with recommended fixes.

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 UI compliant with WCAG 2.2 Level AA criteria?

WCAG 2.2 Level AA compliance requires implementing ARIA patterns, keyboard navigation, focus management, and screen-reader support. You must also satisfy specific contrast ratio thresholds, target sizing, and live region requirements across web and mobile interfaces.

What are the best practices for ARIA roles and keyboard navigation in accessible web development?

Accessible web development best practices include using proper ARIA roles, states, and properties for dynamic components like accordions and tabs. Keyboard navigation requires logical tab order, visible focus indicators, and focus trapping for interactive elements.

Does this accessibility guidance cover mobile touch targets and screen reader support?

Yes, this accessibility guidance covers mobile touch targets and screen reader support. It provides VoiceOver and TalkBack patterns, content descriptions, dynamic live region announcements, and specific touch target sizing requirements for mobile interfaces.

How do I audit a user interface for accessibility barriers and WCAG issues?

To audit a user interface for accessibility barriers, review main screens against WCAG 2.2 success criteria. Use automated and manual testing tools to identify common pitfalls, then produce a prioritized list of issues with recommended remediation fixes.

What contrast ratios and text scaling strategies are required to prevent accessibility barriers?

Preventing accessibility barriers requires meeting specific visual contrast ratio thresholds and implementing text scaling strategies. You must also handle reduced motion preferences to ensure inclusive visual and interaction experiences for users.