How to Catch Low-Hanging Accessibility Fruits while Developing
summary
Demonstrates concrete checks: runs axe DevTools in the browser and reports 49 issues (27 need review, 1 critical, 20 serious, 1 moderate), points out the critical meta viewport that disables zooming on mobile, shows keyboard-only navigation revealing missing skip to content links, keyboard traps and buttons built from divs that aren’t keyboard-activatable, and calls out auto-playing motion with no reduced-motion support — fixes are small but restore real usability.
AI-written summary · about
chapters (6)
- 0:00Intro
- 2:48Automated Testing Tools
- 8:26Navigating with Keyboard Only
- 15:36Questions
- 15:49Common Accessibility Issues
- 18:51How to Convince Your Team
related talks
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
41mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
31mDecoding web accessibility through testing
39mHow to win at mobile accessibility
25mPrevent, Catch and Fix Accessibility Issues
44mTesting Web Accessibility
41mTales of Accessibility Failures
21mPrevent, Catch and Fix Accessibility Issues