Quick Start for Evaluating and Testing Web Accessibility
summary
Workshop lays out a repeatable evaluation flow: set scope and sample, use discovery tools to find issues, then inspect with DevTools to locate the failing HTML. Key tools include screen readers (JAWS ~54%, NVDA ~31%, VoiceOver iOS ~72%), automated site audits like Pope Tech, and the WAVE browser extension to bridge UX and code. Contrast requires many checks (hover/focus/graphics), zoom testing up to 400% zoom matters, alt text needs human judgment, ARIA can produce massive failures (examples over 1,300 issues).
AI-written summary · about
chapters (5)
- 0:00Start
- 12:06Screen reader testing
- 14:41Recommended screen readers for testing
- 32:16Images & Alternative Text
- 38:38Navigation & Interaction
related talks
01h 05mAccessibility Testing 101
56mAccessibility Testing 101
52mAccessibility Testing 101
35mBuilding an accessibility testing habit
31mDecoding web accessibility through testing
21mTesting A11y: Validating Web App Accessibility
44mTesting Web Accessibility
26mThe Ultimate Practical Guide to Accessibility Testing
