1.0 Why an Open Standard?

When individuals and organisations get behind a purposeful vision, solutions to what previously seemed like big challenges become attainable.

The aim is that this Open Standard will help lower the barrier for built-environment owners and digital navigation services to make their environments, products and services inclusive from the outset as we continue to weave technology into our cities.

Once the Open Standard is adopted across the built-environment and digital navigation services alike, vision impaired people will benefit from a consistent, reliable and seamless navigation experience.

1.1 What types of content make up the Open Standard?

The Wayfindr Open Standard contains different types of content:

1.2 How are the guidelines informed

Five main resources have informed the content of the “Working Draft v1.0”:

  • The qualitative user research conducted by Wayfindr in the trials of London Pimlico Underground Station (February 2015), Sydney Town Hall Train Station (August 2015) and London Euston Underground Station (December 2015). In total, 49 user sessions took place in these trials.
  • Academic research that supports the findings in Wayfindr trials. Wherever used, academic research resources can be found under “References”.
  • Factual information about vision impairment and the navigation techniques of vision impaired people. The resources for this information can also be found under “References”.
  • Input and feedback from industry experts:
    • Professor Peter Barker, OBE
    • Alan Brooks, Mobility Specialist
    • Henry Daw, Sound Designer and Audio Branding Consultant, Owner of Oblique Sound
    • Ann Frye, Independent Accessibility Consultant
    • Google Beacon Platform Team
    • Sue Sharp, RLSB
    • Alastair Somerville, Sensory Design Consultant – Acuity Design
  • Input and feedback from Wayfindr Community members such as:
    • BlindSquare
    • BlueCats
    • Estimote
    • Guide Dogs NSW/ACT
    • Kontakt.io
    • Nominet Innovation

1.3 How to use the Open Standard

Each section of the Wayfindr Open Standard might be relevant to different audiences. Some of the audiences that will benefit from the Open Standard are:

  • Venue owners and their access consultants that want to make their estate accessible
  • Developers and designers of navigation products and services that offer wayfinding for vision impaired people
  • Researchers who are conducting research or experiments in the area of wayfinding for vision impaired people

Anyone who is involved in projects about wayfinding for vision impaired people should become familiar with Section 2 “Learning about mobility of vision impaired people, that provides an introduction to the world of vision impaired people and their navigation and mobility techniques.

If you are a venue owner or an accessibility stakeholder, the following sections will be the most relevant:

If you are involved in digital navigation services as a researcher or designer, the following sections include the most relevant content:

If you are involved in digital navigation services as a developer, the following sections will be relevant:

1.4 What is a Working Draft

This Working Draft is the first public release of the Wayfindr Open Standard. The Working Draft has been informed by Wayfindr’s user trials, existing academic or professional research and input from experts. For the Open Standard to evolve there is an open invitation for anyone to contribute insights and feedback.

Think and Do Tanks (Working Groups) will be set up. Made up of members of the Wayfindr Community, they will receive, digest, evaluate contributions and propose updates to the Working Draft.

We are working on tools and a governance framework for contribution. We plan to make this available over the coming months. Until then, please feel free to send your comments and suggestions to standard@wayfindr.net.

1.5 Index

1 – Getting started

1.0 – Why an Open Standard?

1.1 – What types of content make up the Open Standard?

1.2 – How are the guidelines informed

1.3 – How to use the Open Standard

1.4 – What is a Working Draft

1.5 – Index

2 – Learning about mobility of vision impaired people

2.0 – Purpose of this section

2.1 – Some facts about vision impairment

2.2 – Primary mobility aids

2.3 – Orientation and Mobility (O&M) training

2.4 – Landmarks and clues

2.5 – The safest, not the fastest or shortest route

2.6 – User preference for discreet technology

2.7 – References

3 – Designing for vision impaired people

3.0 – Purpose of this section

3.1 – Design principles

3.1.0 – Overview

3.1.1 – Involve users in the process

3.1.2 – Focus on the environment not the technology

3.1.3 – Use simple and concise messages

3.1.4 – Use active words

3.1.5 – Provide reassurance information

3.1.6 – Provide an instruction at every decision making point

3.1.7 – Provide different techniques for diagonal directions

3.1.8 – Provide auditory cues

3.1.9 – Divide the route into clear segments

3.1.10 – References

3.2 – Effective messaging for audio instructions

3.2.0 – Overview

3.2.1 – The components of an audio instruction

3.2.2 – References

3.3 – Different types of audio instructions

3.3.0 – Overview

3.3.1 – The classification

3.3.2 – References

4 – Guidelines

4.0 – Purpose of this section

4.1 – Guidelines for various environmental elements

4.1.0 – Purpose of this section

4.1.1 – Entrances & Exits

4.1.1.0 – Overview

4.1.1.1 – Announcing orientation after entering or exiting a venue

