Accessibility for the Deaf / Hard of Hearing and Progress Over Perfection
summary
Examples show concrete fixes: change a form that requires a phone number to offer a text‑only option and force-choice between at least two contact methods; update scripts so support asks for “email or callback number” (Microsoft Disability Answer Desk does this); avoid parallax and give reduced‑motion toggles because vestibular issues affect ~10% of adults; use readable captions (off‑black background, off‑white text, no ALL CAPS) and supply transcripts; adopt AI note-takers that summarize meetings so a 9,000‑word hour transcript becomes actionable bullets.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:22Deafness spectrum assumptions
- 4:56Thinking in accessibility
- 7:31Communication options DHH
- 14:54Modern communication methods
- 17:18360-degree accessibility
- 19:44Vestibular disorders motion
- 23:22Motion color web design
- 25:53Non-sound notifications
- 27:44AI notetaking summaries
- 30:37Video meetings housekeeping
- 37:10Captions best practices
- 43:36Progress over perfection
- 46:26Universal design paradox
- 48:01Advocating TEACH method
- 50:34Early DHH involvement
- 53:27Q&A
related talks
52mAccessibility: Coding and Beyond
24mAccessibility is more than just supporting screenreaders
40mAccess to Tech, Tech to Live
22mAccessibility for Everyone
24mAccessibility Through the Eyes of a Deaf Professional
45mA Glimpse Into Accessibility
55mAccessibility and Aging in Tech
30mHear! An Accessibility Tale from a Hearing-Impaired Senior Software Engineer