Accessibility caters for routing for different user groups. It is important to keep in mind that accessibility does not just refer to wheelchair-accessible routing, but takes the diversity of visitors groups and their needs into consideration.

Mobility limitations

You can add a lot of complexity to routing options by opting to avoid elevators / escalators / revolving doors / narrow paths. You can either define these in your application, or allow the user to select each and every setting according to their preferences.

As an example, the default iOS options look like this:
options.avoidBarriers = false
options.avoidElevators = false
options.avoidEscalators = false
options.avoidNarrowPaths = false
options.avoidRamps = false
options.avoidRevolvingDoors = false
options.avoidStairs = fals
options.avoidTicketGates = false

On the opposite, you can define standard routing to avoid elevators, if you want to encourage users to use the stairs and escalators. This would be typical in e.g. a mall, where the elevators would be too crowded, if all the visitors used them.

Visibility limitations

As a key functionality, allows you to provide audio navigation following the ITU-T F.921 protocol: ”Audio-based indoor and outdoor network navigation system for persons with vision impairment”. 

  •  Support for detailed navigation instructions only for specific user groups (“the elevator buttons are on your left”)
  • Supports for detailed POI details for specific user groups (“This auditorium has an audio induction loop available”).
  • Support for hazard alerts (“beware of the slippery floor in the café area”)
  • Confirm route every x meters, customizable (“Keep walking straight for 15 meters”)
  • Support for landmarks (“turn right after the Blue meeting room”)
  • Support for segments (“you are now at the reception”)
  • Support for audio cue before instructions are given
  • Support for vibration when instructions are given

If you are interested in providing navigation that follows the protocol, and need help in understanding the requirements, we can connect you with an accessibility specialist to consult you on your venue's needs.

It is also important to keep in mind the large scale of vision impairments, when planning your application, and make sure the UI utilizes enough contrast between the different elements and floorplan. Read more on the Web Content Accessibility Guidelines (WCAG) 2.1.

Cognitional limitations

Remember that your users may also have different capabilities in understanding written and spoken instructions. Make sure your naming is clear, and vocabulary is simple. It is also a good idea to add a photo for each POI to help the user visualize what the location looks like.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us