Accessible Means Hackable
summary
A programmer loses the ability to type in 2015 and learns to dictate code with Talon, customizing macros, a phonetic alphabet, an indexed clipboard and repeat commands. The narrative shows that Talon restores research productivity (PhD work, papers) but introduces vocal strain and requires private offices and time to learn. It also documents diabetic hackers creating closed-loop insulin systems by repurposing Medtronic pumps and the industry resistance despite recent FDA interoperability designations.
AI-written summary · about
chapters (15)
- 0:00Introduction to accessible means hackable
- 1:10My coding to voice journey
- 3:18Why hackable tools matter
- 7:12Talon voice coding system
- 9:18Blind programmers' setups
- 11:05Adaptive tech limits
- 16:24Profit vs accessibility
- 18:31Contempt for accessibility
- 19:54Patronizing attitudes
- 22:45Supporting disabled coders
- 24:27Hacker hand care
- 30:50Hand pain unbearable
- 33:00Living with chronic pain
- 36:51Disability adaptation myths
- 37:33Q&A
related talks
29mHello, computer. Writing Ruby with voice recognition
14mLook ma, no hands! - How to program without using your hands
39mWhat You Say is What You Get: Hands-Free Coding in 2022
21mBuilding for Disabled Power Users
44mHack for good: Accessibility testing with a Flipper Zero
43mDesktop Linux, without a keyboard, mouse or desk
12mIt’s skeuomorphin’ time!! The enduring physicality of braille!
50mAI as an A11y Ally
