a11y-audit
Skill227 starsChanged 50 days agoMITView on GitHub
Audits changed Compass UI for accessibility regressions in semantics, names, keyboard and focus behavior, ARIA, contrast, motion, and testability, then proposes minimal diff-scoped fixes. Use for UI diff reviews, accessibility audits, or flaky interaction tests.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- mayank2424/knacktheir own version, first seen Nov 15, 2026
- plugin87/ux-ui-agent-skillstheir own version, first seen Nov 10, 2026
- arcasilesgroup/ai-engineeringtheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- Aboudjem/ui-ux-suitetheir own version, first seen Nov 8, 2026
- kgelster/ecom-a11y-audittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use perf-audit, design-tokens and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
WhatIfWeDigDeeperSkillperf-audit
Profile and optimize React application performance
Also in 4 projects that use this
ilikescienceSkilldesign-tokens
Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.
Also in 4 projects that use this
Sagargupta16Skilldependency-audit
Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.
Also in 3 projects that use this
lbednerSkilli18n
Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 5 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 4 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- gitkraken/vscode-gitlens★ 10ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- arcasilesgroup/ai-engineering★ 65same name
- helderberto/agent-skills★ 19same name
- Hassaan146/claude-skills★ 18same name
- renfei-design/Figma-AI-Bridge★ 16same name
- kgelster/ecom-a11y-audit★ 12same name
- Mozurok/fhorja.dev★ 10same name
- Aboudjem/ui-ux-suite★ 8same name
- scayver/marketing-skills★ 8same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- chaosSkill
- google-sync-debugSkill
- qa-test-stagingSkill
- shipSkill
- simplifySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Do not expand into an unrelated site-wide audit.
- Distinctive: line 48
Run the checklist below.
- Distinctive: line 64
Every interaction is keyboard reachable and operable.
- Distinctive: line 72
Use ARIA only where native semantics are insufficient.
- Distinctive: line 89
Test meaningful state and focus outcomes, not only element presence.
“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When
UI diff review, accessibility audit, or flaky interaction tests.
Steps
Workflow, then Checklist, scoped to the diff.
Output
Minimal diff-scoped findings and proposed fixes.
Pass
Changed UI reviewed; no site-wide unrelated audit.
Anti-patterns
Do not expand into an unrelated site-wide audit. See
anti-patterns.md.
Escalate
A WCAG judgment that needs a human, or a contrast issue that needs design.
Accessibility change audit
Audit the changed UI and its immediate context. Do not turn a diff review into an unrelated site-wide audit.
Workflow
- Identify changed elements, interactions, states, and styles.
- Exercise affected behavior with the browser tooling available to the current agent when static inspection cannot establish focus, keyboard, contrast, or motion behavior.
- Run the checklist below.
- Tie each finding to a changed line or behavior and propose the smallest durable fix.
- Recommend role/name queries and user-driven tests.
Checklist
Semantics and names
- Heading order and landmarks remain meaningful.
- Interactive elements use native buttons, links, inputs, lists, and tables.
- Inputs, icon controls, dialogs, and regions have accessible names.
- Helper/error text is connected with
aria-describedbywhen appropriate.
Keyboard and focus
- Every interaction is keyboard reachable and operable.
- Focus order follows DOM order; avoid positive
tabIndex. - Dialogs, menus, and popovers place, contain, and return focus correctly.
- Composite widgets implement the expected arrow, Home/End, Enter, Space, and Escape behavior.
ARIA and state
- Use ARIA only where native semantics are insufficient.
aria-expanded,aria-selected,aria-pressed,aria-controls, andaria-activedescendantreflect actual state and relationships.- Hidden/disabled content is not accidentally focusable.
- Live updates and errors are announced when users need them.
Visual behavior
- Text, controls, and focus indicators meet Compass's WCAG 2.2 AA target.
- Color is not the only state indicator.
- Motion respects reduced-motion preferences.
- Zoom, narrow layouts, and reflow do not hide essential controls.
Tests
- Query by role and accessible name rather than CSS or
data-*. - Drive interactions with
user-event. - Test meaningful state and focus outcomes, not only element presence.
- Reuse existing Playwright/axe checkpoints; add one only for a newly exposed representative state.
Read docs/development/testing-playbook.md#accessibility-testing before
changing axe configuration or adding browser checkpoints.
Output
Order findings by blocker, high, medium, then low:
[severity] path:line — problem and user impact
Fix: smallest durable change
Test: semantic assertion or user flow that protects itState when no findings are confirmed. Separate automation results from judgment-based observations and never claim automated checks establish full WCAG conformance.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

