Android VPAT journey

Key Actionable Insights

1

Always ensure error messages are immediately announced to screen reader users when they occur, rather than requiring users to navigate to discover them. For Android, this means updating both inline error displays (OutlinedTextField) and banner-style errors (like SKBanner) to trigger TalkBack announcements automatically.

This was classified as a P1 issue in Slack's VPAT because it directly prevents screen reader users from understanding the outcome of their actions, creating a fundamentally broken user experience.

2

Exclude purely decorative elements like dividers from accessibility list item counts by implementing custom accessibility delegates. When TalkBack announces list item counts, decorative separators should not inflate the number, as this creates confusion about the actual number of interactive items available.

Slack's SK Bottom sheet dividers were being counted as list items, causing TalkBack to announce incorrect totals. The fix involved creating an SKListAccessibilityDelegate that overwrites CollectionInfo with accurate counts.

3

For any gesture-based interaction like drag-and-drop, always provide an accessible alternative through TalkBack custom actions. Add visible affordances like drag handles in an Edit mode, and implement custom actions such as 'Move before' and 'Move after' in the TalkBack context menu.

Users with motor impairments may not be able to perform drag gestures. Slack added both visual drag handles and TalkBack custom actions accessible via three-finger tap or L/r drawing gestures to their workspace switcher.

4

Never rely on color alone to communicate information like error states. Always pair color indicators with additional visual cues such as icons. Conduct an audit across your app to ensure consistent implementation of multi-signal error indication.

This maps to WCAG 1.4.1 Use of Color (Level A). Slack found inconsistent implementation across screens and had to audit and update multiple edit field error displays to include error icons alongside red text.

5

Test your accessibility decisions against native platform conventions rather than applying WCAG web standards directly to mobile native apps. Verify patterns by testing native Google apps and consulting platform-specific guidelines before implementing vendor recommendations.

Slack's vendor suggested app bar titles should be headings, but this didn't match Android native patterns. The industry still lacks comprehensive platform-specific mobile accessibility guidelines, so teams must do their own research.

6

Collaborate with design teams and members of the disability community when making accessibility decisions, especially for ambiguous cases. Small UI changes like adding a search icon to an edit field can significantly improve the experience for users with cognitive difficulties who may forget the purpose of unlabeled fields.

Slack worked with their design team and blind community members to resolve issues like the strikethrough formatting question, which led to a pragmatic decision that most screen readers intentionally don't announce this format.