Codex-a11y-audit

Name: Codex-a11y-audit
Availability: InStock
Author: Switchback

Audit UI diffs for accessibility regressions and propose minimal fixes.

228|68|Updated Sep 27, 2023

Search Tags:#accessibility #a11y #ui-testing #diff-review #aria #keyboard-focus #test-selector

Ready to run

npx skills add https://github.com/SwitchbackTech/compass-calendar --skill codex-a11y-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Codex-a11y-audit
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.agents/skills/a11y-audit
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill codex-a11y-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit UI changes for accessibility regressions and missing improvements, and propose minimal fixes tied to the diff.

Core Features & Use Cases

Semantics, keyboard accessibility, ARIA correctness, and focus management audits tied to UI diffs.
Propose minimal, verifiable fixes mapped to specific changed lines, with role-based test selector recommendations.
Real-world Use Case: review a PR changing a modal or dynamic content and ensure tests remain robust.

Quick Start

Provide a concise accessibility audit for the latest UI diff and return prioritized issues with minimal fixes.

Frequently Asked Questions about Codex-a11y-audit

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

FAQPage Schema

How do I audit UI diffs for accessibility regressions?▼

To audit UI diffs for accessibility regressions, provide the latest UI changes to receive a prioritized list of issues. The analysis identifies semantic, ARIA, and keyboard navigation problems tied to specific changed lines, proposing minimal, verifiable fixes mapped directly to the diff.

How do I fix flaky UI tests related to dynamic content and ARIA roles?▼

Fix flaky UI tests related to dynamic content and ARIA roles by applying role-based test selector recommendations. The audit analyzes test flakiness caused by dynamic UI changes and suggests robust selectors that preserve safe, standards-compliant changes while improving test stability.

Can I review a PR changing a modal for keyboard focus and ARIA correctness?▼

Yes, you can review a PR changing a modal for keyboard focus and ARIA correctness. The audit specifically evaluates focus management, ARIA roles, and semantics within the UI diff, ensuring dynamic content like modals meets accessibility standards without breaking existing tests.

What is the best way to ensure new UI changes meet accessibility standards?▼

The best way to ensure new UI changes meet accessibility standards is through diff-first analysis. This approach targets semantic changes, keyboard navigation, contrast, and testability, generating actionable fixes and role-based test selectors while preserving safe, standards-compliant modifications.

Are there limitations to diff-first accessibility analysis for contrast and semantics?▼

Diff-first accessibility analysis for contrast and semantics is limited to evaluating changed lines within the provided UI diff. It does not audit the entire application codebase, but rather focuses on proposing minimal fixes for regressions introduced by the specific new UI changes.

Why do my dynamic UI changes break keyboard navigation and focus management?▼

Dynamic UI changes break keyboard navigation and focus management when they alter semantics without proper ARIA updates. The audit identifies these regressions in the diff and proposes minimal fixes to restore correct focus order and keyboard accessibility.