Skip to content
PROAV HUBSYSTEMS & HANDOVERالعربية
FIELD REFERENCESystems Case studies Tools
Wayfinding & kiosks

Wayfinding kiosks that get people to a destination

A wayfinding kiosk succeeds when a visitor can identify a destination and follow an available route. Maintain one destination record for Arabic and English, match it to physical signs and assign responsibility for changes. Test closed routes and a usable alternative to touch interaction.

Which records must stay aligned?

Decision pointEvidence to record
DestinationApproved Arabic and English name
RouteStarting point, floor changes and accessible alternative
OperationUpdate owner, closure notice and recovery action
  1. Walk the route from the visitor’s actual starting point.
  2. Compare both language versions with physical signs.
  3. Demonstrate a closed destination and its alternative route.

Test destination names, accessible routes and closed-path alternatives.

PROAV
Illustration of a vertical retail display between storefronts.
Display setting illustration

Build a maintained destination model

Agree one destination name with the facility team and use it on digital screens and physical signs. Record the route origin, floor changes and restricted areas. Hotels need event changes; hospitals need department changes; airports may need separate operational data. Do not imply a connection to live flight or clinical systems unless it is actually in scope and authorized. Keep route ownership and the update process visible in the project brief.

Match the interface to the approach

Survey how a visitor approaches the kiosk and where they stand. Check reach, glare and the room available for mobility aids with the project’s accessibility specialists. A map may need to orient itself to the physical location; a decorative compass is not enough. Test a destination search with spelling variants and familiar names in both languages. Keep the selected language and back action clear throughout the route, with a visible way to start again.

Separate accessibility from a touchscreen claim

Web accessibility is relevant to a kiosk interface, but it does not cover the entire physical installation. Provide an alternative such as staffed assistance or clear physical signs, appropriate to the facility. Avoid collecting personal details just to display a route. After inactivity, reset the session without exposing earlier searches. Plan a useful offline state and indicate when destination information was last updated rather than silently showing an obsolete route.

Compare requirements

Planning comparison — verify the proposed configuration
Project conditionFocusEvidence to request
HotelChanging eventsEvent owner and daily updates
HospitalDepartment accessVerified route and assistance alternative
AirportComplex zonesAuthorized data and controlled updates

Procurement checklist

  • Align names with physical signage.
  • Test a complete route in each language.
  • Assign closure and map updates.
  • Provide a non-touch alternative.
VERIFY IN PRACTICE

A practical acceptance task

Give visitors an unfamiliar destination and observe whether they arrive without help. Include a changed or closed destination and an offline session. Record incorrect turns and confusing wording, then fix the route rather than merely restyling the screen.

Build a project brief

Technical references & installation scope

Confirm the offered model’s limits and applicable local requirements with the responsible project team.

Project references

Continue the project

Updated: