accessibility-audit

1# Accessibility Audit Skill
2 
3This skill produces a structured accessibility audit based on WCAG 2.2 guidelines. It covers visual, motor, cognitive, and screen reader accessibility — with prioritised remediation for each issue found.
4 
5## Required Inputs
6 
7Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked *(assumed, confirm)* and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).
8- **What is being audited** (screen, component, full product, design spec)
9- **Description or image** of the UI
10- **Target WCAG level** (A / AA / AAA — default to AA, which is the legal standard in most jurisdictions)
11- **Known assistive technology users?** (Yes/No — if yes, which: screen reader / switch access / voice control / magnification)
12- **Platform** (Web / iOS / Android / Desktop app)
13 
14 
15## Programmatic Helper
16 
17Contrast ratios cannot be eyeballed. The AA line sits at 4.5:1, and `#777777`
18on white is 4.478 (fails) while `#767676` is 4.54 (passes) — no amount of
19looking at a screenshot separates those. Compute them:
20 
21```bash
22npx --yes notugly fix "#8ab4f8" "#ffffff"     # ratio, APCA, and the nearest passing colour
23npx --yes notugly onepager <url> --out review.html   # every pairing, printable
24npx --yes notugly vision                      # which colours merge for colour-blind viewers
25```
26…