~/talk

How to use Chrome DevTools to improve accessibility of your webpage

links:none on file
slides:none on file

Shows how to use Chrome DevTools to find and fix real accessibility bugs: emulate vision deficiencies and spot color-blind failures, get a suggested replacement color from the contrast checker, use CSS Overview to list all page colors and click-to-jump to contrast failures, view the full page accessibility tree to find missing labels, alt text, and divs masquerading as buttons, and toggle prefers-reduced-motion or use the Animations panel to pause long effects. Runs a Lighthouse accessibility audit (score 0–100) and notes automated tools catch ~57% of issues, so pair with manual testing.

AI-written summary · about

  1. 0:00Introduction
  2. 3:48Golden fish accessibility demo
  3. 10:41Chrome DevTools accessibility checks
  4. 18:20Fixing color contrast
  5. 21:54Screen reader testing
  6. 28:20Semantic HTML and keyboard navigation
  7. 30:31Reducing motion
  8. 35:10Debugging animations
  9. 36:16Lighthouse accessibility audit
  10. 39:08Manual testing
  11. 41:18Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.