Accessibility‑Driven Automation: Bringing Inclusive Design into Windows Package...
summary
Shows concrete, repeatable fixes: replace Write-Host with Write-Output so screen readers and logs capture structured objects, emit JSON structured logs for parsers and monitoring, and lint Markdown for headings and alt text before publishing. Demonstrates tooling and checks — Chocolatey packages, PowerShell scripts, Wave and Axe scans, NVDA for verification — and adds accessibility gates into CI/CD so pipelines can fail on missing alt text or poor contrast. Claims measurable wins: faster troubleshooting and more reliable deployments.
AI-written summary · about
chapters (9)
- 0:00Accessibility-driven automation intro
- 1:22Why accessibility matters
- 7:33Accessibility in DevOps
- 12:02Accessible PowerShell scripting
- 17:33Automating accessibility checks
- 21:45Accessibility pitfalls
- 24:16Accessibility improvements case study
- 26:50Key takeaways
- 34:17Q&A
related talks
49mProgramming for Accessibility
29mProgramming for Accessibility
56mAccessibility Testing 101
53mAutomating Accessibility Assurance
35mBuilding an accessibility testing habit
48mProgramming for Accessibility
21mAccessibility 101: Getting started with assistive technology and product inclusion
45mDevelopment with accessibility in mind Q&A