Meaningful order
Pages use landmarks, headings, labelled controls, descriptive links, and a predictable reading sequence. The app uses semantic labels and Android-native controls.
Accessibility
A guide should make room, too.
The app and support site are designed to remain readable, navigable, and calm across common device settings. Accessibility is an ongoing quality practice, not a certification claim.
Design commitments
Practical access choices
Scalable, high-contrast text
Content favors plain language, strong contrast, short paragraphs, visible focus, and system text scaling. Color is never intended as the only cue.
Respect reduced motion
The site disables nonessential animation when reduced motion is requested. Core information remains available with JavaScript or motion effects unavailable.
Generous targets
Primary controls use clear labels and practical touch sizes. Horizontal content is supplementary; essential routes also remain available through labelled navigation.
Editorial, not instructional alone
Images support atmosphere and recognition. Safety boundaries and module actions are stated in text rather than encoded only in a photograph.
Content without a connection
The Android guide does not require an account or network. External source links are optional and open only when a user chooses them.
Known limits
Device settings still matter
Very large text, display magnification, custom fonts, screen-reader versions, browser extensions, manufacturer changes, and older Android builds can affect layout or interaction. Image descriptions are concise and may not capture every visual detail. The site has been authored for keyboard use and modern assistive technology, but no single test represents every user or device.
If a page is difficult to use, try browser zoom or Reader mode, Android font/display size, TalkBack, high-contrast text, or reduced-motion settings. A trusted person may also help open the same material without entering participant information.
Accessibility feedback
Describe the barrier, not sensitive participant details.
Use the verified developer contact shown on the current Google Play listing or its linked public support page. Include the app version, device/Android version, screen name, assistive technology, and what you expected. Do not include medical, incident, roster, pickup, or other sensitive information.