!important
summary
Argues that code quality loses to time and budgets and shows concrete tools and findings: Accessibility Insights extension highlights tab order and missing alt text, webhint runs as an NPM CI check, Lighthouse audits report accessibility performance and SEO. Cites HTTP Archive numbers about heavy third‑party use and a 5.8MB median page weight, shows a tiny demo using JavaScript Set that provokes scale and safety critiques, and says fixes exist but often arrive only after painful rewrites.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:07Best practices need insight and context
- 4:57We all crave importance and recognition
- 8:30Happy accidents can happen...
- 19:59Accessibility Insights
- 37:21The web is a platform ripe for abuse.
- 39:49What can we do?
related talks
52mOverboard.js
44mAdvancing the web without breaking it?
35mJavaScript/Web tooling now and tomorrow
45mDid We(b Development) Lose the Right Direction?
33mAccessibility and JS: side-by-side
53mThe Unbearable Weight of Massive JavaScript
16mJavaScript & Metaperformance
43mWalking Down the A11Y Road - Lessons Learnt From...