Building Accessible Components: Best Practices and Business Buy-In
summary
Explains concrete fixes and outcomes: uses semantic HTML, focus management, ARIA roles, keyboard handlers and tabIndex to make React components operable; audits with Lighthouse, Siteimprove, Storybook accessibility addon and automated plus manual screen‑reader tests; faces a real bug in Foundation’s nav so chooses to build a mega menu from scratch rather than wait or fork; measures results — WCAG AA and higher Lighthouse scores, improved scalability and reduced legal risk; practical wins and small incremental rollout advice like start with a high‑impact component.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:47Four principles of accessibility
- 4:40React component techniques
- 8:27Barriers to accessibility
- 10:12Testing tools and manual checks
- 10:57Business case for accessibility
- 13:03Jovia Financial success story
- 17:19Key takeaways
- 18:45Q&A
related talks
34mBuilding Accessible Components in React
34mBuilding Accessible Web Apps in React
28mBuilding Accessible React Components
35mAccelerating accessibility in web
22mAccessible Components with Homer Gaines
26mAccessibility Is a Marathon, not a Sprint
47mBuilding Accessible Web Components
41mDemystifying Accessibility in React Apps