Accessible JavaScript applications
summary
Modern single-page apps break screen readers unless navigation changes are announced, so route updates use aria-live polite/assertive and page titles change (React Helmet or lifecycle hooks). Images get alt text via computer vision APIs (Google/IBM/Microsoft) that return a caption and a confidence score. Custom widgets need tabindex role label, modals require aria-hidden and a focus trap, and animations honor matchMedia prefers-reduced-motion. Note: about 15% of people (~1 billion) have disabilities and some Windows screen readers like JAWS cost roughly $1,000 per license.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:19The importance of accessibility
- 3:20Types of disabilities and tools
- 5:12Visual impairment solutions
- 8:12Accessible image handling
- 10:10Navigation and ARIA live
- 12:20Page titles and skip links
- 13:54Physical impairment support
- 16:00ARIA and custom components
- 17:31Accessible modals and traps
- 19:33Cognitive and auditory support
- 21:43Temporary disabilities
- 23:42Conclusion and core takeaway
- 25:03Q&A session
