Accessibility Testing: The Manual Parts
summary
Automated checkers (Wave, axe, Color Oracle) reliably flag ~30% caught by automated tools like missing alt attributes or contrast issues, but about manual tests for the remaining ~70% are necessary: semantic HTML and lang attributes, alt text as short contextual labels (≈125 chars, empty "" for decorative), keyboard tab order and visible focus, real screen‑reader passes, proper table markup, labeled form controls (avoid placeholders), cautious ARIA use (aria-label, aria-describedby), watch context changes and timing, target readability ~grade 6–8; overlay widgets (e.g., AccessiBe) don’t fix core issues and attract legal risk.
AI-written summary · about
chapters (9)
- 0:00Webinar introduction
- 4:44Accessibility fundamentals
- 8:57Automated vs manual testing
- 14:14Limitations of automation
- 20:30Key areas for manual testing
- 26:47Advanced manual testing
- 34:09Content and context testing
- 38:27Conclusion and best practices
- 44:46Q&A session
related talks
56mAccessibility Testing 101
31mDecoding web accessibility through testing
35mAutomated Accessibility Testing
27mAccessibility, what do you eat that with?
01h 05mAccessibility Testing 101
33mAutomated Accessibility Testing
41mAccessibility is a Requirement
48mCoding For Accessibility Best Practices from the Front Lines