SimplyWayfinding
Simple navigation for complex places
SimplyWayfinding is a hospital-site wayfinding application designed to help patients, visitors, carers, volunteers and staff find their way around hospital sites.
This statement applies to the public SimplyWayfinding service, including the route-planning interface, public hospital-selection pages, feedback interface, Privacy, Terms and Accessibility pages.
When SimplyWayfinding is accessed in the context of a particular hospital, the service also shows relevant hospital and organisation contact routes.
The service provides written route instructions alongside the visual map, supports keyboard navigation and browser zoom, does not rely on colour alone to communicate route information, and provides an option to avoid known stair connections.
SimplyWayfinding is being assessed against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
Extensive self-assessment has been completed across the core public journey, including keyboard-only navigation, NVDA screen-reader testing, responsive-layout testing, browser zoom and reflow testing, and automated accessibility checks.
The current assessment has not identified an unresolved accessibility issue that prevents completion of the core tested public journey. VoiceOver, text-spacing, Windows forced-colour and high-contrast, additional route and QR-entry scenarios, and final automated retesting remain outstanding.
We therefore do not yet claim full WCAG 2.2 AA compliance. This statement will be updated when the remaining assessment work is complete.
Keyboard-only and NVDA testing of the core route-planning journey confirmed that users can:
Keyboard focus follows the main route-planning task sequence, and no keyboard traps were identified in the tested public journey. NVDA testing confirmed that the tested page structure, route controls, status and instructions, stair-free state, floor information, menus and representative feedback journey were understandable through a screen reader.
The visual map is not required to create or understand a route. Users can select a start location and destination using the route-planning controls, and written directions are provided when a route is generated.
Individual graphical map nodes are intentionally excluded from the normal keyboard focus order. This avoids requiring keyboard and screen-reader users to navigate a large number of graphical map objects when an equivalent route-planning and written-directions interface is available.
Testing covered desktop, tablet and mobile layouts, 200% desktop browser zoom, a desktop reflow test at approximately 320 CSS pixels, and increased magnification on an iPhone.
At 200% zoom, the tested public journey remained functional and practical. At 300% mobile magnification and the 400% desktop equivalent, it remained operable in the scenarios tested but required substantially more scrolling and context switching.
The visual map is inherently two-dimensional, but route controls and written directions allow users to create and understand a route without interacting with the map. Narrow-screen issues affecting route controls, menus and the feedback dialog were identified and corrected during testing. A final post-remediation narrow-width route test remains planned.
NVDA testing was completed on Windows 11 for a representative public journey. It covered page structure and landmarks; start and destination autocomplete; destination directories; route generation, status and steps; stair-free routing; full written directions; floor changes; hospital information; menus; and a representative feedback journey.
Testing led to simpler route-planning landmarks, shorter autocomplete speech, contextual route controls, removal of duplicate announcements, clearer spoken direction and floor information, simpler floor-selector semantics and removal of a duplicate form landmark from the feedback dialog.
VoiceOver testing on Apple devices remains outstanding and will be completed before the accessibility assessment is treated as complete.
You can report a technical accessibility problem with SimplyWayfinding using the Report a problem option within the service. You can also report a product accessibility problem by emailing info@simplywayfinding.com.
The feedback form uses predefined choices and does not ask for free-text comments, names, email addresses, telephone numbers or file uploads. We review these reports to identify and correct problems, but cannot reply individually through the form.
If you need information in another format, individual accessibility assistance, a response to an accessibility enquiry, or help that cannot be described using the structured choices, use the hospital contact information shown below when a hospital context is selected.
If you need immediate help finding your way while at the hospital, speak to a member of staff, receptionist or hospital volunteer. The feedback form is not monitored continuously and should not be used for emergencies or immediate assistance.
See the Privacy notice for information about the limited technical and route context that may be included with a feedback submission.
For , accessibility assistance, information in another format and individual responses are provided by .
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, corridors, doors or other physical routes are currently available, nor does it guarantee that a route will meet every individual accessibility requirement. Physical signs, temporary restrictions and instructions from hospital staff should take priority over digital route guidance.
The service was tested between 16 and 17 September 2026. Testing included:
Issues corrected during the assessment included route-control order, redundant landmarks, duplicate screen-reader announcements, mobile control positioning, narrow-screen panel sizing and hidden implementation controls.
The initial WAVE review of the public route page reported no contrast errors and no alerts. Two markup-related errors were reviewed and remediated. A post-remediation rerun is planned. Automated tools are supporting evidence and do not establish WCAG compliance on their own.
The following assessment work remains planned:
These outstanding checks are not currently being presented as confirmed accessibility defects.
At very high magnification, the service requires more scrolling and context switching because significantly less of the interface is visible at once.
The graphical map remains a two-dimensional visual representation. Users who cannot or do not wish to interact with it can use the route-planning controls and written route instructions instead.
No unresolved release-blocking accessibility failure has been identified in the keyboard-only, representative NVDA, responsive-layout or zoom testing completed so far. This does not yet constitute a full WCAG 2.2 AA conformance assessment.
If you are not satisfied with how a SimplyWayfinding accessibility issue has been handled, email info@simplywayfinding.com and ask for the issue to be reviewed.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
If you are not happy with how your accessibility complaint has been handled, you can contact the Equality Advisory and Support Service (opens in a new tab).
This statement was first prepared on 15 July 2026.
It was last reviewed on 17 September 2026.
The current statement is based on SimplyWayfinding self-assessment testing completed principally between 16 and 17 September 2026. It will be updated as the remaining planned accessibility testing is completed and when new hospital sites or significant features are introduced.