Accessibility, what do you eat that with?
summary
Explains which concrete problems to fix and how to test them: use semantic HTML, correct heading order, sensible tabindex and keyboard focus, preserve visible focus outlines, ensure color contrast and captions, and run manual screen‑reader and keyboard tests. Cites measured scale of the problem — 69.6 errors per page average, 97.8% of pages had errors — and notes headings misstructured in 300,000 pages so small HTML, CSS, and lab-testing changes produce large accessibility wins.
AI-written summary · about
chapters (12)
- 0:00Disability and accessibility intro
- 3:14Why accessibility matters
- 5:24Web accessibility failures
- 8:16Practical steps everyone
- 9:02Fixing HTML structure
- 14:44Keyboard navigation focus
- 16:53Color contrast accessibility
- 20:36Text readability best practices
- 22:47Media and dynamic content
- 24:37Testing accessibility
- 25:42Who benefits from accessibility
- 26:44Call to action inclusive design
related talks
40mAccessibility, what, why and how?
25mPrevent, Catch and Fix Accessibility Issues
48mCoding For Accessibility Best Practices from the Front Lines
01h 03mAccessibility Testing: The Manual Parts
21mPrevent, Catch and Fix Accessibility Issues
31mDecoding web accessibility through testing
41mAccessibility is a Requirement
54mAccessibility by everyone (and for everyone)