Skip to main content

Accessibility

A product for blind travelers has to be operable without the screen

That is not a compliance target here, it is the primary interface. This page says what conforms today, what does not yet, and how to tell us when we have got it wrong.

The app

Voice first

Every screen ships with a labelled, ordered VoiceOver pass, written as part of building the screen rather than retrofitted afterwards. Controls are reachable with Voice Control by their visible names. Critical actions are never icon-only and never hidden behind a gesture you have to already know.

Display and text

Layouts respond to Dynamic Type through the accessibility sizes, support Increase Contrast and Reduce Transparency, and honour Reduce Motion — including in the live scene, where motion is decorative rather than informational. No state is communicated by colour alone; every colour cue is paired with text, shape, or audio.

Audio and haptics

Feedback is designed to preserve environmental hearing. Directional audio is mixed to sit alongside street sound rather than mask it, and the traveler sets verbosity, intensity, cadence, units, and modality. Guidance can be run haptics-only, speech-only, or both.

Language and locale

Speech, measurements, and route phrasing follow the user’s language and locale rather than a fixed default.

Capability tiers are disclosed

LiDAR and camera-only devices are presented as distinct tiers with explicit limitations, named at first launch and again whenever a limitation is the reason guidance is being withheld. An accessible product does not hide the shape of its own competence.

This website

The site targets WCAG 2.2 Level AAA for contrast and Level AA throughout, and is built to the following:

  • All body and interface text meets a contrast ratio of at least 7:1 against its background.
  • Every interactive element has a visible focus indicator, and the page order matches the reading order.
  • A skip link precedes the header. Landmarks, headings, and lists are semantic, with one level-one heading per page.
  • The plan-view demonstration on the home page carries no information that is not also in text. The drawing itself is hidden from assistive technology; the whole walk — every banner, every spoken line, every pulse setting — is present as an ordered list from first paint.
  • That list is deliberately not a live region. Announcing each cue as it changed would be exactly the constant narration the product refuses to do, so the demonstration never interrupts you and is readable at your own pace.
  • The demonstration is pausable, and each step is a labelled button you can jump to.
  • prefers-reduced-motion disables animation and scroll reveals, and the demonstration is server-rendered paused — so it only ever starts moving once we know you have not asked it not to.
  • Scroll reveals start visible and are only hidden once the observer confirms it can reveal them, so nothing is lost to a failed script or a crawler.
  • The site works without JavaScript apart from the demonstration controls, and the navigation menu uses a native disclosure element.

What does not conform yet

Stating this plainly is more useful than a conformance badge:

  • Media placeholders on this site are not yet real footage. When video is added it will ship with captions, audio description, and a transcript — those are release blockers, not follow-ups.
  • The app’s VoiceOver pass has been written but not yet independently audited by blind testers across every screen. That audit is part of the supervised trials.
  • Braille display output has not been designed. It is on the list and has no date.

Reporting a barrier

If something here or in the app is not usable, tell us and we will fix it. Email nhellyer6@gmail.com with “accessibility” in the subject. Describe what you were trying to do and what happened; you do not need to identify the technical cause.

We aim to acknowledge within five working days and to give a fix or a reason within twenty.