Accessibility

We aim for the Solo Run website to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We use the same standard as a reference for the mobile app where web-specific requirements do not directly apply. This is a continuing target, not a claim that every screen or piece of content already conforms.

The website uses structured headings, meaningful link text, labelled controls, visible keyboard focus and a logical reading order. Pages adapt to smaller screens and larger text. Core navigation and policy content can be used without a mouse.

Decorative images are hidden from assistive technology; images that carry meaning receive text alternatives. We avoid using colour alone to communicate an essential state.

We design main app flows for VoiceOver on iOS, TalkBack on Android, system text sizing and common display adjustments. Interactive controls should have accessible names, roles and states. Touch targets should remain usable without precise movement.

The website respects the reduced-motion preference for non-essential animation. Text should remain readable without relying on background artwork. Zoom, contrast settings and colour filters may change the appearance, but they should not block the main task.

A route map, elevation chart, photograph or audio waveform can contain detail that is difficult to express through a short label. We aim to provide adjacent text for the main distance, duration and effort information, but some spatial detail may still require visual access. User-created photographs, recordings and notes may not include accessible descriptions.

Some older illustrations, third-party map controls, app-store pages and operating-system permission screens sit outside our full control. Very large text may require more scrolling.

Apple, Google, mapping providers, identity providers and device makers control the accessibility of their own interfaces. Report a barrier to us when it blocks a Solo Run task, even if a third party supplies the affected control. We will investigate what we can change or document a workable alternative.

Email hello@moriurban.com with the page or screen, what you were trying to do, the device and operating-system version, browser or app version, and any assistive technology involved. Do not include a password, sign-in code, precise route or raw health export.

We usually acknowledge support messages within three business days. Fix time depends on severity and whether a platform or provider must change something first. If you need the information in another format, state the format and the best way to contact you.

We review accessibility during design, implementation and defect work, and we test core flows with keyboard and screen-reader checks. We will update this statement when our target, known limits or contact process materially changes.