Accelerating accessibility in web
summary
A compact checklist for making components actually accessible: prefer native HTML over ARIA so controls ship with focus, states and keyboard behavior; verify keyboard navigation, visible focus styles and logical tab order; ensure color contrast and zoom to 400% without overlap; give every control an accessible name and expose states (expanded, selected, disabled); consider the Accessibility Object Model for web components; run Firefox/Edge accessibility devtools, Polypane, WAVE and CI checks (automate ~20% of tests).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:04What is web accessibility
- 3:32Component-based mindset
- 7:04Accessible component checks
- 11:16Naming controls properly
- 15:05Supporting zoom in components
- 16:08Conveying component states
- 17:54Honoring user preferences
- 19:38Accessibility Object Model
- 22:04Key takeaways summary
- 23:09Q&A on prioritizing accessibility
related talks
45mA Web for Anyone, Anywhere, Anytime
22mWeb Accessibility - a better user experience for everyone!
01h 07mA web for anyone, anywhere, anytime
26mAccessibility Is a Marathon, not a Sprint
25mBe an ally! In the battle for an inclusive and accessible internet!
47mAccessible JavaScript: it's easier than you think!
37mAccessibility Matters: Creating a Better Web
47mBuilding Accessible Web Components