How it Works / WIM Record Objects / accessibility
accessibility

Inclusive Routing

Accessibility attributes as first-class citizens of the record — not optional metadata bolted on afterward. Every mobility, sensory, cognitive, and physical constraint is encoded here, enabling routing engines to generate truly inclusive routes across every channel, simultaneously, from one source.

WIM v1.0 33 fields 4 required
33
Total fields
4
Required
29
Optional
9
Field groups
EN 17210
Primary standard
Purpose
Built-in, not bolted on

The accessibility object makes inclusive routing structurally automatic. Because the data is in the record, any channel that reads the record gets accessibility context — without custom integration per system. One update propagates everywhere.

Hierarchy position
Root-level · always evaluated

The accessibility object sits at root level alongside place, topology, and status. Routing engines evaluate all accessibility fields before computing any route — a user's accessibility profile is matched against this object before a single edge is traversed.

Standards alignment
EN 17210 · WCAG 2.2 · ISO 21542

Fields map directly to EN 17210 functional accessibility requirements for the built environment. Digital output accessibility aligns with WCAG 2.2. Physical dimension thresholds follow ISO 21542 (Building construction — accessibility and usability).

EN 17210 (CEN) WCAG 2.2 (W3C) ISO 21542 BS 8300
01 Mobility & Route Access 3 fields
step_free_route
boolean required

Whether a fully step-free route exists from any public entrance to this destination. true guarantees that a traveller who cannot use stairs, steps, or kerbs can reach this destination using only lifts, ramps, and level surfaces. This is the primary flag evaluated by accessibility routing engines for users with step avoidance requirements.

Standard: EN 17210 Requirement 4.1 — Prerequisite for: wheelchair_accessible, mobility_scooter_accessible

"step_free_route": true
wheelchair_accessible
boolean required

Whether this destination is fully accessible to a standard manual or powered wheelchair. Implies step-free access, sufficient door clearance (≥ 0.9 m), turning space (≥ 1.5 m diameter), and accessible reception or service point. true requires step_free_route to also be true.

Standard: EN 17210 · BS 8300 — Implies: step_free_route, door_clear_width_m ≥ 0.9

"wheelchair_accessible": true
mobility_scooter_accessible
boolean optional

Whether this destination is accessible to a Class 2 or Class 3 mobility scooter. Requires wider clear widths and turning circles than a standard wheelchair (typically ≥ 1.2 m door clearance, ≥ 1.8 m turning space), and lift dimensions sufficient to accommodate the scooter footprint. Expressed separately because scooter access requirements are more demanding than standard wheelchair.

Typical door min: 1.2 m — Turning circle: ≥ 1.8 m — Lift depth min: 1.4 m

"mobility_scooter_accessible": true
02 Tactile & Orientation 3 fields
tactile_guidance
boolean required

Whether tactile ground surface indicators (TGSIs) — blister and corduroy paving — are present on the primary route to this destination. true enables routing engines to recommend this route to blind and visually-impaired users as a tactile-guided path. Tactile guidance is a mandatory wayfinding provision under EN 17210 for public facilities.

Standard: EN 17210 Requirement 5.3 · ISO 23599

"tactile_guidance": true
tactile_map_available
boolean optional

Whether a tactile map or raised-relief floor plan is available at or near this destination. Tactile maps allow blind and visually-impaired travellers to orient themselves spatially before beginning navigation. Presence of a tactile map is surfaced in voice AI channel output: "A tactile map is available at the entrance."

"tactile_map_available": false
braille_available
boolean optional

Whether Braille signage is present at this destination — on room signs, lift buttons, or directional panels. true indicates that a blind traveller can independently confirm arrival and orientation using tactile Braille information at the destination itself, without relying solely on audio guidance.

"braille_available": false
03 Auditory & Sensory Alerts 3 fields
hearing_loop
boolean required

Whether an induction loop (hearing loop / telecoil loop) is installed and operational at this destination. true enables hearing aid and cochlear implant users in telecoil mode to receive direct audio — critical at reception desks, consultation areas, and waiting rooms. Surfaced in all channel outputs for users with a hearing accessibility profile.

Standard: EN 17210 Requirement 7.2 · IEC 60118-4 — Symbol: BS EN ISO 7000-1641

"hearing_loop": true
audio_guidance_available
boolean optional

Whether an audio guidance system (automated voice announcements, infrared audio beacon, or Bluetooth audio trigger) is installed on the primary route to or at this destination. Enables fully non-visual navigation for blind users independently of a smartphone. Complements rather than replaces tactile guidance.

Types: IR beacon, BLE beacon (e.g. NaviLens), PA announcement — Standard: EN 17210 Requirement 5.4

"audio_guidance_available": false
visual_alarm_available
boolean optional

Whether visual fire alarms (strobes or flashing lights) are installed at this destination, supplementing audible alarms. Essential for deaf and hard-of-hearing users who cannot rely on an audible alarm for emergency evacuation. Surfaced in accessibility profile output and routing for users who require visual emergency alerts.

Standard: EN 54-23 (Visual alarm devices) · BS 5839-1

