Getting started with accessibility and product inclusion
summary
Practical starter steps and concrete tools: test keyboard-only and screen‑reader flows, run Accessibility Scanner on Android and Chrome Lighthouse on desktop, and map failures to WCAG rules; automated checks catch about 57% of issues so pair them with manual tasks (keyboard navigation, screen reader activation). Example findings include missing alt text, unlabeled icons, low contrast, untabbable controls; workshops surface product ideas like skin‑tone matching and cite demographic shifts (US Latinx mobile app use +48% 2015–16).
AI-written summary · about
chapters (12)
- 0:00Accessibility and inclusion intro
- 1:24Accessibility and assistive tech
- 4:35Keyboard navigation demo
- 7:49Accessibility testing methods
- 11:23WCAG guidelines
- 12:28Inclusive design vs inclusion
- 13:57User inclusion meaning
- 15:03Business case for inclusion
- 16:05Inclusion in dev workshops
- 17:57End-to-end inclusion process
- 18:42Inclusive mindset culture
- 20:04Call to action
related talks
01h 05mAccessibility Testing 101
56mAccessibility Testing 101
45mTips from the Trenches: Accessibility Testing
35mBuilding an accessibility testing habit
36mRaise accessibility awareness at work as an Android developer
29mUnlocking Inclusion, How to Get Started With A11y Testing
35mAccessibility (when you don't have time to read the manual)
42mArchitecting for Accessibility