PM-led Accessibility: Shepherding project teams into accessible design and developmen...
summary
A practical framework shows how to cultivate empathy with real user stories (stroke, screen reader, one-thumb mobile use), then unpack requirements from briefs into specific WCAG/Section 508 tasks and legal risks. It assigns role-based responsibilities (designers: contrast and focus states; developers: keyboard/ARIA; QA: ongoing tests), recommends progressive enhancement, testing early and reporting progress, and escalating for resources or external accessibility consultants when scope or risk is underestimated.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:30Typical roles
- 2:38Accessibility
- 3:00Project Managers
- 4:00How do we embrace accessibility
- 4:36Cultivating empathy
- 6:23Connecting with others
- 10:12Other resources
- 10:43Accessibility community
- 11:23Understanding requirements
- 16:02Risk mitigation
- 17:45Reporting accessibility progress
- 19:06Stay firm
- 20:02Refocus efforts
- 20:56Documentation
- 21:22Conclusion
- 21:42What got you focused on accessibility
- 24:28Working in accessibility
- 29:51Common themes
- 33:00Infectious
- 34:51Michelle Collier
related talks
01h 05mAccessibility Testing 101
01h 02mAccessibility - how to get the job done in a highly collaborative manner
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
31mWeb Accessibility: From Design to Code, How to Move Toward Greater Inclusion
09m"How to bring accessibility into your teams."
29mHow to bring accessibility into your teams
44mDesigning with Accessibility in Mind
38mHow to set up an accessibility program in an imperfect world