"visual_alarm_available": true
04 Cognitive & Sensory Comfort 4 fields
low_stimulation_route
boolean optional

Whether a low-stimulation route is available — one that avoids high-noise areas, crowds, bright or flickering lights, and strong odours. Designed for autistic people, people with sensory processing differences, anxiety conditions, or dementia. A low-stimulation route may be longer in distance but less cognitively demanding. Routing engines select this route variant when the user's profile includes sensory sensitivity flags.

Avoids: crowds, noise above 65dB, flickering lights, strong scents — May be longer route

"low_stimulation_route": true
quiet_route
boolean optional

Whether a specifically quiet route — below a defined noise threshold — exists to this destination. Distinct from low_stimulation_route in that it focuses exclusively on acoustic environment, not the full multi-sensory context. Beneficial for users with hearing aids who experience background noise amplification, and for users in pain who are noise-sensitive.

Threshold: typically < 60 dB ambient — Distinct from: low_stimulation_route

"quiet_route": false
low_vision_support
boolean optional

Whether the route and destination environment provides specific support for low-vision users beyond standard signage — such as enhanced contrast markings on floor edges, door frames, and hazards; large-format room numbering; and colour-contrast way-markers. true unlocks a low-vision route variant in routing engines.

Standard: EN 17210 Requirement 6.1 — Contrast ratio: ≥ 3:1 for way-markers

"low_vision_support": true
crowd_avoidance_available
boolean optional

Whether a crowd-avoidance route to this destination has been modelled in the navigation graph — typically a staff corridor, secondary entrance, or quieter alternative path that bypasses the main public circulation. Used by routing engines for users who experience crowd anxiety, those recovering from surgery, or infection-control scenarios requiring physical distancing.

"crowd_avoidance_available": true
05 Information Accessibility 5 fields
high_contrast_signage
boolean optional

Whether high-contrast signage (meeting or exceeding a 4.5:1 luminance contrast ratio between text and background) is in use at this destination and on its primary route. A WCAG 2.2 AA requirement for digital content; the equivalent physical standard is EN 17210 Requirement 6.2. Enables routing engines to confirm signage compliance for low-vision user profiles.

Standard: EN 17210 Requirement 6.2 — Contrast ratio: ≥ 4.5:1 (text) · ≥ 3:1 (large text)

"high_contrast_signage": true
large_text_available
boolean optional

Whether large-print information materials (appointment letters, maps, leaflets) are available at this destination for users who have difficulty reading standard print. Typically means materials are available in 18pt+ font on request. Surfaced in kiosk and mobile channel output for users with a large-print preference profile.

Standard print size: 12pt — Large print: ≥ 18pt — Clear print: RNIB Clear Print Guidelines

"large_text_available": true
easy_read_available
boolean optional

Whether Easy Read versions of key destination information are available — materials using simple language, short sentences, and supporting images designed for people with learning disabilities, cognitive impairments, or those with limited literacy. Easy Read is a distinct format from plain language and from large print.

Governed by: Mencap Easy Read Guidelines — Distinct from: plain_language_available, large_text_available

"easy_read_available": false
plain_language_available
boolean optional

Whether all public-facing information at this destination uses plain language — short sentences, common words, active voice, and no unnecessary jargon. Affects how voice AI channel content is generated: when true, the channel renderer selects simplified language templates for routing instructions and announcements.

Standard: Plain English Campaign — Reading level: ≤ Grade 8 (US) / Year 9 (UK) target

"plain_language_available": true
multilingual_support
boolean optional

Whether multilingual wayfinding support is available at this destination — through multilingual staff, on-demand interpreter services, multilingual printed materials, or digital translation. When true, routing engines may surface this in output for users whose language preference differs from wim.language_default. Specific languages available are modelled in the channels object.

"multilingual_support": true
06 Facilities 4 fields
accessible_toilet_nearby
boolean optional

Whether a fully accessible toilet (meeting BS 8300 or equivalent dimensions and fixtures) is available within reasonable proximity of this destination. "Nearby" is context-dependent but typically within the same level or the nearest accessible lift journey. Routing engines surface this in output for users who require accessible toilet access as part of journey planning.

Standard: BS 8300 · EN 17210 Requirement 9 — Typically: same level or nearest accessible lift

"accessible_toilet_nearby": true
changing_place_nearby
boolean optional

Whether a Changing Places facility — a larger, fully equipped accessible toilet with a height-adjustable bench and ceiling hoist — is available near this destination. Changing Places are essential for people with profound and complex disabilities who cannot use a standard accessible toilet. Distinct from accessible_toilet_nearby.

Standard: PAS 1899:2022 · Changing Places Consortium — Minimum room size: 12 m²

"changing_place_nearby": false
resting_points_available
boolean optional

Whether seating or resting points (seats with armrests, or accessible bench seating) are available along the primary route to this destination. Critical for users with fatigue conditions, chronic pain, respiratory conditions, or those recovering from surgery. When true, the interval is specified in resting_point_interval_m.

