Where standard routes exclude people
Indoor navigation systems marketed as "accessible" frequently default to the same shortest-path algorithms used for all visitors, with a step-free filter applied as an afterthought. For a wheelchair user, the shortest step-free route is not necessarily a usable one. A path that avoids stairs but includes a heavy fire door, a narrow corridor, or a steep ramp may be technically passable but impractical or unsafe.

Wheelchair-accessible routing demands a distinct data model. Standard indoor maps typically record corridors, rooms, and connections. An accessible map must additionally capture door widths, threshold types, ramp gradients, floor surface changes, lift dimensions, turning-space availability at junctions, and the location of features such as automatic doors or accessible toilets. Without these attributes, the navigation engine cannot distinguish between a route that is merely step-free and one that is genuinely navigable.
Proximity technology plays a specific role here. Bluetooth beacons, NFC tags, and QR codes can confirm that a visitor has reached a critical decision point — a lift lobby, a ramp entrance, or a controlled-access door — and deliver context-specific instructions. This matters because wheelchair users often need to take actions that other visitors do not: waiting for a lift, pressing a request button, or using a different entrance entirely. Zone-based triggers can provide those prompts at the right moment, rather than relying on the visitor to notice a small instruction on a phone screen while managing a chair in a busy corridor.
The practical distinction is between navigation that plots a route and navigation that supports a journey. Plotting a route is a geometry problem. Supporting a journey means accounting for the physical realities of moving through a building in a wheelchair, and updating that information when conditions change.
Design for perception, movement and cognition
Hospitals and Healthcare Facilities
Hospital wayfinding is a common starting point for accessible navigation, but it also exposes the limitations quickly. Outpatient departments, wards, and treatment areas are often spread across multiple floors and connected buildings. A wheelchair user may need to travel from a ground-floor reception to a first-floor clinic, then to a ground-floor pharmacy before leaving. Each leg of that journey may involve different lifts, different surface types, and doors with varying access mechanisms. The navigation system needs to handle multi-leg routes where the accessible path is not simply the reverse of the outward journey — for instance, a one-way accessible corridor or a lift that only serves certain floors.
Retail and Leisure Venues
Shopping centres and leisure venues present a different challenge: volume and variability. During peak hours, corridors that are wide enough for a wheelchair may become obstructed by displays, queuing systems, or crowd density. An accessible route mapped in a quiet morning survey may not reflect the reality of a Saturday afternoon. Some venues use real-time or near-real-time zone monitoring to detect congestion, but translating that into rerouting for wheelchair users requires the system to hold alternative accessible paths, not just alternative paths. If the only step-free route is blocked, the system should communicate that clearly rather than silently directing the visitor into a difficult situation.
Museums and Exhibition Spaces
Museums often have complex layouts with temporary exhibitions that alter routes for months at a time. Accessible navigation in this context depends on keeping the underlying map data aligned with the physical space. A temporary partition that narrows a corridor below usable width, or a ramp installed for an exhibition that has a different gradient from the permanent one, both need to be reflected in the routing data. Beacons or QR codes positioned at exhibit entries can serve a dual purpose: delivering content and confirming the visitor's position against the expected accessible route.
Data Collection and Maintenance
Collecting the physical attributes needed for wheelchair routing is labour-intensive. Door widths must be measured, not estimated from architectural drawings — finished floor levels, door hardware, and building modifications frequently differ from plans. Ramp gradients should be measured with a digital inclinometer rather than assumed from design specifications. Surface types need to be recorded at a level of detail that matters to wheelchair users: a slight change from smooth vinyl to textured tile can affect effort and control, particularly for manual chair users.
Maintenance is an ongoing obligation, not a one-time task. Lifts go out of service. Doors are propped open or locked closed. Temporary obstacles appear during cleaning, maintenance, or events. The navigation system needs a process for updating accessible-route data when these changes occur, and a mechanism for communicating disruptions to visitors mid-journey. A beacon-triggered notification at a lift lobby saying "Lift 3 out of service — alternative route via Lift 7, Floor 2" is more useful than a route that silently leads to a broken lift.
Testing with disabled users and maintaining access
Equating Step-Free with Accessible
The single most common mistake is treating "step-free" as a sufficient accessibility attribute. A step-free route that passes through a 750 mm doorway, crosses a heavily ribbed entrance mat, or requires a sharp 90-degree turn in a narrow corridor is step-free but not wheelchair-accessible under BS 8300 or the Equality Act 2010's practical expectations. Any system that filters routes by step-free access alone will produce unusable directions for a significant proportion of wheelchair users.
Ignoring Manual and Powered Chair Differences
Routing requirements differ between manual and powered wheelchair users. A powered chair may manage a 1:12 ramp gradient that would be exhausting or impossible for a manual chair user. A manual chair user may be more affected by surface resistance over long distances. Most current indoor navigation systems do not differentiate between these needs, offering a single "accessible" route profile. When evaluating a system, ask whether it supports multiple accessibility profiles or a single binary accessible/not-accessible flag.
Overstating Positioning Accuracy
Indoor positioning using Bluetooth beacons or Wi-Fi does not provide the fine-grained accuracy in suitably designed and tested systems needed to guide a wheelchair through a narrow doorway or along a precise line in a corridor. Realistic accuracy in a typical UK retail or museum environment, after calibration, is usually in the range of two to five metres — sufficient to confirm which zone a visitor is in, but not sufficient to replace visual wayfinding or tactile guidance. Systems that imply turn-by-turn navigation comparable to outdoor GPS are overselling the technology. Positioning should be treated as zone confirmation and progress tracking, not precise steering.
Static Maps in Dynamic Spaces
A mapped route is only reliable until the first physical change. Venues that install accessible navigation without a plan for ongoing data maintenance will find the system degrading within weeks. Key questions to put to a supplier or integrator: how are route changes logged and propagated? What is the process when a lift is taken out of service? Can venue staff update a single zone or route segment without reconfiguring the entire map? How quickly does a change reach a visitor already in the building?
Testing Without Wheelchair Users
Routes validated by able-bodied staff walking the path are not validated for wheelchair use. A corridor that feels spacious on foot may feel confined in a chair, particularly when passing other people or manoeuvring at a junction. Door pressure that is easy to push open standing up may be very different when approaching from a seated position. Pilot testing should include wheelchair users — ideally a mix of manual and powered chair users — following the routes independently and reporting on each segment. Their feedback will typically identify issues that no amount of map-data review can catch.
Key Checks Before Committing
- Does the system store door widths, ramp gradients, and surface types as distinct attributes, or only a binary accessible flag?
- Can it route around a single out-of-service lift without disabling the entire accessible path?
- Does the positioning accuracy claim come with a measured environment report, or is it a theoretical figure from the chipset manufacturer?
- Is there a documented process for venue staff to update accessibility data without calling the integrator?
- Have routes been tested by actual wheelchair users, and is that testing documented?
- Does the system communicate mid-journey disruptions (lift out of service, corridor blocked) to the visitor, or does it only work at the point of route calculation?
Accessible indoor navigation for wheelchair users is not a feature that can be switched on after a standard system is built. It requires distinct data, distinct routing logic, and a maintenance discipline that treats physical accessibility attributes as live operational data rather than static map annotations. The technology that supports it — beacons, NFC, QR, zone detection — is the same used for general wayfinding, but what it is asked to do, and how accurately the underlying map reflects wheelchair reality, determines whether the result is genuinely useful or merely compliant on paper.



