Why accessibility in digital wayfinding goes beyond compliance, and what it takes to get right.

When someone cannot find where they need to go in a hospital, it is not a minor inconvenience. For a patient navigating to an unfamiliar clinic, for an elderly visitor trying to find a ward, for someone with a vision impairment using a kiosk for the first time, a poorly designed wayfinding system does not just frustrate. It causes real harm.
Accessible digital wayfinding is not a legal obligation you design around. It is the central brief — and it applies to every hospital, shopping centre, and government building Envent works in.
The common framing: accessibility provides all people, regardless of capacity, equal opportunity to engage with digital wayfinding. That is correct, but it is too narrow.
Accessibility is not only about permanent disability. A person with a broken arm cannot use a standard touch interface comfortably. Someone in a noisy shopping centre cannot hear audio cues. A hospital visitor who is anxious, tired, or unfamiliar with technology runs into difficulty with systems that assume a certain baseline of capability.
Design for the 10% who need it most. The other 90% benefits automatically.
Designers do not just build what the brief asks for. They carry a responsibility to every person who will eventually use what they build.
In Australian wayfinding design — whether for hospitals, shopping centres, or council buildings — the DDA (Disability Discrimination Act) has to be part of the designer's thinking from day one, not reviewed at the end. It cannot be a compliance checklist applied after the core design is finished. By that point, the structural decisions have already been made, and retrofitting accessibility is expensive, incomplete, and visually compromised.
The DDA has to be part of the designer's psyche. Not their checklist.
Accessible UI/UX expands the usable audience for a wayfinding system, not just to people with disabilities, but to anyone whose capacity to interact is temporarily or contextually reduced.
That means high-contrast display modes for low vision, adjustable text size, screen reader compatibility, clear visual hierarchy, logical interaction sequences, and interfaces that do not punish hesitation or slow response. It also means testing with real users, not just running an automated accessibility audit.
WCAG 2.0 Level AA is the minimum benchmark. It covers perceivability, operability, understandability, and robustness. These are not four bonus features. They are the four conditions a usable interface has to meet.
Ergonomics is where wayfinding accessibility becomes a physical design problem.
A kiosk usable only while standing excludes every wheelchair user. A screen positioned for a tall standing adult is unreachable for a child or someone using a mobility aid. The answer is not two kiosks. The answer is the accessibility overlap: a design zone simultaneously within reach for both seated and standing users.
This overlap sits between approximately 700mm and 1200mm from floor level. All primary controls, the touchscreen, the key UI elements, the interactive zones, belong within that range. Secondary information can exist above it. Nothing critical should exist only outside it.
This gets engineered into the kiosk enclosure before production, not retrofitted afterward.
Four Australian standards apply to accessible wayfinding design:
AS1428.1 (2009) covers general requirements for access and mobility.
AS1428.2 (1992) covers enhanced and additional requirements.
AS1428.4.2 (2018) covers tactile ground surface indicators.
WCAG 2.0 Level AA covers the digital interface layer.
For hospitals and government buildings where formal certification is required, obtaining a Disability Access Design Compliance Certificate is worth pursuing from the outset.
For healthcare wayfinding specifically, the combination of AS1428 physical standards and WCAG 2.0 Level AA digital standards is what defines a fully compliant accessible wayfinding system.