Standard: EN 17210 Requirement 4.4 — Seat spec: armrests, back support, 450–480 mm height

"resting_points_available": true
resting_point_interval_m
integer optional

Maximum distance in metres between resting points (seats) on the primary route to this destination. Used by routing engines to assess whether the route meets the physical endurance requirements of a specific user profile. EN 17210 recommends a maximum interval of 50 m in public buildings. Null when resting_points_available is false.

Units: metres — EN 17210 recommendation: ≤ 50 m — Null when resting_points_available is false

"resting_point_interval_m": 50
07 Physical Dimensions 6 fields
maximum_slope
float optional

Maximum gradient (as a percentage) encountered on the primary route to this destination. Routing engines compare this against user profile slope tolerance — a gradient above 5% may be excluded from wheelchair routes; above 8% is impassable for most manual wheelchairs without assistance. Values drawn from the topology object's edge data.

Units: percentage — EN 17210 max (independent): 5% — Assisted max: 8%

"maximum_slope": 2.5
minimum_clear_width_m
float optional

Minimum clear path width in metres at the narrowest point on the primary route. Routing engines use this to verify route suitability: ≥ 0.9 m for manual wheelchair, ≥ 1.2 m for power wheelchair or mobility scooter, ≥ 1.5 m for two-way wheelchair passing. Values below 0.9 m block wheelchair routing to this destination.

Units: metres — Wheelchair min: 0.9 m — Two-way min: 1.5 m

"minimum_clear_width_m": 1.8
door_clear_width_m
float optional

Clear opening width of the primary entrance door to this destination in metres. Determines whether a wheelchair, scooter, or medical transport can pass through. Values below 0.9 m exclude this destination from wheelchair routing. This accessibility-level field references the destination's own door; edge-level door widths are in the topology object.

Units: metres — Wheelchair standard: ≥ 0.9 m — BS 8300 preferred: ≥ 1.0 m

"door_clear_width_m": 1.2
lift_available
boolean optional

Whether a lift (elevator) is available on the step-free route to this destination. true is required for step_free_route to be valid on any destination above ground level. Routing engines use this in conjunction with topology's nearest_lift field to confirm the vertical connection exists.

"lift_available": true
lift_dimensions
string optional

Internal floor dimensions of the lift serving this destination, expressed as width × depth. Used by routing engines to determine whether a specific mobility aid fits — a Class 3 scooter requires at least 1.1 m × 1.4 m internal space. Null when lift_available is false.

Format: "{width}m × {depth}m" — BS 8300 minimum: 1.1 m × 1.4 m

"lift_dimensions": "1.1m × 1.4m"
handrail_available
boolean optional

Whether continuous handrails are present on the primary route to this destination along corridors, ramps, and stairs. Handrails are required under EN 17210 Requirement 4.3 for any route with a slope, step, or change in level. true enables routing for users who depend on handrail support for balance and fatigue management.

Standard: EN 17210 Requirement 4.3 — Height: 900–1000 mm both sides on ramps and stairs

"handrail_available": true
08 Environmental Conditions 3 fields
surface_evenness
enum optional

Overall evenness of the floor surface on the primary route. An uneven surface increases wheelchair travel effort, may cause instability for ambulant disabled users, and creates a tripping hazard. Routing engines increase edge_weight on routes with uneven or highly_uneven surfaces for mobility aid profiles.

even mostly_even uneven highly_uneven
"surface_evenness": "even"
lighting_level
enum optional

General illumination level on the primary route and at the destination. Low lighting increases orientation difficulty for low-vision users, impairs sign legibility, and creates fall risk for ambulant disabled users. Routing engines use this when selecting routes for low-vision profiles — preferring routes with bright or adequate lighting.

bright adequate dim variable
"lighting_level": "adequate"
glare_risk
enum optional

Risk of disabling glare on the primary route — from bright windows, reflective floors, or poorly positioned artificial light sources. Glare is particularly problematic for low-vision users, cataract sufferers, and people with light sensitivity. Routing engines may deprioritise high-glare routes for sensitive visual profiles and surface a glare warning in channel output.

low moderate high
"glare_risk": "low"
09 Assistance 2 fields
assistance_required
boolean optional

Whether human assistance is required — or strongly recommended — to navigate the route to or within this destination independently. true causes routing engines to flag this destination as requiring escort arrangements and surfaces a prominent assistance notice in channel output. A true value does not suppress the destination from routing — it adds an assistance instruction.

Triggers: escort instruction in all channels — Does not suppress routing

"assistance_required": false
assistance_point_nearby
boolean optional

Whether a staffed assistance point (help desk, information point, or accessible customer service counter) is located within reasonable proximity of this destination. true enables routing engines to include an assistance point waypoint in routes for users who have flagged that they may need in-journey support. The assistance point itself is modelled as a separate WIM record with record_subtype: reception.

"assistance_point_nearby": true
Complete accessibility object — example

A fully populated Inclusive Routing object for the Cardiology Clinic at UMC Utrecht. Required fields always present; optional fields shown with representative values.

accessibility-dept-cardiology-001.json