a11y
Skill2 starsChanged 4 months agoMITView on GitHub
Audit the UI for accessibility problems — missing labels, alt text, contrast, keyboard traps, ARIA misuse, semantic structure — and fix them against WCAG. Use when the user says "check accessibility", "audit a11y", "is this accessible", "fix accessibility issues", "add aria labels", "screen reader support", or "WCAG compliance".
11 other projects use a version of this.
Adopted by
Most recently taken up by
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
- gbvillarinho/react-design-skillstheir own version, first seen Oct 20, 2026
- pengGgxp/skillstheir own version, first seen Oct 11, 2026
- BeyondTheProtocol/polaristheir own version, first seen Sep 25, 2026
- Surfrrosa/claude-skillstheir own version, first seen Jun 25, 2026
- ariadoss/superskillstheir own version, first seen Jun 21, 2026
Used with
Projects with it also use verify.
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.
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- BeyondTheProtocol/polaris★ 47same name
- bmarshall511/forexflow★ 14same name
- ariadoss/superskills★ 12same name
- launch52-ai/flutter-template★ 2same name
- Buddhilive/buddhi-cli★ 1same name
- pengGgxp/skills★ 1same name
- Surfrrosa/claude-skills★ 1same name
- CorentinGC/claude-skills★ 0same name
- gbvillarinho/react-design-skills★ 0same name
- Nadav011/apex-skills★ 0same name
1 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 repository68 other files it gives its agents.
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
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 31
Read the components and identify real violations with file:line.
- Distinctive: line 37
Prefer native semantic HTML over ARIA.
- Distinctive: line 38
Don't change visual design or behavior beyond what the fix requires.
“Common” is measured: kept by at least 6 in 10 of the 9 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
UI surface & tooling
!grep -rilE "react|vue|svelte|angular|<template|\.tsx|jsx" package.json 2>/dev/null | head
!ls node_modules/.bin/axe node_modules/.bin/eslint 2>/dev/null && grep -rl "jsx-a11y\|eslint-plugin-vuejs-accessibility" package.json .eslintrc* eslint.config.* 2>/dev/null | head
Instructions
Audit the UI in $ARGUMENTS (or the main components if none given) for accessibility issues and fix the clear ones. Anchor findings to WCAG 2.1 AA.
What to check
- Text alternatives —
<img>withoutalt(and decorative images that should havealt=""), icon-only buttons/links with no accessible name,<svg>without a title/aria-label. - Semantic structure — real headings in order (no skipped levels), landmarks (
main/nav/header), lists for lists,<button>vs<a>used for the right job (action vs navigation) instead of clickable<div>s. - Forms — every input has an associated
<label>(oraria-label/aria-labelledby), required/invalid states exposed (aria-invalid,aria-describedbyfor errors), grouped controls in<fieldset>/<legend>. - Keyboard & focus — everything interactive is reachable and operable by keyboard, no
tabindex > 0, visible focus styles, focus is managed for modals/menus (trap while open, restore on close), no keyboard traps. - ARIA correctness — prefer native elements over ARIA; where ARIA is used, roles/states are valid and not contradicting native semantics (the first rule of ARIA: don't use ARIA if a native element works).
- Color & contrast — text/background contrast meets AA (4.5:1 normal, 3:1 large); meaning not conveyed by color alone.
- Media & motion — captions/transcripts for media, and respect
prefers-reduced-motionfor animations.
Method
- Read the components and identify real violations with
file:line. Use an automated checker (axe,eslint-plugin-jsx-a11y) if configured — but automation catches ~a third of issues, so reason through the rest by reading the markup and interaction. - Fix the unambiguous issues (missing
alt, unlabeled inputs,divthat should be abutton, missing focus management) preserving behavior and styling. - Flag judgment calls rather than guessing — contrast that needs a design decision, alt text whose correct wording depends on intent, an interaction pattern that needs rework.
Rules
- Prefer native semantic HTML over ARIA; only add ARIA when no native element expresses the semantics, and keep it valid.
- Don't change visual design or behavior beyond what the fix requires; surface contrast/wording decisions to the user instead of inventing them.
- Tie each finding to what it breaks for a real user (screen reader, keyboard-only, low vision) and the WCAG criterion — not just "best practice".
- Automated tools are a floor, not a ceiling — state that keyboard/screen-reader testing is still needed for anything you couldn't verify statically.
- Summarize: issues found by severity, what you fixed, and what needs a human decision or manual assistive-tech testing.
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.

