Accessibility Done Right
summary
Shows concrete fixes and tools: keep JavaScript on and add ARIA roles and states so dynamic content actually reads out via ARIA live regions politely; label form fields with aria‑label/aria‑required, include errors in the page title and avoid captchas; add descriptive alt text, logical headers and high contrast (about 8% color deficiency); test with keyboard and native screen readers like VoiceOver and the WAVE Firefox plugin; cites Twitter as a working example and notes legacy screen‑reader quirks when retrofitting sites.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:07Accessibility story
- 3:05Its not about people with disabilities
- 3:22Its about people using the web
- 4:44Accessibility in real life
- 6:32Universal design
- 8:17Consistent language
- 8:38Be clear concise
- 11:00Be easy to use
- 13:12Avoid CAPTCHAs
- 18:49Area
- 25:31Wave
- 26:19Color Filter
- 27:04Color Contrast Checker
- 27:24Web Accessibility Tools
- 27:39Accessibility is not assistive technology
- 28:08Keep your JavaScript on
- 28:23Ask questions
- 33:07Thank you
related talks
01h 07mA web for anyone, anywhere, anytime
01h 01mA web for anyone, anywhere, anytime
47mBuilding Accessible Web Components
45mA Web for Anyone, Anywhere, Anytime
22mAccessibility for Everyone
37mAccessibility Matters: Creating a Better Web
25mBe an ally! In the battle for an inclusive and accessible internet!
31mBringing the Web Back to the Blind