Accessibility FAQs Panel
summary
Panelists answer common mistakes with concrete fixes: use NVDA speech viewer to capture screen‑reader output as text, follow the WCAG alt‑text decision tree and write meaning‑first image descriptions (not “photo of” or verbatim captions), recognize that ASL interpretation is a AAA-level need while captions cost can block free events, and test with real users (watch them use content) rather than relying on analytics. Practical claims: start with AA-level choices, prioritize low‑hanging fruit, and iterate—progress over perfection.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:40Welcome
- 2:00Diane
- 3:05Gwen
- 4:05Bella
- 5:10Kayleen
- 7:15Star Peterson
- 8:00Most common misconception
- 8:55Biggest misconception
- 12:15Misconceptions
- 14:05What if someone becomes blind
- 16:00Why wait until access is requested
- 21:25Accessibility in the design of content
- 23:50Benefits of accessibility
- 26:45Guidelines for writing effective alt text
- 31:50Resources for writing alt text
- 33:02Image descriptions and alt text
- 35:02Empathy
- 37:17Visual challenges
- 39:00Low tech is needed
- 42:55Sitting with learners
- 44:02Following disabled people
- 45:07Connecting on LinkedIn
related talks
38mGuidelines on Designing for Accessibility in UX Design
22mAccessibility for Everyone
59mAccessibility in UX: A panel discussion
01h 03mAccessibility: Making your websites more inclusive
33mAccessibility Done Right
48mLet's break some WCAG rules
52mCommon Accessibility Pitfalls
22mAccessibility in Practice