Indoor navigation can remove barriers only when the whole journey is considered: finding the entrance, understanding choices, moving through the venue, recovering from a closed route and obtaining help when technology fails.
Treat wayfinding as a service, not only an app
Indoor wayfinding systems sit at the intersection of two regulatory threads in the UK: obligations to make physical spaces accessible, and obligations to make digital services accessible. Understanding which applies, and when, is the first step toward a system that actually works for disabled visitors rather than merely ticking a compliance box.
The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people. For a museum, retail unit, conference venue or stadium, that duty extends to how people find their way around the building. A wayfinding system that only serves visitors who can read standard-sized print on a wall-mounted sign, or who can operate a touchscreen without difficulty, may fall short of that obligation. The Act does not prescribe specific technologies, but it does create a legal incentive to think carefully about whether your chosen approach excludes particular groups.
For public sector bodies, the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 add a further layer. These regulations focus on the digital component: if your indoor navigation relies on a web app or mobile application, that software must meet the WCAG 2.1 AA standard. This affects everything from colour contrast in your wayfinding interface to whether screen readers can interpret the route instructions your system generates. The regulations apply to public sector organisations directly, but many private venues adopt the same standard as a benchmark because it represents a widely recognised measure of digital accessibility.
Building regulations, particularly Approved Document M in England and Wales (with equivalent provisions in Scotland and Northern Ireland), set requirements for physical features such as tactile signage, contrast markings and accessible route design. Indoor wayfinding technology does not replace these physical requirements. A beacon-based app that tells a visitor which corridor to take does not satisfy the obligation to provide tactile wayfinding information at decision points. The technology supplements the physical infrastructure; it does not substitute for it.
The practical upshot is that no single regulation tells you to install beacons, NFC tags or QR codes. Instead, the regulatory framework asks whether disabled visitors can independently navigate your space with a level of convenience comparable to that experienced by non-disabled visitors. If your current signage, layout and staff assistance leave gaps that technology could fill, the reasonable-adjustment duty pushes you to consider whether that technology is, in fact, reasonable to provide.
Combine physical, digital and human support
Matching technology to the access need
Different disabilities create different wayfinding challenges, and no single proximity technology serves all of them equally well. The selection process starts with understanding which groups you need to support and what each technology can realistically deliver.
For visitors with visual impairments, the key requirement is often an audio channel. Bluetooth beacons paired with a smartphone app can trigger spoken descriptions or turn-by-turn directions as the visitor moves through zones. NFC tags placed at specific decision points allow the visitor to tap and receive audio information on demand, giving them control over when they hear content. QR codes can serve a similar function but require the visitor to aim a camera, which is less straightforward for someone with limited vision. In all cases, the app or web page must be fully compatible with the device's screen reader (VoiceOver on iOS, TalkBack on Android).
For visitors with mobility impairments, the priority is usually route information: where the lifts are, which entrances are step-free, how to avoid stairs or steep gradients. Beacons can push location-aware notifications that highlight the nearest accessible route, but the underlying map data must accurately reflect accessible paths. An indoor navigation system that directs a wheelchair user to a staircase because the accessible lift was not included in the floor plan data is worse than useless. NFC or QR codes placed near lifts and accessible entrances can provide confirmatory information, such as operating instructions or current availability.
Visitors with cognitive or learning disabilities benefit from simplicity: clear landmarks, short instructions and the option to repeat information without social pressure. A system that floods the screen with multiple route options, estimated walking times and promotional content may cause confusion. Beacons that trigger a single, clear instruction at each decision point tend to work better than systems that present a full route overview. Visual cues within the app, such as photographs of the corridor or door the visitor should look for, can supplement text instructions.
Venue-specific applications
In museums and galleries, accessibility-focused wayfinding often centres on exhibit-level information. A visitor who cannot read the small-print label on a display case needs an alternative channel. NFC tags or QR codes on or near exhibits allow the visitor to request a large-text, audio or British Sign Language version of the label. Beacons can trigger the same content automatically as the visitor approaches, but automatic triggering raises questions about consent and notification frequency, particularly for visitors who may find unexpected audio disruptive.
In retail environments, the practical focus shifts to finding departments, assistance points and accessible facilities. A beacon system that announces the location of the nearest assistance desk or accessible fitting room as the customer enters a new zone can reduce the need to ask staff for directions. However, the system must account for the fact that store layouts change frequently. If a department moves and the beacon zone is not updated, the accessibility benefit becomes a source of confusion.
At events and conferences, temporary infrastructure creates particular challenges. Wayfinding must be deployed, tested and removed within a short window. Accessible routes at large venues often involve long detours around service corridors or between buildings. A beacon or QR-based system that maps these routes in advance, and updates them if a route is closed on the day, provides tangible value. The limitation is that visitors must know the system exists before they arrive, which means pre-event communication is as important as the technology itself.
Test with disabled users and maintain the alternatives
Assuming digital replaces physical
The most persistent mistake is treating an app or web-based wayfinding system as a replacement for tactile signage, clear contrast markings and well-designed physical layouts. Regulations and standards are explicit that digital wayfinding is supplementary. A visitor who does not own a smartphone, whose battery has died, or who cannot use a touchscreen for any reason must still be able to navigate the space. If your budget forces a choice, physical accessibility improvements usually take priority over digital wayfinding.
Designing without disabled users
Wayfinding systems are frequently designed by able-bodied teams and tested only with able-bodied participants. The result is an interface that works perfectly in the office but fails in the hands of someone using a screen reader, a switch device or a phone mounted on a wheelchair at an unusual angle. Involving disabled users in the pilot stage, not just as a post-deployment feedback exercise, is the most reliable way to uncover these problems. Look for organisations that offer user-testing services with disabled participants, or recruit directly through access panels.
Overlooking maintenance as an access issue
A dead beacon battery or a defaced QR code is a minor inconvenience for most visitors. For a disabled visitor who is relying on that beacon as their primary navigation aid, it is a barrier. Maintenance schedules for accessibility-critical hardware should be tighter than for general promotional beacons. If a beacon serving an accessible entrance fails, it should be treated with the same urgency as a broken lift call button, not as a low-priority device refresh.
Ignoring the consent and privacy intersection
Accessibility-focused wayfinding often involves processing location data to determine where a visitor is and what information to provide. Under UK data protection law, disabled visitors have the same rights as anyone else to know what data is collected, how it is used and how long it is kept. The fact that data is collected for an accessibility purpose does not create an automatic exemption from transparency requirements. If your system logs the path a visitor takes through a museum to improve future wayfinding, that processing must be explained in the privacy notice, regardless of the visitor's disability status.
Key checks before deployment
- Screen reader compatibility: Test the wayfinding interface with VoiceOver and TalkBack. Verify that route instructions are announced in a logical sequence and that interactive elements are correctly labelled.
- Accessible route accuracy: Walk every accessible route in the system and confirm that the floor plan data matches the physical reality. Check that lifts, ramps and accessible toilets are correctly positioned and described.
- Offline capability: Determine whether the system functions in areas with poor mobile signal. If it relies entirely on a live connection, visitors in basement levels or thick-walled older buildings may lose access precisely where they need it most.
- Physical signage alignment: Confirm that digital instructions reference the same landmarks, room names and directional language as the physical signage. Contradictions between a sign on the wall and the app in the visitor's hand create confusion.
- Notification control: Ensure that visitors can adjust or silence audio notifications. Automatic audio triggers can be disorienting for some users, particularly in echo-prone spaces.
- Fallback plan: Define what happens when the technology fails. Staff should know how to direct visitors manually, and physical signage must be sufficient to allow independent navigation without the app.
For regulatory guidance specific to your sector and nation within the UK, consult the Equality and Human Rights Commission's resources on the Equality Act 2010, the Government Digital Service's guidance on the Public Sector Bodies Accessibility Regulations, and the relevant building regulations documents for your jurisdiction. This article provides practical context rather than legal advice, and the regulatory landscape can change.
Accessibility acceptance criteria
- Essential destinations remain discoverable without a compatible smartphone.
- Digital content meets the project’s applicable accessibility requirements.
- Routes include step-free and other relevant constraints, with human-verified updates.
- Instructions do not depend only on colour, small text, audio or precise gestures.
- Disabled users are involved before launch and after material venue changes.
