Walking Down the A11Y Road - Lessons Learnt From...
summary
Work on KA Lite and Kolibri shows concrete fixes: add page language and distinct titles, use semantic HTML5 and ARIA landmarks, fix nested headings and keyboard focus, add descriptive alt and link text, and provide captions and transcripts for multimedia. Teams use Bootstrap, Vue.js and video.js, add an Sr-only layer and automated a11y tests early, and keep a Tools Repository and weekly accessibility pills. Expect tradeoffs: retrofit costs rise from ~1–3% to ~10%+, color-deficiency affects ~10% of users, and legal cases now number 250+.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:40Radina Matic
- 3:51Who benefits?
- 4:36People with disabilites?
- 5:29EVERYBODY
- 7:00Good for Business
- 7:45Don't put up fires
- 8:28Standards & Laws
- 10:18Accessibility mishaps make headlines (and courtrooms)
- 14:01Headings
- 14:44Keyboard navigation
- 17:33Links and Forms
- 20:34OFFER ALTERNATIVES
- 23:22Screenreader-only output
- 28:37A11y from the start
- 32:45How did we get here?
- 33:26A11Y Pills & Passion
- 35:46A11y Tools Repository
- 36:05Accessibility is
- 37:35Describing images - Tools
related talks
33mAccessibility Done Right
41mTales of Accessibility Failures
28mThe intentions were good
23mPractical A11Y for Web Apps
26mAccessibility Is a Marathon, not a Sprint
31mHow to Be an A11Y - Creating Accessible React Apps
01h 07mA web for anyone, anywhere, anytime
47mLessons learnt from building accessible complex web apps