Inclusive SRE: Best Practices for Working with a Visually Impaired Incident...
summary
Shows a live PowerShell terminal demo running git add/commit/push with a hardware security key, demonstrating how a screen reader announces prompts and command output; shows a 40‑cell braille display used to read and verify YAML playbook indentation in Visual Studio Code line by line; demonstrates fixing inaccessible tables by adding an explicit marker (exclamation) in the status column; recommends notifications and providing downloadable CSV/tabular data for graphs, and notes about color alone (≈10% of men are red‑green colorblind).
AI-written summary · about
chapters (13)
- 0:00Inclusive SRE practices
- 2:03Diverse perspectives in incident response
- 3:50Input and output methods
- 6:18Screen reader demo: terminal navigation
- 11:40Braille display demo: technical work
- 18:03Communications for visually impaired teams
- 21:32Avoid color-only dashboards
- 22:33Accessible server status tables
- 24:19Graphs for screen reader users
- 26:27Accessible data visualization
- 28:55Asking for accessibility guidance
- 30:25Inclusive SRE best practices summary
- 31:28Resources and closing
related talks
39mWhat visually impaired programmers are thinking about Ruby?
23mI See: Overcoming Challenges in Software Development
41mAccessibility‑Driven Automation: Bringing Inclusive Design into Windows Package...
49mProgramming for Accessibility
29mProgramming for Accessibility
35mBeyond the Screen: A Deep Dive into Linux Accessibility for Developers
45mA Glimpse Into Accessibility
05mFlying Blind - Accessibility in Monitoring