How Slack mobile does accessibility
summary
Slack Mobile runs with one Android accessibility engineer, no dedicated iOS hire yet and plans to recruit one, and no manual QA so engineers own accessibility. Processes include bi-weekly Testfest sessions, weekly third‑party regression tests tied to a weekly release, and Fable user research. Development uses Espresso accessibility checks on 1,000+ UI tests, lint-as-error for new view code, and a third‑party paid SDK for extra automated catches beyond the ~50–60% typical coverage; 95% of screens use design‑system components.
AI-written summary · about
chapters (11)
- 0:00Slack mobile accessibility intro
- 1:09Accessibility team and processes
- 3:39Accessibility feedback
- 5:51Accessibility testing and checks
- 7:40Mobile test sessions
- 9:47User research and newsletters
- 11:13Development and release tools
- 13:44Automated and manual testing
- 15:09Design system improvements
- 16:34Sharing best practices
- 17:15Q&A
related talks
42mAccessibility @ Scale
36mRaise accessibility awareness at work as an Android developer
20mDid You Hear? Accessibility for Mobile Apps
49mThe Next Generation of Automated Accessibility Testing for Mobile Apps
42mMake Your Mobile Apps Accessible to All
40mGetting started with mobile accessibility: iOS, Android, and Flutter
01h 02mAccessibility - how to get the job done in a highly collaborative manner
34mIs your app for everyone? A primer on accessibility for Android