Prevent, Catch and Fix Accessibility Issues
summary
Concrete findings and hands‑on checks: the WebAIM Web‑million stats claim 96.8% of home pages have issues and an average of 50.8 errors per page, with most problems in six categories. Demos show using VoiceOver, the Chrome DevTools accessibility tab and an IBM checker to find missing alt text, empty links, absent form labels, focus styles, ARIA/name gaps and keyboard traps. Guidance explains which defects auto tests catch, which need manual exploration, and when ARIA is harmful versus required.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:35Understanding Digital Experiences
- 8:35Accessibility in the Software Development Life Cycle
- 11:12Missing Alternative Text Issues
- 12:26Visual Indicator Issues
- 18:23Keyboard Navigability
- 19:42Missing Document Language
- 22:15Missing ARIA Attributes
related talks
21mPrevent, Catch and Fix Accessibility Issues
40mAccessibility, what, why and how?
27mAccessibility — What Do You Eat That With?
27mAccessibility, what do you eat that with?
37mMaking A Strong Case For Accessibility
50mAccessibility by Everyone (and for Everyone)
41mAccessibility is a Requirement
33mWeb accessibility in practice, more than just WCAG