Are you including...?
summary
Claims a conservative one in seven people have disabilities and demonstrates concrete failures: a TripAdvisor demo exposes 339 links, no form fields detected, a modal that appears visually but never receives focus, and unusable date pickers so booking fails. Tools shown are JAWS and VoiceOver; automated checks like wave.org and Chrome DevTools catch only ~20–40% of issues. Advice is specific: use semantic HTML not divs, implement skip-to-main and proper focus order, test with keyboard and real users, include WCAG A/AA requirements and VPATs in procurement and hiring.
AI-written summary · about
chapters (13)
- 0:00Start
- 13:12Web Content Accessibility Guidelines (WCAG)
- 14:06Cost of a Bug Fix
- 14:51Roles Designers Style
- 16:53Roles Designers Structure & Layout
- 18:22Roles Content Authors Copy
- 20:46Roles Developers Code
- 22:01Roles Developers Keyboard Checklist
- 23:13Roles Developers More Checks
- 24:42Roles Quality Assurance
- 25:32Roles Purchasing
- 26:04Roles Recruitment
- 27:07What can I do?
related talks
41mTales of Accessibility Failures
41mAccessibility is a Requirement
25mPrevent, Catch and Fix Accessibility Issues
56mAccessibility Testing 101
25mReal Life Accessibility: Have you HEARD your site?
53mLet's break some WCAG rules
46mYou Can Come to This Talk with Your Eyes Closed
37mAccessibility Matters: Creating a Better Web