Stop what you are doing. You're breaking the web.
summary
Front-end failures are concrete: pages take 8.1 seconds to render readable text on Medium and 8.4 seconds for a single tweet unless stripped to a 4‑second plain HTML version; images loaded only by JavaScript can be missing on Wi‑Fi; interactive controls, links and keyboard access routinely become unresponsive; accessibility fixes include semantic HTML, ARIA roles and VoiceOver testing; gov.uk measures show 0.2% without JS and 0.9% JS‑capable but not executing; decide by these measured failures, payload size and whether features degrade gracefully.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:22Logging, testing, reporting
- 3:32Trying to do thing Can't do thing
- 14:07Keyboard and single switch access
- 14:35Captioning and transcripts
- 15:15Testing for accessibility
- 17:34Jargon, language and tone
- 29:35Nobody turns JavaScript off on purpose
- 31:091.1% didn't get JS enhancements
- 32:24Why doesn't my JavaScript run?
- 33:03Networks blocking JS access
- 34:17Not enough processing power
- 34:53Your CDN is down
- 35:24Single page web apps
- 38:22Should it work without JS?
- 40:18Know how to measure
- 40:39Learn about statistics
- 41:27Browser is a hostile environment
- 42:49What you make is what you stand for - David Hieatt
related talks
38mDear Developer, the Web Isn't About You
44mWeb Components Can't Save Us. But You Can!
42mBuilding quick apps in 2018
27mSlashing Performance Bottlenecks and Poor User Experience
23mPerformance Optimizations for Progressive Web Apps
58mWeb Panel
44mAdvancing the web without breaking it?
20mDon't Break The Web