Android app view - UX UI Design accessibility WCAG checklist

How to design an Android app view

WCAG Disabilities

An Android app view must meet WCAG principles:

1 Perceivable

Text can resize up to 200% with no loss of information - 1.4.4 AA
Content is presented in a meaningful sequence - 1.3.2 A
View can support pinch/zoom magnification - 1.4.4 AA
Page view adapts to horizontal or vertical orientation - 1.3.4 AA

2 Operable

View has a unique title heading that describes its purpose - 2.4.2 A
The focus order is meaningful (even if it doesn't perfectly match the visual layout) - 2.4.3 A
Offer at least two ways to find content (like navigation & search) - 2.4.5 AA
Path based gestures can be operated with a single tap - 2.5.1 A

3 Understandable

Help options are presented consistently in the page view. - 3.2.6 A

4 Robust

Meets criteria across platforms, devices and viewports 4.0.0 AA

An Android app view must work for people with disabilities:

Low vision

Text can resize up to 200% with no loss of information - 1.4.4 AA
View can support pinch/zoom magnification - 1.4.4 AA

Cognitive

Offer at least two ways to find content (like navigation & search) - 2.4.5 AA

Motor

The focus order is meaningful (even if it doesn't perfectly match the visual order) - 2.4.3 A
Page view adapts to horizontal or vertical orientation - 1.3.4 AA
Path based gestures can be operated with a single pointer - 2.5.1 A

Blindness

View has a unique title heading that describes its purpose - 2.4.2 A
Content is presented in a meaningful sequence (even if it doesn't perfectly match the visual layout) - 1.3.2 A
Meets criteria across platforms, devices and viewports 4.0.0 AA

Usage

Your Android view frames the foundation of all other components.

By considering accessibility from the beginning, your app will be consumable by a wider range of people, not just those with disabilities.

Material vs global experience language

Many enterprises have attempted to apply a global experience language to iOS, Android and Web platforms only to find that each platform isn’t just a different device — it’s a different way of operating.

Let Android be Android

Use Material components the way they were intended. Don’t try to cram Web and iOS conventions into a place they don’t belong.

Design Android app view