0120-accessibility-compliance

Implement WCAG 2.2 accessibility improvements for web and mobile interfaces.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0120-accessibility-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 0120-accessibility-compliance
Source: https://github.com/MrJmpl3/codex_____data_____configuration/tree/main/skills/0120-accessibility-compliance
Command: npx skills add https://github.com/MrJmpl3/codex_____data_____configuration --skill 0120-accessibility-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the common problem of inaccessible interfaces that exclude users relying on keyboards, screen readers, and mobile accessibility features, leading to usability failures and WCAG 2.2 non-compliance.

Core Features & Use Cases

  • WCAG 2.2 alignment: Practical guidance for Perceivable, Operable, Understandable, and Robust requirements, including Level AA/AAA focus and target-size considerations.
  • Accessible ARIA patterns: Clear role/state/property usage for interactive widgets and live regions to support assistive technologies.
  • Keyboard + focus management: Techniques for focus order, visible focus states, modal focus trapping, escape-to-close, and skip-to-content navigation.
  • Screen reader support: Recommendations for semantic HTML, heading structure, alt text strategy, landmarks, and announcement patterns.
  • Mobile accessibility: Touch target sizing and platform support concepts for VoiceOver and TalkBack, plus reduced motion and text scaling considerations.

Quick Start

Use the 0120-accessibility-compliance skill to audit a UI for missing labels, broken keyboard flows, insufficient contrast, and inadequate focus handling, then apply the included accessible component patterns to remediate the issues.

Frequently Asked Questions about 0120-accessibility-compliance

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

FAQPage Schema
How do I audit my UI for WCAG 2.2 compliance issues?

To audit your UI for WCAG 2.2 compliance, check for missing labels, broken keyboard flows, insufficient contrast, and inadequate focus handling, then apply accessible component patterns to remediate the identified issues.

What is the best way to manage focus trapping in an accessible modal?

The best way to manage focus trapping in an accessible modal involves implementing strict focus order, visible focus states, and escape-to-close functionality to ensure keyboard operability for screen reader users.

How do I use ARIA roles and live regions for screen reader announcements?

To use ARIA for screen reader announcements, apply clear role, state, and property usage to interactive widgets and live regions to support assistive technologies with proper semantic structure.

Does mobile accessibility require specific touch target sizing for WCAG 2.2?

Yes, mobile accessibility requires specific touch target sizing to meet WCAG 2.2 Level AA and AAA target-size considerations, alongside platform support concepts for VoiceOver and TalkBack screen readers.

Can I fix broken keyboard navigation without breaking existing screen reader semantics?

You can fix broken keyboard navigation by implementing skip-to-content navigation and visible focus states while maintaining correct ARIA relationships and semantic HTML structure for screen reader support.