The Future Should Be Uneven
summary
Argues for concrete steps: make accessibility cross-browser and bandwidth-aware, supply persistent customization so keyboards (Dvorak) and input preferences follow users, and expose a portable pseudonymous profile (uploader suggests an XML-like format) as an interoperable API. Notes existing attempts—Mozilla personas, Microsoft accessibility kits—and endorses hardware like the ultimate hacker keyboard for real-world benefit. Recommends a semantic abstraction layer so content is labeled by function (h1, procedure step) enabling alternate renderers, blocking, and workflow choices rather than fixed, one-size-fits-all pages.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:30The Future Should Be Uneven
- 1:04The dominating image
- 2:00The privileged user
- 3:02The internet is slow
- 4:48The Veil of Ignorance
- 6:54Paradox of Tolerance
- 8:32What would make it better
- 8:48Consistency
- 11:54Input Sources
- 12:47Persistent Customization
- 15:45Disabilities
- 17:04We get it wrong
- 17:25Fixed mindset
- 18:29Growth mindset
- 19:58Design for growth
- 21:44Empowerment
- 23:51Blocking
- 26:33Personal Optimization
- 27:46Conclusion
related talks
40mAccessibility: What If We Let Users Customize ...
26mAccessibility Is a Marathon, not a Sprint
41mTechnologic (Human After All): Accessibility remix
26mMake the internet a better place - with coding for accessibility
39mStop to diss ability: the web is designed for all
49mThese 5 Changes Will Advance Inclusive Design
51mWhat Is The Future of Accessibility?
21mBuilding for Disabled Power Users