Discussion Panel: Accessible Technology
summary
A panel recounts concrete accessibility facts: a talking calculator from 1977 and VoiceOver since 2004, recommendation to read HTML/ARIA specs for specific widgets, and use axe browser extensions for in-page checks. Instagram’s web UI remains unusable for months — one incident stretches to eight months before fixes — while Apple’s site rates highly for shopping flows. Concrete fixes: label every control, provide image text, prefer semantic HTML over ARIA, and expect a potential 15–30% audience uplift.
AI-written summary · about
chapters (17)
- 0:00Introduction to panel
- 0:23Earliest accessible tech
- 1:24Blindfold simulation experience
- 3:51Best accessibility resources
- 6:40Tools for browsing the internet
- 8:26Fixing inaccessible apps
- 10:29Instagram accessibility failure
- 11:14Justifying accessibility to managers
- 13:21Accessibility benefits everyone
- 14:43Blind community size and challenges
- 15:24Making accessibility fun
- 19:16Solving accessibility problems
- 20:21Blind community communication
- 21:48Mainstreaming and community rejection
- 22:51Most accessible website
- 23:14Accessibility vs JavaScript speed
- 25:29Closing remarks
related talks
59mAccessibility in UX: A panel discussion
21mAccessibility 101: Getting started with assistive technology and product inclusion
45mA Glimpse Into Accessibility
01h 07mA web for anyone, anywhere, anytime
40mAccess to Tech, Tech to Live
33mAccessibility Done Right
37mAccessibility Matters: Creating a Better Web
26mAccessibility Is a Marathon, not a Sprint