Accessibility

More than colour and motion.

The interface combines scale-aware text, visible labels, native controls and reduced-motion support. Accessibility still depends on the final device configuration and should be tested with the intended users.

01

System-scaled text

Text uses Android scale-aware units so a user's font-size preference can increase readable copy.

02

Visible button equivalents

Custom pitch, ribbon, fork, prism and loop graphics are paired with labelled native controls; the canvas is never the only route to an action.

03

Large targets

Primary controls are designed around at least 48dp targets with spacing suitable for touch.

04

Contrast and non-colour cues

Labels, numbers, shapes and position carry meaning alongside the navy, green, citron, orange and mist palette.

05

Reduced motion

A local switch removes route-entry motion. Android's reduced-motion preference is complemented by the visible in-app control.

06

Bounded language

Controls avoid unexplained icons and provide headings, descriptions and reset language in English.

Adults navigating a marked football activity in open space
Practical review

Test the exact release, not the design intention.

Before publication, the responsible publisher should test screen-reader order, large-text reflow, contrast, switch access and touch behaviour on representative devices. An accessibility statement is useful only when it stays aligned with the actual uploaded AAB.

Read support and limitations