Coding For Accessibility Best Practices from the Front Lines
summary
Concrete checklist of what breaks and what fixes it: semantic HTML5 landmarks, correct heading order, labels tied to inputs (for/id or wrapped label), fieldset/legend for grouped radios, required attribute or aria-required, and focus management with aria-describedby for error summaries; automated scanners miss keyboard traps and context so supplement with manual tests—keyboard only navigation, zoom to 400%, hide images, turn sound off; cites numbers: 42.5 million (US), 1.3 billion global, ~4,600 ADA cases in 2023; tool examples include Screaming Frog and Chrome DevTools accessibility tree and a Mac contrast picker.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 3:57Why accessibility matters
- 10:16Common accessibility problems
- 17:16Keyboard accessibility and forms
- 27:49Form validation best practices
- 31:18Buttons links and labels
- 34:48Focus states and design considerations
- 36:54Key takeaways and resources
related talks
31mDecoding web accessibility through testing
22mWeb Accessibility - a better user experience for everyone!
27mAccessibility, what do you eat that with?
01h 03mAccessibility Testing: The Manual Parts
01h 01mA web for anyone, anywhere, anytime
41mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
41mTales of Accessibility Failures
41mAccessibility is a Requirement