accessible-design
Skill0 starsChanged 22 days agoMITView on GitHub
Use when checking or designing for accessibility on mobile, tablet or desktop: touch target size, contrast, text scaling, screen readers (VoiceOver, TalkBack), keyboard and switch use, reduce motion, WCAG 2.2 criteria, or an accessibility checklist for a design. Do not use for general visual styling (visual-design-system), legal compliance claims, or writing accessibility code for a framework.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KMaruthi2002/universal-llm-skills★ 1same name
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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adaptive-layout-and-spacingSkill
- ai-interface-designSkill
- interaction-feedback-and-formsSkill
- mobile-ux-foundationsSkill
- navigation-and-flowsSkill
- ui-ux-designerSkill
- ux-documentation-and-handoffSkill
- ux-review-and-testingSkill
- visual-design-systemSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 21
Every control has a name, role and state a screen reader can announce.
- Distinctive: line 22
Do not rely on gestures, drags or multi-finger input alone.
- Distinctive: line 24
Never use colour, sound, haptics or motion as the only signal.
- Distinctive: line 42
Text scaling: Check largest system size and browser zoom to 400 percent.
- Distinctive: line 44
Input alternatives: Check one-finger, keyboard, switch and voice paths for each task.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accessible Design
Stance: frozen are WCAG 2.2 AA as the floor, platform minimums for touch, and no information carried by one sense only. Flexible are how each requirement is met in a given design.
Hard rules
- Touch targets: 44 x 44 pt on iOS (28 pt hard minimum), 48 x 48 dp on Android and the web, 8 dp apart; WCAG 2.2 AA floor is 24 x 24 CSS px or 24 px of spacing. Mechanism: small or crowded targets cause mis-taps and exclude people with tremor; the visible icon may be smaller if the hit area is padded.
- Contrast 4.5:1 for text and 3:1 for large text and meaningful controls (WCAG 1.4.3, 1.4.11). Mechanism: low contrast fails low vision and glare.
- Text must scale to large sizes and reflow at 320 CSS px without clipping (WCAG 1.4.4, 1.4.10). Mechanism: fixed-height boxes cut off enlarged text.
- Every control has a name, role and state a screen reader can announce; reading order follows visual order. Mechanism: unlabeled icon buttons are silent or read as "button".
- Do not rely on gestures, drags or multi-finger input alone; give a single-tap or button path (WCAG 2.5.7). Mechanism: switch, voice and keyboard users cannot perform them.
- Focus is always visible and not hidden behind sticky bars (WCAG 2.4.11). Mechanism: keyboard and switch users lose their place.
- Never use colour, sound, haptics or motion as the only signal. Mechanism: each fails for some users; pair them.
- Sign-in must not demand memory tests, puzzles or transcription without alternatives (WCAG 3.3.8). Mechanism: cognitive load blocks access; allow paste, password managers and passkeys.
- State accessibility claims as "meets criterion X at level AA" with the check made; never "fully accessible" or "compliant". Mechanism: conformance needs scope and evidence.
- Act only on what the user asked. Before answering or changing anything, open the relevant files and check what is already done; report only what you checked, never guess, and do not redo finished work. Reason: guesses and repeated work waste the user's credit.
Gate
| Situation | Action |
| Quick design check | Run the checklist; mark untested items |
| Formal audit requested | Say what an automated and manual check cover; recommend testing with disabled users; no compliance claim |
| A hard-to-hit control needed (dense map pins) | Treat as the "essential" exception; offer an alternative way |
| Request to drop a requirement for looks | Offer a design that keeps the requirement (padded hit area, darker shade) |
Steps
- Targets. Measure hit areas, not visuals. Use targets-and-contrast.md.
- Contrast. Compute ratios for text, icons, borders and focus rings, in each theme.
- Text scaling. Check largest system size and browser zoom to 400 percent.
- Screen reader pass. Name every control; set order; group; mark decorative images; announce state changes.
- Input alternatives. Check one-finger, keyboard, switch and voice paths for each task.
- Motion and time. Honour reduce motion; avoid flashing; allow extensions on time limits.
- Errors and help. Identify the field, explain the fix; keep help in a consistent place (WCAG 3.2.6).
- Report what passed, failed and was not tested, with the criterion for each.
Checklist (copy into the reply and tick as you go)
- [ ] Targets sized and spaced per platform
- [ ] Contrast checked in each theme
- [ ] Largest text and 320 CSS px tested
- [ ] Names, roles, order set for a screen reader
- [ ] Single-pointer alternative for gestures and drags
- [ ] Visible focus, not obscured
- [ ] No signal carried by one sense only
- [ ] Authentication has an alternative
- [ ] Untested items listedExamples
Example 1: icon toolbar User says: "Check this toolbar of five 24 px icons for accessibility." Actions: measure hit areas; propose 48 dp padded areas with 8 dp gaps; require accessible names for each icon; check icon contrast at 3:1. Result: a list of failures with fixes and criterion numbers.
Example 2: ask for a certificate User says: "Tell me this app is WCAG compliant." Actions: decline a blanket claim; state which criteria were checked and how; list untested areas. Result: an honest scoped statement.
Common issues
- Icon buttons read as just "button". Cause: no accessible name. Fix: add a label matching the visible meaning.
- Large text breaks the layout. Cause: fixed heights. Fix: allow growth and wrap.
- Custom control invisible to a screen reader. Cause: no role or state exposed. Fix: use the platform control or expose role, name and value.
References
- targets-and-contrast.md: target sizes, contrast values and WCAG 2.2 mobile criteria.
Next
ux-review-and-testing to run the checks with real users.
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.

