This Talk Has Been Disabled
summary
Claims that 15–20% of people have disabilities, that guidelines alone are enough, or that UX examples prove accessibility get tested here with specifics: a linked GitHub repository and QR code for sources, use of the Axecore accessibility testing library, Color Oracle and NVDA, the Ninth Circuit Domino’s accessibility ruling, 547 security alerts in a team exercise, 8–10% colorblind failure rates, and hacked Medronic Minimemed pumps via open APS showing what broke and what fixes actually work.
AI-written summary · about
chapters (19)
- 0:00Reenabling this talk
- 1:05Introduction
- 2:28Disability and accessibility models
- 7:04Accessibility in tech design
- 8:08Bad vs good web design
- 11:18Accessibility guidelines and tools
- 16:13Atlassian Confluence failure
- 19:43Domino’s Pizza lawsuit lessons
- 23:56Screen reader testing methods
- 25:00Geocities design pitfalls
- 26:45Epilepsy and design risks
- 29:15League of Legends colorblind issue
- 33:09White House sign language lawsuit
- 34:11Accurate captioning importance
- 37:19Artificial pancreas security flaw
- 39:30Medical device security overlap
- 41:16Speaker’s ironic venue experience
- 43:26Conference venue accessibility
- 44:07Recap and benefits
related talks
53mThe Human Side of Accessibility
56mAccessibility Testing 101
41mAccessibility is a Requirement
56mAccessibility for UX: Don't worry, it's much worse than you think
44mTesting Web Accessibility
25mBuilding empathy and accessible apps
41mTales of Accessibility Failures
45mTips from the Trenches: Accessibility Testing