fixing-accessibility
Skill0 starsChanged 2 months agoMITView on GitHub
Audit and fix accessibility problems in web interfaces, including semantics, names, keyboard access, focus, forms, dialogs, status messages, contrast, zoom, and motion preferences. Use for explicit accessibility work or when implementing interactive web controls with material accessibility risk.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- ClaireAll/skillstheir own version, first seen Nov 5, 2026
- matheus-rib1108/meu-kit-claude-codetheir own version, first seen Nov 1, 2026
- robinbril/claude-code-harnesstheir own version, first seen Nov 1, 2026
- okfriansyah-moh/agentic-workflowtheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use fixing-motion-performance, ui-skills-root and 9 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.
kapishdimaSkillfixing-motion-performance
Fix animation performance issues.
Also in 7 projects that use this
Discriminative-shoji607Skillui-skills-root
Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.
Also in 3 projects that use this
Discriminative-shoji607Skillimprove-ui
Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.
Also in 3 projects that use this
studio-lgtmSkillmake-interfaces-feel-better
Apply design engineering best practices to polish UI components - use when reviewing or improving interfaces, animations, typography, or interaction details.
Also in 4 projects that use this
swyxioSkillmobile-native
Apply swyx's native mobile UX preferences when designing or critiquing iPhone/iPad flows, adapting tablet layouts, choosing communication-app notification behavior, or opening notifications/deep links/widgets/shortcuts before local content is ready. Also use for iOS/iPadOS generated build configuration, signing/install/launch problems, and device playtesting. Keep existing native or cross-platform stacks; excludes browser-only responsive work and backend-only changes without native UX or delivery implications.
Also in 3 projects that use this
wxyhgkSkillimprove-animations
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
Also in 4 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- ibelick/ui-skills★ 11ksame name
- agentset-ai/agentset★ 2.1ksame name
- kapishdima/soundcn★ 864same name
- kumaran-is/claude-code-onboarding★ 35same name
- podo/design-agent-skills★ 32same name
- master5d/claude-design-skills★ 26same name
- jscraik/Agent-Skills★ 9same name
- Discriminative-shoji607/ui-skills★ 3same name
- robinbril/claude-code-harness★ 3same name
- ClaireAll/skills★ 2same name
9 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 repository21 other files it gives its agents.
- global/AGENTS.mdAGENTS.md
- api-designSkill
- backend-patternsSkill
- brandSkill
- contract-firstSkill
- database-migrationsSkill
- engineering-task-workflowSkill
- error-handlingSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- intent-driven-developmentSkill
- react-native-patternsSkill
- react-patternsSkill
- react-testingSkill
- security-best-practicesSkill
- shadcnSkill
- supabase-postgres-best-practicesSkill
- systematic-debuggingSkill
- tdd-workflowSkill
- ui-ux-pro-maxSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Prefer native HTML semantics.
- Distinctive: line 18
Add a focused automated assertion when it can prevent regression.
- Distinctive: line 19
Verify with repository checks and a bounded manual keyboard review.
- Distinctive: line 23
Do not claim WCAG conformance from lint or component tests alone.
- Very specific: line 24
Do not add redundant roles, positive tabindex, or broad ARIA workarounds.
- Very specific: line 25
Use the separate native accessibility capability when it is installed and the target is React Native, iOS, or Android.
“Common” is measured: kept by at least 6 in 10 of the 18 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
Fixing Web Accessibility
Workflow
- Identify the affected user journey and the repository's existing accessibility tools.
- Reproduce the problem with semantic inspection and keyboard use before changing code.
- Prefer native HTML semantics; add ARIA only when native elements cannot express the interaction.
- Repair accessible names, relationships, focus order, visible focus, error association, live feedback, contrast, zoom/reflow, and reduced motion as applicable.
- Preserve behavior for pointer and touch users while adding keyboard and assistive-technology support.
- Add a focused automated assertion when it can prevent regression.
- Verify with repository checks and a bounded manual keyboard review. Report screen-reader or browser testing as skipped when it was not actually performed.
Boundaries
- Do not claim WCAG conformance from lint or component tests alone.
- Do not add redundant roles, positive
tabindex, or broad ARIA workarounds. - Use the separate native
accessibilitycapability when it is installed and the target is React Native, iOS, or Android.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

