Embracing Accessibility in Open source
summary
Open source projects miss accessibility for huge numbers: one billion people (15%), 285 million visual impairments and 466 million with hearing loss, so prioritizing WCAG/ATAG/UAAG and automated scanners is urgent. Practical fixes described include using Vinux, AutoHotkey and symbol sets, recruiting excluded contributors for design reviews, adding keyboard and low-bandwidth support, and enforcing accessibility as part of workflow. Case made that inclusive design increases outreach, sustainability and contributor diversity.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30About Anita
- 3:20Accessibility
- 14:05Open Source
- 18:20Outreach
- 26:19Accessibility Standards
- 33:09Accessibility in Software Engineering
- 34:09Recognizing Exclusion
- 42:06Open Source Assistive Tools
- 44:26Universality
- 44:57Questions
- 45:15Outro
related talks
12mAccessibility-First Development: Making Applications Inclusive from Day One
28mBuilding in accessibility for broader value to all
54mAccessibility by everyone (and for everyone)
36mThe Human Side of Accessibility
19mCommit to Change: How to Increase Accessibility in Your Favorite Open Source Projects
14mAccessible Accessibility
53mThe Human Side of Accessibility
25mBuilding empathy and accessible apps