a11y
Skill0 starsChanged 33 days agoMITView on GitHub
Accessibility guidance so everyone can use an interface: keyboard use, focus, color contrast, semantic HTML, ARIA, screen readers, forms, motion, touch targets and WCAG 2.2 AA. Use whenever the user asks for an accessibility audit or fix, mentions a11y, WCAG, screen readers, keyboard navigation, contrast or "acessibilidade", or is building interactive UI such as forms, menus, dialogs, tabs, dropdowns and custom components, even if they never say "accessibility". Use alongside `ui` and `ux`, because accessibility is easiest to get right while building.
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
- pengGgxp/skillstheir own version, first seen Oct 11, 2026
- BeyondTheProtocol/polaristheir own version, first seen Sep 25, 2026
- Pradnyeshp/Claude-Skillstheir own version, first seen Jul 6, 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
- Pradnyeshp/Claude-Skills★ 2same name
- Buddhilive/buddhi-cli★ 1same name
- pengGgxp/skills★ 1same name
- Surfrrosa/claude-skills★ 1same name
- CorentinGC/claude-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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Make it work with the keyboard: Every action reachable and operable, with a visible focus and a logical order.
- Distinctive: line 15
Check forms and messages: Read references/forms-and-feedback.md for inputs, errors, status updates and loading.
- Distinctive: line 22
Don't take control away: No keyboard traps, no autoplay that cannot be stopped, no time limits without a way to extend them.
- Distinctive: line 24
Report what you did not verify: If you could not run the page, a screen reader or a contrast tool, say so.
“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
Accessibility
An interface is only finished when people can use it without a mouse, without seeing color, with a screen reader, with large text, or with limited motor control. These are everyday conditions, not edge cases: temporary injuries, bright sunlight and a broken trackpad create them for everyone. The practical goal is WCAG 2.2 level AA, built in from the start because retrofitting it costs far more.
Process
- Start with the right element. Most accessibility comes from using the correct semantic HTML (
button,a,label,nav,main,h1-h6,ul,table). Custom elements need everything the native one gave for free. Read references/semantics-and-aria.md when building or reviewing structure and custom widgets. - Make it work with the keyboard. Every action reachable and operable, with a visible focus and a logical order. Read references/keyboard-and-focus.md for interactive pieces, dialogs, menus and flows.
- Check perception. Contrast, text size, color-only meaning, motion and zoom. Read references/visual-and-motion.md when choosing colors, type, charts, animation or media.
- Check forms and messages. Read references/forms-and-feedback.md for inputs, errors, status updates and loading.
- Run references/audit-checklist.md on your own output and fix failures. When asked for an audit, report findings by severity with the element, the problem, who it affects and the fix.
Principles
- Native first, ARIA second. The first rule of ARIA is to not use it when a native element exists. Wrong ARIA is worse than none.
- Don't rely on one sense. Color, sound, position or hover alone must never carry meaning.
- Don't take control away. No keyboard traps, no autoplay that cannot be stopped, no time limits without a way to extend them.
- Automated tools find about a third of the problems. Pair them with a keyboard pass and, when possible, a screen reader pass. Do not claim an interface is "fully accessible" from a tool score alone.
- Report what you did not verify. If you could not run the page, a screen reader or a contrast tool, say so.
Working with the other skills
ui chooses color, type and motion, and accessibility sets the floor: contrast, focus visibility and reduced motion override a visual preference. ux decides structure and flow, and accessibility makes that structure operable and announced correctly. copy and ux/references/writing.md supply clear labels, error text and link text, which screen reader users depend on.
Source
Numeric thresholds in the references were checked against the WCAG 2.2 text published by the W3C (https://www.w3.org/TR/WCAG22/) on 2026-10-07: contrast 4.5:1 and 3:1, non-text contrast 3:1, target size 24 by 24 CSS pixels, reflow at 320 CSS pixels, text resize at 200%, text spacing values, three flashes in one second, and pause controls after 5 seconds. When a legal requirement applies, confirm against the current standard and the applicable local law.
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.