Beyond the Screen: A Deep Dive into Linux Accessibility for Developers
summary
Demo code and slides live on GitHub and show concrete fixes: GTK4 emits focus events into the AT-SPI tree, Orca reads them via the Orca screen reader, and adding accessibility attributes fixes the common no labels on buttons smell. Live demos expose focus traps, keyboard-only “divorce” of toolbars, and the terminal paradox where line‑oriented TUIs lose structure. Advice includes a 30‑second keyboard test, using the exerciser/docktail to inspect the accessibility tree, and treating AI as an aid not a replacement.
AI-written summary · about
chapters (10)
- 0:00Linux accessibility intro
- 3:11Visual vs screen reader users
- 7:31Screen readers and apps
- 8:58Accessibility smells
- 13:16Live demo: accessibility issues
- 16:33Terminal accessibility limits
- 18:23AI vs accessibility
- 20:13Testing tools & keyboard test
- 21:18Accessibility core requirement
- 23:02Q&A
related talks
31mDeveloping for Everyone
21mAccessibility 101: Getting started with assistive technology and product inclusion
29mProgramming for Accessibility
52mInclusive design challenges with UI widgets
53mDoing Responsive Right: Accessibility Lessons from the Field
25mLove Thy Keyboard
23mI See: Overcoming Challenges in Software Development
31mThree Cheers for Keyboard Accessibility