RouteSky · Accessibility

RouteSky Accessibility Statement.

How we approach accessibility in RouteSky, and how to give feedback.

1. Our commitment

Accessibility matters. Alderframe is committed to making RouteSky usable for as many people as possible, including people with vision, motor, hearing, or cognitive differences. We design RouteSky to work alongside the system-level accessibility features built into iOS, and we treat accessibility as an ongoing part of how we build, not a one-off check.

2. Accessibility considerations

RouteSky is being designed and developed with the following considerations in mind:

Dynamic Type. Text scales with the system Dynamic Type setting so users can read content at their preferred size.
VoiceOver. Interactive elements are designed to be reachable and labelled for VoiceOver. We aim to give every meaningful control a clear, descriptive accessibility label and hint.
Contrast. Text and key UI surfaces are designed to meet reasonable contrast levels against the dark theme. We continue to test contrast against system settings, including Increase Contrast.
Large touch targets. Tap targets aim to meet Apple's Human Interface Guidelines minimum size to support users with motor differences.
Reduced motion. We honour the iOS Reduce Motion setting and provide subtler alternatives where motion is used decoratively.
Not relying only on colour. Status indicators (such as the Journey Score) are designed to be understandable through labels and shapes as well as colour, so they remain meaningful for people with colour-vision differences.
Glanceable surfaces. Information shown in widgets, Live Activities and the Dynamic Island is designed to be readable at a glance, with clear hierarchy and concise wording.
Voice Control & Switch Control. Interactive elements are intended to be operable using iOS Voice Control and Switch Control, leveraging native iOS controls wherever possible.

3. Known limitations

RouteSky is still in development. We want to be honest about this: some advanced map, route and weather visualisations may require further accessibility testing and refinement before release, and some areas of the app may not yet meet the standard we are aiming for. We are actively working on these, and we treat accessibility regressions as bugs.

4. Feedback

If you encounter an accessibility issue in RouteSky, or have a suggestion that would make the app easier for you to use, please get in touch:

Email: [email protected]
Subject line: RouteSky Accessibility

Please include your iOS version, device model, RouteSky version, and a short description of the issue. We will work to acknowledge feedback within a reasonable time and we welcome suggestions from users of assistive technology.

5. Ongoing improvements

Accessibility is iterative. We will keep this statement up to date as RouteSky evolves, and we will document material improvements and known issues here.

6. Standards and guidance

For RouteSky, we look to: Apple's Human Interface Guidelines (Accessibility), Apple's iOS Accessibility frameworks, and the principles of the Web Content Accessibility Guidelines (WCAG) 2.1 where they translate to a native iOS app. These RouteSky Accessibility Statement is not a formal conformance claim and does not constitute legal or regulatory certification.