The Experience of Access
summary
Design claims that architecture must not dictate use and people will repurpose interfaces in whatever way is most convenient; teams built around 4 to 8 people cannot capture all lived experience so test coverage is limited. Concrete examples: restroom access forces allocating 15–20 minutes and the single one stall I can use is occupied about 80% of the time. Tech venues and hiring patterns produce few developers with physical disabilities and physical access failures persist.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05What experience design means
- 2:09End of UX as a role
- 3:34Defining access
- 4:21Design shouldn't dictate behavior
- 5:46Accessibility as user choice
- 7:17Disability as design lens
- 8:02Bad design and privilege examples
- 9:50Universal design and user choice
- 10:56Building diverse teams
- 11:59Diversity beyond checkboxes
- 13:04Homogeneous cultures problem
- 14:28Education access and tech diversity
- 15:54Closing thoughts
related talks
45mAccessibility at all stages
57mHow (and why) to 'shift-left' your accessibility testing
52mShop Accessible: Concrete Strategies for Procuring Accessible/Inaccessible Solutions
56mAccessibility for UX: Don't worry, it's much worse than you think
44mCrafting Great Accessible Experiences
14mAccessible Accessibility
12mAccessibility-First Development: Making Applications Inclusive from Day One
51mThe Intersection Of Accessibility And Inclusive Design