Accessibility statement
What we aim for
Gonav Pilot should be usable by a pilot who reads with a screen reader, who needs larger text, who cannot tell red from amber, or who gets motion-sick from animation — and legible for every pilot on a kneeboard in sun. We follow Apple's and Google's accessibility guidelines and WCAG 2.2 AA where it applies to native apps, and we check the app with the platforms' own accessibility audits as part of our automated tests.
What works today
- Screen readers. Lists, forms, switches and sheets read with VoiceOver and TalkBack. In flight mode, every HUD figure is spoken by name with its unit ("ground speed, 100 knots"), and traffic that needs attention is read as one sentence.
- Text size. Text follows your system text size. The flight HUD's readouts grow up to 1.6 times their normal size so the HUD still fits a phone in portrait.
- Reduce Transparency. The glass panels over the map become solid.
- Reduce Motion. Sheet and card transitions become cuts.
- Contrast. Every text and background colour pair in the app's design system meets a 4.5:1 ratio in light and dark mode, enforced by a test.
What is still being improved
- The map itself is drawn as a picture, so its labels cannot be read by a screen reader. An accessible list of what is near, the active leg and nearby traffic is in progress.
- Traffic levels are shown by colour; a distinct shape per level is in progress.
- Some secondary text over the glass panels sits just under the contrast target in bright conditions.
- Not every screen has yet been walked end to end with a screen reader; the flight map and the NOTAMs page have.
Tell us
If something in the app does not work for you, write to the address on the privacy policy page with the screen, what you expected and what happened. We answer, and we fix what we can in the next release.