Accessibility — What Do You Eat That With?
summary
An automated audit of roughly one million web pages found that automated tools detect only about 25% of accessibility issues, with an average of 56.6 errors per page and 97% of pages having at least one error. The talk calls for concrete fixes: use semantic HTML instead of divs-as-buttons, correct tabindex and heading use, preserve visible focus outlines, enforce color-contrast ratios, provide captions and transcripts, disable autoplay, and perform manual testing with assistive technologies such as ChromeVox and Windows Narrator.
AI-written summary · about
chapters (10)
- 0:00Accessibility intro
- 3:32Definition and importance
- 7:24Tech limits experiences
- 13:50HTML semantics navigation
- 16:41Keyboard focus
- 19:26Color contrast legibility
- 21:54Clear language content
- 23:41Accessible multimedia
- 24:47Manual testing tools
- 25:53Universal benefits
related talks
40mAccessibility, what, why and how?
25mPrevent, Catch and Fix Accessibility Issues
21mPrevent, Catch and Fix Accessibility Issues
50mAccessibility by Everyone (and for Everyone)
50mAccessibility by Everyone (and for Everyone)
41mAccessibility is a Requirement
54mAccessibility by everyone (and for everyone)
49mLost in Translation
