Accessibility statement for SimplyWayfinding

SimplyWayfinding is a hospital-site wayfinding application designed to help patients, visitors, carers, volunteers and staff find their way around hospital sites.

SimplyWayfinding has been designed with accessibility in mind. It includes written directions alongside the visual map, supports browser zoom, is designed so that route information does not rely on colour alone, and provides an option to avoid known stair connections.

Some features have not yet been fully tested with assistive technologies, and known limitations are described below.

Compliance status

SimplyWayfinding is being assessed against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

The application has not yet been assessed sufficiently to determine a formal compliance status. We therefore do not currently claim that it is fully or partially compliant with WCAG 2.2 AA.

Known accessibility limitations

We are aware of the following accessibility limitations.

  • Some visual map node actions are pointer-based and are not currently exposed as keyboard-focusable controls. The main workaround is to use the Start location and Destination search fields instead of tapping the map. This affects interactive map-node actions. Further keyboard testing is needed to confirm whether the search fields provide equivalent access for all map-node functions.

Areas not yet fully tested

The following areas are not being presented as confirmed defects. They still need fuller accessibility testing before any compliance claim is made:

  • complete keyboard-only route planning;
  • VoiceOver on Apple devices;
  • NVDA on Windows;
  • autocomplete interaction with screen readers;
  • route-change announcements;
  • focus restoration for dialogs and panels;
  • 200% zoom and increased text spacing;
  • Windows forced-colour and high-contrast mode;
  • offline and service-worker update states;
  • error messages;
  • QR entry and route-generation journeys.

The visual map is not intended to be the only way to understand a route. Written route instructions are provided when a route is generated.

Digital and physical accessibility

This statement principally concerns the accessibility of the SimplyWayfinding digital service.

The stair-free option avoids known stair connections in the map data. It does not confirm that lifts, doors or corridors are currently available or that a route will meet every individual accessibility requirement.

Physical signs, barriers and instructions from hospital staff should take priority over digital route guidance.

If you cannot use the application

If you need immediate help finding your way while at a hospital, ask a member of staff, receptionist or hospital volunteer.

If you cannot access information provided by SimplyWayfinding, email info@simplywayfinding.com and tell us what information you need and the format that would help you.

Reporting accessibility problems

You can report an accessibility problem through the Give feedback option or by emailing info@simplywayfinding.com.

We will review accessibility reports and respond where contact details are provided.

It is helpful, but optional, to include:

  • the hospital site or page you were using;
  • the task you were trying to complete;
  • your device and browser;
  • any assistive technology you were using;
  • a description of the problem.

Complaints and escalation

If you are not satisfied with the response to an accessibility report, you can reply to the response you received or contact info@simplywayfinding.com and ask for the issue to be reviewed.

Scope of this statement

This statement covers:

  • the public route-planning application;
  • public Privacy, Terms and Accessibility pages;
  • the public feedback interface;
  • other public landing or hospital-selection pages included in the production service.

How we test the application

Testing and review completed so far includes:

  • code and semantic review of public pages and application components;
  • inspection of headings, landmarks, form labels, controls and accessible names;
  • review of autocomplete, route announcements and focus-handling code;
  • automated checks on selected public pages using WAVE and browser accessibility tools;
  • production build and responsive-layout checks.

Automated tools can help identify issues, but they do not establish WCAG compliance on their own.

Further testing is planned, including:

  • repeatable keyboard-only testing;
  • VoiceOver testing on Apple devices;
  • NVDA testing on Windows;
  • testing at 200% browser zoom and with increased text spacing;
  • Windows forced-colour and high-contrast testing;
  • testing of route generation, error states, QR-code entry and offline use;
  • a fuller WCAG 2.2 AA assessment before making a formal compliance claim, with independent review considered when appropriate.

Preparation of this statement

This statement was prepared on 15 July 2026.

Last reviewed: 27 July 2026.

Accessibility is being reviewed throughout development, and this statement will be updated as testing evidence and service scope change.