How to Build Accessible Products
summary
Ontario requires new or refreshed web content since 2012 to meet WCAG 2.0 level A and mandates upgrading to level AAA by 2021 for organizations with 50+ employees, so compliance planning and cost avoidance matter. Practical actions include keyboard testing, publishing a central accessibility style guide, running an alt-text audit (intern-led at one company), using NVDA/VoiceOver cheat sheets for testing, rejecting text-only sites, and recruiting people with lived experience into design and QA.
AI-written summary · about
chapters (17)
- 0:00Accessibility panel intro
- 1:12Why accessibility matters
- 2:38Ontario’s accessibility law
- 4:24Accessible products benefit everyone
- 8:17Innovation at the edge
- 9:01Will accessibility last?
- 10:50Text-only alternatives fail
- 13:15Learning accessibility
- 17:52Free design resources
- 20:21Design for diversity
- 23:54One-size-fits-all fails
- 26:24How Jennifer got into accessibility
- 31:27Microsoft’s inclusive shift
- 36:16Accessibility is a journey
- 39:27Slack’s keyboard lesson
- 40:49Two must-haves for accessibility
- 43:00Q&A
related talks
45mAccessibility Models in Tech Companies
38mGuidelines on Designing for Accessibility in UX Design
01h 03mAccessibility: Making your websites more inclusive
29mCreating Accessibility Culture
29mAccessibility Matters: Creating a Better Web
06mWeb Accessibility by 2025
33mWeb Accessibility: Why, How and What?
40mAccessible Websites - A Prolegomenon