4.1.1.2 – Allowing users to choose entrance or exit

4.1.1.3 – Informing users about door type

4.1.1.4 – Announcing location of door opening button

s4.1.1.1 – Revolving doors: tell users where to find an accessible door

4.1.2 – Pathways

4.1.2.0 – Overview

4.1.2.1 – Providing guidance at each junction on the route

4.1.2.2 – Providing reassurance over long distances where no change in direction is required

4.1.2.3 – Informing about a curve in the pathway

s4.1.2.1 – Advising to keep on one side on a two-way route

s4.1.2.2 – Announcing the pathway type

4.1.3 – Tactile paving

4.1.3.0 – Overview

4.1.3.1 – Mentioning tactile paving in all audio instructions

4.1.4 – Escalators

4.1.4.0 – Overview

4.1.4.1 – Announcing direction of travel of escalator

4.1.4.2 – Announcing proximity of escalators

4.1.4.3 – Indicating next move while travelling on the escalator

4.1.5 – Stairs

4.1.5.0 – Overview

4.1.5.1 – Announcing the direction of stairs

4.1.5.2 – Describing the number of steps

4.1.5.3 – Announcing if there is more than one flight of stairs

4.1.5.4 – Indicating next move while using stairs

s4.1.5.1 – Advising which side of stairs to use

s4.1.5.2 – Announcing open riser stairs

4.1.6 – Lifts

4.1.6.0 – Overview

4.1.6.1 – Announcing the location of the call button

4.1.6.2 – Announcing which button to press when travelling in a lift

4.1.6.3 -Indicating next move before getting out of a lift

4.1.7 – Ticket control

4.1.7.0 – Overview

4.1.7.1 – Choosing the correct gate to travel in desired direction

4.1.7.2 – Describing the location of a wide gate

4.1.7.3 – Indicating next move while approaching the ticket control

4.1.7.4 – Using appropriate terminology to refer to the ticket control

4.1.7.5 – Clearly communicating actions required

4.1.8 – Platforms

4.1.8.0 – Overview

4.1.8.1 – Announcing arrival on the platform

4.1.8.2 – Determining orientation in relation to the platform edge

s4.1.8.1 – Determining position in relation to the platform length

s4.1.8.2 – Determining orientation in relation to the direction of travel

s4.1.8.3 – Announcing close proximity of two platforms

s4.1.8.4 – Warning if platform is part of pedestrian route

s4.1.8.5 – Announcing nearest way out before leaving the train

4.2 – Guidelines for various types of built-environment

4.2.0 – Purpose of this section

4.2.1 – Mainline Rail and Metro stations

4.2.1.0 – Overview

4.3 – Guidelines for mobile app development

4.3.0 – Purpose of this section

4.3.1 – Guidelines for mobile app functionality

4.3.1.1 – Providing user preview of all audio instructions

4.3.1.2 – Enabling replay of previous audio instruction

4.3.1.3 – Enabling dictation for searching

s4.3.1.1 – Enabling selection of directional instructions

s4.3.1.2 – Enabling dictation for selection of options

s4.3.1.3 – Providing guidance to the nearest help point

s4.3.1.4 – Suggesting the safest not the shortest or fastest route

s4.3.1.5 – Enabling users to choose voice type

s4.3.1.6 – Displaying the instructions as text

s4.3.1.7 – Enabling users to choose their mobility aid

s4.3.1.8 – Enabling saving of frequently used places

s4.3.1.9 – Enabling saving of personal landmarks

4.3.2 – Guidelines for sound design

4.3.2.0 – Overview

4.3.2.1 – Using sound to attract people’s attention

4.3.2.2 – Using different notification alerts for different purposes

4.3.2.3 – Distinguishing notification alerts from other sounds

s4.3.2.1 – Using new sound alerts for more specific purposes

5 – Wayfinding technologies

5.0 – Purpose of the section

5.1 – Bluetooth Low Energy beacons

5.1.0 – Purpose of this section

5.1.1 – What is a Bluetooth Low Energy beacon?

5.1.2 – Sources of Bluetooth signal distortion

5.1.3 – BLE beacon installation

5.1.3.0 – Purpose of this section

5.1.3.1 – Proximity-based approach

5.1.3.2 -Trilateration-based approach

5.1.3.3 – Best practices for BLE beacon positioning

5.1.4 The parameters of a BLE beacon

5.1.4.1 – iBeacon

5.1.4.2 – Eddystone

5.1.4.3 – Estimating the distance from a BLE beacon

5.1.4.4 – BLE beacon configuration settings

5.1.5 – Maintenance and Operational considerations

5.1.6 – References

6 – Open Source Wayfindr Demo mobile app

6.0 – The aim of the Wayfindr Demo mobile app

6.1 – How was Wayfindr Demo mobile app developed