Lean accessibility: Building inclusive design into your agile workflow
summary
Claims that accessibility and agile pair well with measurable business value and lower long‑term cost, backed by specifics: start with keyboard accessibility and images, automate checks into CI (Selenium/Jenkins), use the web developer toolbar and TDD for regressions, and build a pattern library (reusable accessible modal, error summary links) to avoid late rework. Statistics cited: 15% of users have disabilities and one project reports ~30% conversion lift after fixing keyboard and contrast issues.
AI-written summary · about
chapters (6)
- 0:00Start
- 28:47UX and Design leads
- 29:18The Hamburger Menu
- 35:40Usability testers
- 37:47Developers!
- 43:16QA testers
related talks
45mAccessibility at all stages
08m"Accessibility! Why should I care?"
12mAccessibility-First Development: Making Applications Inclusive from Day One
01h 02mAccessibility - how to get the job done in a highly collaborative manner
29mHow to bring accessibility into your teams
28mBuilding in accessibility for broader value to all
57mHow (and why) to 'shift-left' your accessibility testing
45mTips from the Trenches: Accessibility Testing