JavaScript for accessible web applications
summary
Advocates progressive enhancement and server-side rendering with deferred JavaScript — Twitter cuts time to first tweet 1/5 by rendering first and running JS later. Gives two concrete practices: handle focus properly (use hashchange or click handlers, set tabindex="-1" and programmatically focus while often preventing default to avoid Chrome/Firefox quirks), and expose dynamic updates via live regions (use aria-live="polite"). Cites BBC Olympics fallback approach and zero complaints as proof it works.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:27Wide variety of user agents
- 9:38Is it difficult
- 10:50Progressive enhancement
- 13:03Twitter
- 22:17Nicholas Zakas
- 46:12JavaScript as a technology
related talks
41mYou Really Don't Need All That JavaScript I Promise
29mJavaScript for Everybody
28mJavaScript + Web Standards II: The Quickening
33mAccessibility and JS: side-by-side
21mYou Really Don't Need All That JavaScript, I Promise
30mAccessible.JS
34mWeb development isn't about you, dude
39mYou really don't need all that JavaScript, I promise
