claude-a11y-audit

Audit UI diffs for accessibility regressions and semantic issues.

228|68|Updated Sep 27, 2023
One-click install
npx skills add https://github.com/SwitchbackTech/compass-calendar --skill claude-a11y-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-a11y-audit
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.claude/skills/a11y-audit
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill claude-a11y-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits UI diffs to identify accessibility regressions, ensuring changes remain usable by all users and compliant with accessibility standards.

Core Features & Use Cases

  • Diff-first analysis: Reviews only changed lines and their context to surface issues.
  • Semantics and structure checks: Verifies correct use of headings, lists, landmarks, and native semantics.
  • Keyboard and focus audits: Ensures all interactive elements are reachable and operable via keyboard, with proper focus management.
  • ARIA and contrast validation: Checks aria usage, labels, roles, and contrast compliance for readability.
  • Remediation guidance: Proposes minimal, targeted fixes tied to specific diffs to maximize impact.
  • Testability recommendations: Suggests accessible queries and reliable tests to improve robustness.

Quick Start

Provide a UI diff and a sample page to audit, then generate actionable findings.

Frequently Asked Questions about claude-a11y-audit

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

FAQPage Schema
How do I check UI diffs for accessibility regressions?

To check UI diffs for accessibility regressions, provide the UI change feed and optional screenshots to analyze semantics, keyboard navigation, and ARIA correctness, generating targeted findings and minimal code fixes.

How do I audit keyboard navigation and focus management in a web interface?

Auditing keyboard navigation and focus management involves reviewing UI diffs to verify all interactive elements are reachable and operable via keyboard, ensuring proper focus management and suggesting accessible test queries.

Can I use a diff feed to validate ARIA correctness and contrast compliance?

Yes, you can use a diff feed to validate ARIA correctness and contrast compliance by analyzing changed lines and their context to check aria usage, labels, roles, and contrast for readability issues.

What is the best way to fix accessibility issues with minimal code changes?

The best way to fix accessibility issues with minimal code changes is to review UI diffs and apply remediation guidance that proposes targeted, minimal fixes tied to specific changed lines to maximize impact.

Do I need screenshots to perform an accessibility audit on changed UI lines?

Screenshots are optional for performing an accessibility audit; the core requirement is a UI diff feed and a set of accessibility checklists to generate findings, semantics checks, and testability recommendations.

Why does my accessibility audit only flag issues on changed lines?

Your accessibility audit flags issues on changed lines because it uses a diff-first analysis approach, reviewing only modified code and its surrounding context to surface semantic, keyboard, and ARIA regressions efficiently.