Unlocking Inclusion, How to Get Started With A11y Testing
summary
A simple four-rule checklist claims to reveal 80–90% of accessibility issues and the team validates it by doing a manual gap analysis that produces a long bug list: contrast fails (checked with Xcode and platform tools), text truncation when scaled, overlapping cast-controller buttons, a missing button that blocks flow, tab focus loops on login, and screen-reader labels that read nonsense. Initial testing uses built-in platform tools and hands-on checks; automation comes later.
AI-written summary · about
chapters (19)
- 0:00Accessibility testing intro
- 3:20Why inclusion matters
- 6:26Legal drivers for accessibility
- 8:13Challenges with guidelines
- 9:39Five rules for compliance
- 13:08Gap analysis for apps
- 13:49Building accessibility into features
- 14:53Legacy systems and docs
- 15:16Real-world accessibility issues
- 19:51Keyboard and screen reader testing
- 20:33Screen reader testing and UI
- 23:00Benefits beyond compliance
- 24:48AI in accessibility testing
- 25:34Q&A: Accessibility tools
- 26:38Q&A: Automating accessibility
- 26:58Q&A: Legacy app hurdles
- 27:42Q&A: Contrast testing tools
- 28:02Q&A: Tool result differences
- 28:25Q&A: Blind-friendly websites
related talks
41mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
01h 05mAccessibility Testing 101
45mTips from the Trenches: Accessibility Testing
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
21mAccessibility 101: Getting started with assistive technology and product inclusion
21mTesting A11y: Validating Web App Accessibility
01h 03mAccessibility Testing: The Manual Parts
21mGetting started with accessibility and product inclusion