What If We Talked About Web Accessibility?
summary
Demonstrates web accessibility problems affecting about 1 billion people by running a Chrome DevTools/Lighthouse audit, showing keyboard-only navigation to expose broken tab order and fixing a modal focus trap. Explains how tabindex and ARIA roles alter screen reader output, and builds a custom checkbox where JavaScript updates aria-checked to show semantic markup plus scripting is required; includes a legal example (Coles, Australia) to illustrate real consequences.
AI-written summary · about
chapters (20)
- 0:00Beginning
- 0:27The power of the web lies in its universality
- 1:10Why is it important?
- 2:52Legal obligations
- 5:12Vocabulary
- 6:04Web Content Accessibility Guidelines
- 7:02Why aren't all websites accessible today?
- 7:36Are developers familiar with accessibility?
- 9:07What can you do?
- 9:24Use your keyboard
- 9:58Private browsing
- 10:53DOM order
- 12:38Focus
- 14:07As-by on buttons
- 19:28Who borders?
- 21:42What does it look like?
- 26:41Semantics
- 30:22Buttons
- 34:47DevTools
- 37:32Modifying existing elements
related talks
31mDecoding web accessibility through testing
13mDemystifying Web Accessibility
44mTesting Web Accessibility
32mDemystifying Accessibility
31mWeb Accessibility: From Design to Code, How to Move Toward Greater Inclusion
41mTales of Accessibility Failures
26mMake the internet a better place - with coding for accessibility
22mWeb Accessibility?