Skip to content
Skills Library
Design & UX · Review & audit

accessible-design

/accessible-design

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.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Hard rules
  2. Gate
  3. Steps
  4. Checklist (copy into the reply and tick as you go)
  5. Examples
  6. Common issues
  7. References
  8. Next
Original SKILL.md headings · 78 lines, 802 words
SKILL.md preview
---
name: accessible-design
description: >
  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.
---

# 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

1. **Targets.** Measure hit areas, not visuals. Use [targets-and-contrast.md](references/targets-and-contrast.md).
2. **Contrast.** Compute ratios for text, icons, borders and focus rings, in each theme.
3. **Text scaling.** Check largest system size and browser zoom to 400 percent.
4. **Screen reader pass.** Name every control; set order; group; mark decorative images; announce state changes.
5. **Input alternatives.** Check one-finger, keyboard, switch and voice paths for each task.
6. **Motion and time.** Honour reduce motion; avoid flashing; allow extensions on time limits.
7. **Errors and help.** Identify the field, explain the fix; keep help in a consistent place (WCAG 3.2.6).
8. **Report** what passed, failed and was not tested, with the criterion for each.

## Checklist (copy into the reply and tick as you go)

```text
- [ ] 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 listed
```

## Examples

**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](references/targets-and-contrast.md): target sizes, contrast values and WCAG 2.2 mobile criteria.

## Next

[ux-review-and-testing](../ux-review-and-testing/SKILL.md) to run the checks with real users.
Files in this package (2)
  • SKILL.md 5 KB
  • references/targets-and-contrast.md 3 KB

Versions

The database has no other skills named accessible-design.

Database snapshot: 13.11.2026 · package version d61807582754 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100accessibility
    Use when building or reviewing UI for accessibility — screen readers (VoiceOver, TalkBack), keyboard and focus, colour contrast, Dynamic Type and text scaling, reduced motion, touch targets, accessible forms, captions — or when auditing against WCAG 2.2, the European…
  • 100accessibility
    Audit and fix Flutter accessibility - screen reader labels and semantics, tap target sizes, text scaling, contrast, focus order and keyboard navigation - and add automated accessibility tests. Use when the user asks about accessibility, TalkBack, VoiceOver, large text, or an accessibility review.
  • 100include
    Design for everyone by treating accessibility as a first-class design discipline, not a compliance checklist. Part of the Intent design strategy system. Covers WCAG 2.2 for designers, screen reader experience design, keyboard navigation, cognitive accessibility, motor…
  • 90accessibility-design
    The WCAG 2.2 AA audit cookbook for Laravel front-ends and mobile — concrete thresholds (contrast, target size, focus), Livewire / Inertia focus-management specifics, screen-reader semantics, reduced motion, mobile a11y (VoiceOver / TalkBack, dynamic type). Use when designing…
  • 100accessibility-audit
    Audit UI code for WCAG 2.1 AA compliance — semantics, keyboard navigation, color contrast, and ARIA. Use when auditing accessibility or the user mentions a11y, screen readers, WCAG, or keyboard support. For visual/design quality use /design-review instead.
  • 100accessible-by-default
    Non-negotiable accessibility baseline for any UI an agent builds or restyles: WCAG 2.2 AA contrast, visible focus, 24x24 target size, reduced motion, semantic HTML, text alternatives, and never relying on color alone. Includes a pass/fail checklist and code patterns. Use this…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.