Accessibility with Vue
summary
Gives concrete counts — 2 million visually impaired, 11 million with hearing loss — and demonstrates actual tooling: JAWS and VoiceOver used to show BBC mostly works and YouTube and many SPAs break. Shows failures: hidden content via max-height still reads, custom Vue widgets lose semantics, hover-only popups and client-side routing don’t announce page changes. Recommends fixes: keep native inputs or mirror them, use aria-live for dynamic text, announce navigation after route changes, and test with real screen readers or an accessibility tester.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:11Epilepsy
- 3:45Screen Readers
- 6:04Screen Reader Example
- 9:08Website Examples
- 12:05Screen Reader
- 13:30Safari
- 20:37Custom Components
related talks
30mWeb Accessibility with VueJS
31mBringing the Web Back to the Blind
46mA11Y with Vue - Can everyone reach your application?
01h 00m60 Minutes to Accessibility
41mBuilding Accessible Vue Components
46mYou Can Come to This Talk with Your Eyes Closed
25mHello Accessibility, my old friend
52mResearching and Writing Accessible Vue ... Thingies