Codex skills for Accessibility
Accessibility skills span web audits against WCAG 2.2, ARIA widget patterns, axe-core tests in CI, color contrast, native mobile screen readers and tagged PDFs. Codex reaches for native HTML before ARIA, reports every finding against its success criterion with evidence, and states what a scan cannot prove instead of quoting a Lighthouse score as an audit.
Start with these 3
- WCAG 2.2 Accessibility Audit Findings mapped to criteria, with fixes Codex runs a real accessibility audit instead of quoting a Lighthouse score: it scopes representative templates and journeys, scans every UI state with axe-core, then does keyboard, screen reader, zoom, contrast and form passes covering the new 2.2 criteria. Findings carry a success criterion, evidence, affected users and a code fix, and the report states what was not tested.
- Color Contrast Accessibility Measured ratios for every color pair you ship Codex inventories your color tokens, pairs each text and UI role with every surface it sits on in light and dark themes, and measures them with a bundled script that reports the WCAG ratio and APCA Lc. Failures get fixed once at the token level, and links, errors, charts and status badges gain a second cue so meaning never rides on hue alone.
- Mobile Accessibility Every core task, eyes closed, text at 200% Codex audits core user tasks with the screen reader and the largest text size rather than only running a scanner, then fixes semantics in the stack's own API: SwiftUI, UIKit, Compose, Views, React Native or Flutter. It groups cards into single focus stops with custom actions, enforces 44pt and 48dp targets, wires performAccessibilityAudit and Espresso checks into tests, and reports findings against WCAG 2.2.
11 more Accessibility skills
-
Accessibility Testing
axe in CI, humans for what axe cannot see -
PDF Accessibility
Tagged PDFs that pass PDF/UA and real readers -
ARIA Patterns
Widgets screen readers announce correctly -
Color Systems
Even OKLCH ramps, semantic roles, contrast that passes -
EPUB Ebooks
Ebooks that pass EPUBCheck the first time -
UI Copy and States
No blank screens, vague errors or mute buttons -
Game UI and Menus
Menus that work with a controller in hand -
Radix UI Primitives
Accessible behavior, your own styling -
AI Chat Interface
Chat UIs that stream, stop and recover cleanly -
Icon Systems
One icon family, crisp, themed and labelled -
Plain Language
Understood on the first read by anyone
General skills with Accessibility guidance
Not built around Accessibility, but they include steps or tools for it. Not part of the install-all command.
-
Storybook Stories
Stories that document and test every state -
SwiftUI Views
One owner per state, views that adapt -
Design Systems
A shared UI library teams actually adopt -
Form UX
Forms people finish on the first try -
Dark Mode Theming
Right theme on first paint, designed not inverted -
Design Handoff
Specs engineers can build without a meeting -
Responsive Design
Layouts that hold at every width, not three -
AppleScript and macOS Automation
Script Mac apps through dictionaries, not clicks
Every Accessibility skill in one command
Installs these 14 into ~/.agents/skills/. Add --project after -- to install into the current repository instead.
The installer is a 104-line POSIX shell script. It fetches the skills you name from codexskills.dev and unpacks each into its own folder in your skills directory. No sudo, no telemetry, and every skill page shows the full SKILL.md first. Read install.sh
curl -fsSL codexskills.dev/install.sh | sh -s -- wcag-accessibility-audit color-contrast-accessibility mobile-accessibility accessibility-testing pdf-accessibility aria-patterns color-systems epub-ebooks ui-copy-states game-ui radix-ui ai-chat-interface icon-systems plain-language Accessibility FAQ
Can Codex run a WCAG 2.2 accessibility audit?
WCAG 2.2 Accessibility Audit scopes representative templates and journeys, scans each UI state with axe-core, then does keyboard, screen reader, zoom, contrast and form passes, including the new 2.2 criteria such as 2.4.11 Focus Not Obscured and 2.5.8 Target Size. Each finding carries a success criterion, evidence, affected users and a code fix. The report states what was not tested, and conformance claims or a VPAT/ACR still need human confirmation.
Is there a Codex skill for adding axe-core accessibility tests to CI?
Accessibility Testing places axe-core where it catches defects: jest-axe or vitest-axe for shared components and @axe-core/playwright for page states after interaction. The CI gate blocks new serious and critical violations without failing legacy apps on old ones. It warns that a passing jsdom scan proves nothing about contrast or focus order, and pairs scans with a manual keyboard, screen reader and zoom pass.
Do these skills cover iOS and Android accessibility?
Mobile Accessibility audits core tasks with the screen reader and the largest text size, then fixes semantics in the stack's own API: SwiftUI, UIKit, Compose, Views, React Native or Flutter. It groups cards into single focus stops with custom actions, enforces 44pt and 48dp touch targets, and wires performAccessibilityAudit and Espresso checks into tests.
How do I install all 14 Accessibility skills at once?
Pass every name to the installer in one command: curl -fsSL https://codexskills.dev/install.sh | sh -s -- wcag-accessibility-audit color-contrast-accessibility mobile-accessibility accessibility-testing pdf-accessibility aria-patterns color-systems epub-ebooks ui-copy-states game-ui radix-ui ai-chat-interface icon-systems plain-language. Add --project right after -- to put them in the current repository's .agents/skills/ so your team gets them too.
Which Accessibility skill should I try first?
WCAG 2.2 Accessibility Audit is the closest fit for most Accessibility work. Mention it with $wcag-accessibility-audit in a prompt to load it on purpose; after that, Codex picks it up on its own whenever a task matches.