GitHub Accessibility: Bridging the Disability Divide through Code Collaboration
summary
Five guiding principles (participation first; disabilities arise from barriers; remove barriers; tech can include or exclude; progress beats perfection) frame GitHub’s accessibility work and its claim that lowering barriers drives real participation. Practical moves: GitHub Copilot and a voice preview Hey GitHub are integrated with NVDA and VS Code (Copilot auto-suggests and inserts code; temporary copy‑paste workaround noted), and community projects like EyeMine (forked from OptiKey) let an eye‑gaze user produce mods, push commits to GitHub, and code successfully.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Principles of accessibility
- 13:15What is GitHub?
- 17:04GitHub accessibility pillars
- 19:43Generative AI and coding
- 27:13Developer spotlight: Becky
- 37:50Diving deeper into eye gaze
- 44:55Q&A and closing
related talks
49mEmpowering People with Disabilities Using GitHub Copilot
05mGitHub Accessibility Scanner
11mOpen Source Accessibility
19mCommit to Change: How to Increase Accessibility in Your Favorite Open Source Projects
49mProgramming for Accessibility
45mAccessible by default
30mHow to Accessibility if You’re Mostly Back-End
43mHow to make your application accessible (and keep it that way!)