Lost in Translation
summary
Claims that semantic HTML, not visuals, fixes accessibility problems backed by data and examples: WebAIM’s Million finds low contrast on ~83% of homepages, missing alt on ~55%, empty links on >50%, missing labels on ~46%, empty buttons ~27%, missing lang ~22%, and pages with aria present average 70% more errors; automated scans flag 96.8% of sites. Practical fixes shown: replace divs with a real button with aria-expanded and aria-controls, use landmarks, headings and lang, test with Wave, Lighthouse, Accessibility Insights, devtools and VoiceOver.
AI-written summary · about
chapters (12)
- 0:00Start
- 10:27Designers know too little about HTML.
- 13:22We put too much trust and hope in ARIA
- 22:01Accessibility issues don't just come from what's visible in a design, but from what's not visible.
- 43:32Developers, prioritise HTML
- 44:36Learn who your users are and how they're using the web.
- 45:21Stop belittling HTML.
- 45:34Universities, schools, teachers, course coordinators, prioritise HTML!
- 46:06Rewrite your curriculums, they don't work.
- 47:38Use accessible HTML in your demos.
- 47:55Learn how to test your sites with automatic testing tools.
- 48:25Learn how to test your sites with the keyboard and screen readers.
related talks
57mLost in Translation
01h 01mA web for anyone, anywhere, anytime
40mAccessibility, what, why and how?
25mPrevent, Catch and Fix Accessibility Issues
01h 07mA web for anyone, anywhere, anytime
27mAccessibility — What Do You Eat That With?
50mAccessibility by Everyone (and for Everyone)
50mMaking a Strong Case for Accessibility