Web Accessibility: From Design to Code, How to Move Toward Greater Inclusion
summary
The talk surveys web accessibility problems and practical fixes: it cites automated audit limits (WAI, axe-core, Lighthouse) and emphasizes using semantic HTML and ARIA as progressive enhancement. It recommends enforcing accessibility via a design system with Storybook and Figma (contrast, keyboard order, alt text), testing with screen readers, and using Copilot/LLMs only as a suggestion that still needs accessibility-aware review.
AI-written summary · about
chapters (20)
- 0:00Web accessibility intro
- 1:25Screen reader demo
- 2:31Disability and digital inclusion
- 3:34Accessibility definition
- 4:57Automated testing tools
- 6:44Early accessibility integration
- 7:26User diversity discovery
- 9:09Design systems and accessibility
- 10:32Contrast and readability
- 12:40Emojis and accessibility
- 14:05User stories for accessibility
- 15:06Semantic HTML
- 16:53HTML tags and accessibility
- 17:56Image alt attributes
- 19:01ARIA and dir attributes
- 21:07AI tools limits
- 22:53Continuous feedback
- 23:35Fixing existing projects
- 24:59Conclusion and call to action
- 26:08Q&A
related talks
59mImproving Accessibility Through Design Systems
01h 05mAccessibility Testing 101
37mAccessibility Matters: Creating a Better Web
01h 07mA web for anyone, anywhere, anytime
44mDesigning with Accessibility in Mind
25mBeyond Compliance: Testing for a more Accessible Web
52mDesigning inclusive and accessible experiences
52mCommon Accessibility Pitfalls