Does your design conform with WCAG accessibility guidelines — or does it comply
summary
Argues that meeting WCAG is necessary but not sufficient and shows a working framework — Understand, Engage, Iterate, Scale — used to drive Pinterest’s roadmap, with a concrete Figma-based gating tool: Gestalt checklist in Figma plugin that flags contrast, semantics, tab order and target size. Cites outcomes: 100+ components built since 2021, 600+ people trained, a 9% product accessibility improvement, and legal risk (Target $6M settlement; ~2,000 web lawsuits in 2023) to justify prioritizing AA and mobile gaps.
AI-written summary · about
chapters (16)
- 0:00Introduction and goals
- 2:30Compliance vs. conformance
- 4:09Legal standards and laws
- 7:01Levels and risks
- 10:33Design system integration
- 13:27Inclusive design mindset
- 17:07Accessibility framework
- 19:56Understanding user needs
- 23:15Engagement and tools
- 26:41Iterating through feedback
- 29:23Scaling accessibility
- 31:23Pinterest implementation
- 33:22Best practices in action
- 36:14Training and resources
- 39:24Final takeaways
- 41:00Q&A session
related talks
49mMaking Pinterest More Inclusive Through Design Systems
26mAuditing design systems for accessibility
52mDesigning inclusive and accessible experiences
22mThe designer is the problem, design is the solution
52mEssential Accessibility Annotations for a Smoother Design to Development Handoff
26mProven ways to make your website accessible in 2023
44mDesigning with Accessibility in Mind
42mArchitecting for Accessibility