Accessibility Testing 101
summary
Claims that shifting accessibility testing left and involving people with disabilities catches most problems early, and that automated tools only find about 30–37% of issues. Demonstrates a GitHub repo with a good vs bad site identical visually example that both pass automated scans yet only the semantic version works with screen readers and keyboard. Runs specific tools: Chrome DevTools Lighthouse, Accessibility Insights, axe, WAVE, CCA plus NVDA/VoiceOver/TalkBack, Andy bookmarklets and W3C validator, and shows guided manual tests and pipeline checks.
AI-written summary · about
chapters (18)
- 0:00intro
- 0:27preamble
- 1:12agenda
- 1:30what is accessibility?
- 3:09what is accessibility - continued
- 8:25why make things accessible?
- 11:09how do we decide what is accessible?
- 17:37building accessibility test plans
- 29:00tools and resources: - built-in to browsers
- 32:32cca by tpgi
- 33:58microsoft accessibility insights
- 35:51browser extensions & web apps
- 39:28bookmarklets
- 40:38books (physical and ebook)
- 41:28additional resources
- 42:18corgi dev
- 42:57tools in action
- 55:37thank you!
