Hinting at a better web
summary
Claims that most sites load 5.8 MB average page and that automated scans find accessibility failures on roughly 85% of homepages back the urgency. Demonstrations use Lighthouse, the browser extension Accessibility Insights with Fastpass and assessment workflows, and a CLI workflow via npx hint example.com that fails builds on policy violations. Concrete fixes include adding alt text, proper labels, reducing oversized images and baking audits into editors and CI so problems are prevented, not just reported.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:10Happy 30th birthday, World Wide Web!
- 6:53World Wide Mess
- 9:35The web is made for humans...
- 12:59The web is an accessibility mess...
- 13:23Rampant accessibility failures...
- 15:01Basic things get forgotten...
- 16:21Even better - we concentrate on the wrong things...
- 20:45Let's take a breath and think web...
- 28:02So why don't we build great solutions?
- 29:00Web Developers need to know a lot...
- 30:57Browser tool audits...
- 31:20Accessibility Insights
- 34:52Adding experience to build processes...
related talks
35mExploring the Lighthouse
22mPrioritising Accessibility to Web Development
21mPrevent, Catch and Fix Accessibility Issues
56mContinuous Accessibility: Adding Lighthouse to Your CI/CD Pipeline
30mTesting Web Accessibility
40mAccessibility, what, why and how?
44mTesting Web Accessibility
56mAccessibility Testing 101