Accessible Components with Homer Gaines

on YouTube ↗22m

" summary

Covers WCAG 2.1 POUR and gives concrete guidance: build components with semantics first, prefer native buttons for actions and links for navigation, always use explicit form labels and alt text, keep headings sequential, and use tabindex 0 / -1 sparingly. Cites surveys: 98.1% of sites have accessibility failures and ARIA usage correlates with ~60% more errors. Recommends design systems plus testing — automated checks catch ~20–57% of issues and manual tests with VoiceOver NVDA JAWS finish the job.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:08Accessibility
3. 3:35Disabilities
4. 6:52Coding Practices
5. 8:37Accessibility Standards
6. 11:09Semantic Markup
7. 11:56Buttons
8. 15:45Images
9. 18:41Tab Indexing
10. 19:12Testing
11. 20:42Manual Testing

" related talks

• 41mBuilding Accessible Vue ComponentsHomer Gaines · Vueconf.US 2022
• 52mCommon Accessibility PitfallsChris DeMars · DevReach 2022
• 35mAccelerating accessibility in webHidde de Vries · Git Commit Show 2021
• 47mBuilding Accessible Web ComponentsRuss Weakley · Inclusive Design 24 (#id24) 2016
• 23mBuilding Accessible Components: Best Practices and Business Buy-InWayne Jones · Commit Your Code 2025
• 37mAccessibility Matters: Creating a Better WebLindsey Dragun · DjangoCon US 2017
• 59mImproving Accessibility Through Design SystemsHomer Gaines · Web Accessibility in Mind Conference 2024
• 01h 07mA web for anyone, anywhere, anytimeRowdy Rabouw · NDC Melbourne 2022