Building Accessible Web Apps in React
summary
Argues that accessibility belongs in the first lines of a React app and proves it with a three‑stage demo that converts a broken list into a usable experience using shadCN components, ARIA roles and a roving tabindex. Cites WCAG AA as the target, mentions tools (axe, WAVE, Lighthouse, linters, screen readers) and concrete stats — ~4.9% vision, 5.7% hearing, 10% cognitive — to show scope. Shows code (github.com/shotikapor08/tanstack-example-jokes) and demonstrates that the fix works for keyboard and screen reader navigation.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:57Accessibility matters
- 8:50Testing accessibility
- 14:05Accessible vs non-accessible demo
- 25:34Key takeaways and Q&A session
related talks
25mBuilding Inclusive Web Experiences: Web Accessibility in ReactJS
36mAccessibility in React Application
39mBuilding Webapps for everyone - a11y with React
26mDemystifying Accessibility in React Apps
41mDemystifying Accessibility in React Apps
31mHow to Be an A11Y - Creating Accessible React Apps
50mTips, tricks and tools for building accessible React web apps
28mBuilding Accessible React Components