accessibility-passlisted

# accessibility-pass Check someone's live site against how people actually use the web: on bright screens, without a mouse, with screen readers, with imperfect vision. Most fixes are small; the skill is finding them systematically instead of assuming the site is fine because it looks fine to its author. ## Run the tools 1. Run a Lighthouse accessibility audit (Chrome DevTools, same panel as make-it-fast) on every page. It catches the machine-checkable layer: contrast failures, missing alt, missing labels, missing `lang`. Save the score as the "before". 2. axe DevTools, the free browser extension, on the worst page — it explains each finding better and catches things Lighthouse skips. One page is enough to learn the failure patterns. 3. The tools stop at what machines can check, so add two human tests: put the phone at arm's length in daylight and try to read it, and do the keyboard test below. ## Fix what turned up Work through findings with them making the calls; each fix is a one-line explanation. - Contrast: every flagged text/background pair gets checked in the WebAIM contrast checker and nudged until it passes 4.5:1 (3:1 for large text). They pick the new shade — darkening the text usually keeps the design intact. - Alt text: every meaningful image gets a description of what it shows, written by them, since they know why the image is there. Purely decorative images get `alt=""` so screen readers skip them. - Keyboard: unplug the mouse