Individual skill

accessibility-auditor

Checks an interface against accessibility principles - keyboard navigation, semantic HTML, color contrast, labels, and screen-reader behavior. Use before shipping any user-facing UI, especially public-facing ones.

skills/ui-ux/accessibility-auditor/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Aug 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
design Derived category
design-interface Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 1,315 bytes
SKILL.mdcore · 2,912 bytes
examples/example.mddoc · 2,259 bytes

Read excerpt


## Purpose

Audit a UI implementation against core accessibility principles so it's usable by people relying on keyboard navigation, screen readers, or other assistive technology — not just usable with a mouse and full vision.

## When to Use

- Before shipping any user-facing UI, especially public-facing products.
- Reviewing a form, modal, or interactive component specifically.
- The user asks for an accessibility review/audit, or mentions WCAG/a11y compliance requirements.

## What to Analyze

1. **Semantic HTML** — using actual `<button>`, `<a>`, `<nav>`, `<form>`, heading levels (`<h1>`–`<h6>`) instead of generic `<div>`/`<span>` with click handlers or visual-only styling standing in for structure.
2. **Keyboard navigation** — every interactive element reachable and operable via keyboard alone (Tab, Enter/Space, Escape for dismissible elements), with a visible focus indicator.