Get Accessibility Right: Shift It Left!
summary
Tests of two train sites show one is unusable by keyboard while Trenitalia becomes purchasable in March, the other never exposes focus; a weather site forces 27 announcements before weather when used with a screen reader. Annual analysis of a million homepages finds simple, common failures: low text contrast, missing alt text, empty links, missing labels and language. Practical checklist: use semantic HTML, visible focus, skip links, interview users with disabilities, and include accessibility in requirements, QA and training.
AI-written summary · about
chapters (9)
- 0:00Introduction and setup
- 1:51Weather site accessibility failure
- 5:52Train ticket website barriers
- 8:04Accessibility as inclusive design
- 9:08Shift accessibility left in projects
- 12:04Team roles in accessibility
- 16:05Developer checklist for accessibility
- 17:53Why accessibility matters
- 20:30Q&A session
related talks
40mAccessibility, what, why and how?
41mTales of Accessibility Failures
38mAssistive Technologies as Tools for Accessibility Testing
25mPrevent, Catch and Fix Accessibility Issues
43mWhat is accessibility, and why I should care?
25mReal Life Accessibility: Have you HEARD your site?
27mAccessibility, what do you eat that with?
31mHow to Program with Accessibility in Mind