Integrate Accessibility Snapshot Testing into the Mobile Build Process
summary
Hilton shows a concrete setup: snapshot tests run per component and screen for iOS and Android using PointFree, Paparazzi, accessible-snapshot, capturing light/dark, dynamic type, locales (including RTL Arabic) and screen sizes; tests produce VoiceOver output pre-merge so screen reader labels and swipe order get fixed before release. Developers write tests, PRs add roughly 10–30 snapshots per PR, repo growth is mitigated with git LFS, Android snapshots run fast without emulators, iOS accessibility snapshots run as slower hosted tests and require strict simulator and OS consistency.
AI-written summary · about
chapters (12)
- 0:00Introduction and team overview
- 2:05Why we needed snapshot testing
- 7:42What is snapshot testing
- 10:09Impact on accessibility work
- 11:13Design collaboration benefits
- 12:38Trade-offs and considerations
- 16:45Snapshot testing use cases
- 24:02Testing localization and layouts
- 26:07Integration steps and setup
- 35:51Review and approval workflow
- 36:12Final takeaways and next steps
- 38:18Q&A session
related talks
50mMobile accessibility: testing mobile sites and native apps for accessibility
19mTesting Beyond Unit
14mAutomated Visual Regression and Accessibility Testing Made Easy
46mGuerilla Accessibility Testing Techniques
39mHow to win at mobile accessibility
44mAccessibility Testing at Scale Powered by Appium
35mBuilding an accessibility testing habit
18mHow Slack mobile does accessibility