Practical A11Y for Web Apps
summary
Argues that single‑page apps must behave like real pages and demonstrates concrete fixes: use Lighthouse and aXe in CI, inspect Chrome DevTools Accessibility panel, test with NVDA/VoiceOver and real blind users (ING runs user tests), and catch silly failures like an image alt that reads “cute dog.” Recommends native semantics over ARIA, use scroll to top, update document title, focus first element on route change, add landmarks and skip links, and use aria‑live for dynamic updates.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:40Accessibility
- 3:55Guidelines
- 5:00Perceivable
- 8:20Language
- 9:17Robust
- 10:45Routing
- 12:33Accessibility Testing
- 14:10Manual Testing
- 15:50Control with Keyboard
- 17:15Screen Reader
- 18:10Landmarks
- 19:53Test for Accessibility
- 20:15Why Aria
- 22:02Outro
related talks
45mA Web for Anyone, Anywhere, Anytime
01h 07mA web for anyone, anywhere, anytime
21mTesting A11y: Validating Web App Accessibility
31mHow to Be an A11Y - Creating Accessible React Apps
33mAccessibility Done Right
28mMaking Single Page Apps accessible
16mAccessibility Matters: How to Build Apps for Everyone
17mAccessibility in Single Page Applications