Android VPAT journey

Slack's Android team tackled a VPAT accessibility audit and found critical gaps that affected screen reader users. Here's what they fixed and why it matters for your mobile app.

After Slack's major UI redesign (IA4), a third-party accessibility vendor identified numerous Android a11y issues through a VPAT assessment. Staff Engineer Hye Jung Choi shares how the team triaged and resolved the most impactful problems, from error announcements to drag-and-drop alternatives.

Key Takeaways

• Error messages weren't announced to TalkBack users, forcing manual screen navigation
• Added Edit mode with six-dot handles and custom TalkBack actions for workspace reordering
• Fixed list item counts by creating SKListAccessibilityDelegate to exclude decorative dividers
• Search field got explicit icon so users know its purpose when placeholder text disappears
• Not all WCAG standards apply to Android native patterns after testing Google apps

The team discovered that one common text formatting feature actually shouldn't be announced to screen readers, and the blind community agreed.