Demystifying Accessibility in React Apps
summary
Covers how browsers build an accessibility tree, when to use native HTML versus ARIA, and how a demo form is implemented to announce errors and success reliably to screen readers (VoiceOver, NVDA, JAWS, TalkBack). Shows a reusable visually hidden component (polymorphic via an as prop), using React’s useId hook, aria-describedby/aria-invalid/aria-hidden, and role=status/alert for aria-live behavior. Demonstrates :focus-visible and the :has selector for keyboard-friendly hover actions, warns that research finds pages using ARIA often have more accessibility errors.
AI-written summary · about
chapters (8)
- 0:00Introduction to accessibility
- 1:25Foundations of web accessibility
- 4:17ARIA and semantic HTML
- 6:25Icon buttons and focus management
- 12:23Accessible text inputs
- 20:34Validation and error handling
- 23:03Accessible notifications
- 24:29Testing with screen readers
related talks
16mDemystifying accessibility in React apps
41mDemystifying Accessibility in React Apps
28mBuilding Accessible React Components
36mAccessibility in React Application
34mBuilding Accessible Web Apps in React
31mHow to Be an A11Y - Creating Accessible React Apps
34mBuilding Accessible Components in React
25mBuilding Inclusive Web Experiences: Web Accessibility in ReactJS
