Prevent, Catch and Fix Accessibility Issues
summary
Shows that 96.3% of top homepages have accessibility issues averaging ~50 errors each and 96.1% fall into six categories, with automated tools catching only ~35–40% of problems; demos use Lighthouse, axe, IBM Accessibility Checker, WebAIM contrast checker and Chrome DevTools accessibility tab to find a color contrast ratio as low as 1.22, missing alt text, empty links, unlabeled form fields and a custom tabs widget that needs ARIA plus keyboard patterns. 96.3%, ~50 errors per page, Lighthouse axe DevTools
AI-written summary · about
chapters (14)
- 0:00Accessibility introduction
- 3:33Disability stats and spending
- 5:39WCAG guidelines
- 6:42Common accessibility issues
- 7:48Automated testing tools
- 8:09Fixing color contrast
- 10:18Alt text best practices
- 12:23Empty link text
- 13:50Form input labels
- 14:54Empty button issues
- 16:18Document language
- 16:59ARIA attributes
- 19:28Bad ARIA risks
- 20:11Q&A
related talks
40mAccessibility, what, why and how?
25mPrevent, Catch and Fix Accessibility Issues
27mAccessibility — What Do You Eat That With?
50mAccessibility by Everyone (and for Everyone)
20mDon't Break The Web
37mMaking A Strong Case For Accessibility
41mAccessibility is a Requirement
52mEssential Accessibility Annotations for a Smoother Design to Development Handoff