Navigating the A11Y Iceberg: Approaches for Organizational Accessibility Excellence
summary
Argues that reactive bug‑fixing causes fatigue and that starting at the Accessibility Iceberg’s base — interviewing teams to surface mental models — reveals root causes; recommends building an internal site + documented step-by-step guide, role‑based Slack/Teams channels, scheduled office hours, JIRA labels, a Kanban board and automation to track requests and licenses, and a 5+ year roadmap so accessibility shifts from downstream firefighting to measurable, sustained enablement across products.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:42The iceberg framework
- 3:01Understanding the levels
- 5:45Proactive vs reactive
- 6:32The river analogy
- 7:36Assessing the organization
- 12:25Building community
- 16:49Strategic documentation
- 23:18Taking action
- 24:53Executing the roadmap
- 31:00Sustaining systems
- 33:10Purpose and care
- 33:58Closing thoughts
- 38:22Q&A session
related talks
29mHow to bring accessibility into your teams
01h 02mAccessibility - how to get the job done in a highly collaborative manner
21mBuilding an Accessibility Culture
45mAccessibility at all stages
28mBuilding an Accessibility Culture, One Step at a Time
26mHow (Not) to Fail at Accessibility
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
38mHow to set up an accessibility program in an imperfect world