Accessibility Is a Marathon, not a Sprint
summary
Argues accessibility is incremental not instant and gives concrete wins: semantic HTML fixes (headings, nav, fieldset and legend) eliminate custom key handlers, replacing div-buttons with real buttons removes onkeydown hacks, ARIA states/properties fill only real gaps, and automated checks (the axe extension, headings map, linting with a11y JSX/ESLint) catch regressions. Cites CDC figure 26% of US population. Shows demos where less code and proper elements make forms and keyboard + screen‑reader behavior unexpectedly robust.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:25Defining Accessibility
- 2:15The Problem
- 3:59The Solution
- 6:01Semantic HTML
- 8:24Headings
- 9:56Buttons
- 11:44Forms
- 13:55ARIA
- 16:33Why are you using REM
- 17:44Why are you using 2K
- 20:56Visual Impairments
- 22:36Learning to Interact
related talks
29mAccessibility first is the new Mobile first
37mAccessibility Matters: Creating a Better Web
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
32mDemystifying Accessibility
52mCommon Accessibility Pitfalls
20mImpactful Accessibility: The Changes that Mean the Most
31mHow to Program with Accessibility in Mind
41mAccessibility is a Requirement