Agent skill · Security

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

mturacgithub.com/mturacGitHub ↗
codexcopilotcursorMIT
Install
npx skills add mturac/everything-openai-codex --skill accessibility --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/accessibility/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 84
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Accessibility (WCAG 2.2) This skill ensures that digital interfaces are Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those using screen readers, switch controls, or keyboard navigation. It focuses on the technical implementation of WCAG 2.2 success criteria. ## When to Use - Defining UI component specifications for Web, iOS, or Android. - Auditing existing code for accessibility barriers or compliance gaps. - Implementing new WCAG 2.2 standards like Target Size (Minimum) and Focus Appearance. - Mapping high-level design requirements to technical attributes (ARIA roles, traits, hints). ## Core Concepts - **POUR Principles**: The foundation of WCAG (Perceivable, Operable, Understandable, Robust). - **Semantic Mapping**: Using native elements over generic containers to provide built-in accessibility. - **Accessibility Tree**: The representation of the UI that assistive technologies actually "read." - **Focus Management**: Controlling the order and visibility of the keyboard/screen reader cursor. - **Labeling & Hints**: Providing context through `aria-label`, `accessibilityLabel`, and `contentDescription`. ## How It Works ### Step 1: Identify the

What's inside
Steps it walks through
  1. When to Use
  2. Core Concepts
  3. How It Works
  4. Step 1: Identify the Component Role
  5. Step 2: Define Perceivable Attributes
  6. Step 3: Implement Operable Controls
  7. Step 4: Ensure Understandable Logic
  8. Step 5: Verify Robust Compatibility
  9. Accessibility Architecture Diagram
  10. Cross-Platform Mapping
  11. Examples
  12. Web: Accessible Search
  13. iOS: Accessible Action Button
  14. Android: Accessible Toggle
More from everything-openai-codex
All skills →
About this skill
What does the accessibility skill do?

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

How do I install it?

Run `npx skills add mturac/everything-openai-codex --skill accessibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going