Development with accessibility in mind Q&A
summary
Visual Studio reports moving from basic compliance to usable accessibility by adding an integrated accessibility checker (powered by the Accessibility Insights engine) and testing with real users, plus features like AI code suggestions and audio cues that cut repetitive keystrokes. Teams report saving 600–800 ms per workflow step (scaling to hundreds of thousands of dollars per week at enterprise scale). Emphasis is on configurability and including people with disabilities in design and testing.
AI-written summary · about
chapters (13)
- 0:00Accessibility development intro
- 1:57Accessibility in enterprise workflows
- 3:45Accessibility and inclusivity defined
- 8:01Accessibility features impact
- 9:24Developer’s accessibility experience
- 16:14Balancing accessibility needs
- 19:31Designing for real usability
- 25:19Neurodiversity tools and strategies
- 30:04Visual Studio accessibility tools
- 31:52Gaining org buy-in for accessibility
- 38:15Integrating accessibility in dev
- 41:28Customer feedback on accessibility
- 44:19Closing remarks
related talks
48mProgramming for Accessibility
49mProgramming for Accessibility
54mLean accessibility: Building inclusive design into your agile workflow
48mProgramming for accessibility
57mHow (and why) to 'shift-left' your accessibility testing
12mAccessibility-First Development: Making Applications Inclusive from Day One
48mProgramming for Accessibility
01h 02mAccessibility - how to get the job done in a highly collaborative manner