Decoding web accessibility through testing
summary
Shows that simple manual tests catch the bulk of problems while automated scanners find only about 30–40% of issues. Demonstrates repros and fixes: remove harmful CSS like outline:none, add missing alt text, replace tabindex hacks with semantic HTML, and label form fields with for+id. Uses concrete tools: Chrome DevTools accessibility pane, Lighthouse (axe), the axe extension and Accessibility Insights for Web. Covers screen reader checks with NVDA and VoiceOver and using ARIA live regions to announce dynamic changes, plus step‑by‑step checks you can run now.
AI-written summary · about
chapters (7)
- 0:00Web accessibility intro
- 1:24What is accessibility
- 3:54Keyboard navigation testing
- 10:25Browser tools for testing
- 16:52Screen reader testing
- 24:13Summary
- 25:00Q&A








