Skip to content
DocsAccessibility

DocsNavigation

Accessibility

What Veeee supports today for accessible routing and an accessible visitor page, and what organizations must map for it to work.

On this page

Accessible navigation depends on two things: the organization marking which connections are step-free, and the route planner honouring it. This page says precisely what is supported today.

Step-free and stair-free routing

Every connection has a Wheelchair accessible flag, on by default, and a type that says whether it is a hallway, a door, stairs or an elevator. The route planner can plan Step-free routes (only wheelchair-accessible connections), Avoid stairs and Avoid elevators, and always excludes connections marked temporarily blocked.

Mapping for accessibility

  • Turn Wheelchair accessible off on stairs, steps, turnstiles and narrow doors.
  • Give every elevator its own location on each floor it serves and connect them with Elevator connections, so a step-free route across floors exists.
  • Use Temporarily blocked when an elevator is out of service; routes will use the stairs or another elevator until it is cleared.
  • Name accessible entrances and restrooms so visitors can ask for them by name, and add aliases such as “accessible entrance”. See Points of interest.

The visitor page

  • Instructions are spoken aloud by default with the phone’s built-in speech, and can be turned off.
  • Instructions are short sentences in large type over the camera, and the full directions list is available at any time.
  • The page follows the phone’s light or dark setting, with a toggle.
  • Controls are reachable with a keyboard and screen readers announce status changes; the event card does not steal focus.
  • The screen stays awake while the camera is active, so a visitor does not have to keep touching the phone.