This statement explains how accessible the spanSense platform and the spanSense Field companion app are, any known limitations, and how to get in touch if you have difficulty using them.
spanSense Ltd · Registered in England and Wales, company no. 17464577 · Registered office: 8 Howard Street, Reading, RG1 7XS
1.1spanSense Ltd is committed to making the spanSense web application and the spanSense Field companion app (together, the "Service") accessible to as many people as possible, including people who use assistive technology such as screen readers, screen magnification, speech recognition, or keyboard-only navigation.
1.2We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This statement sets out where we currently meet that aim, where we do not yet, and what we are doing about it.
2.1This statement covers the spanSense web application (used by inspectors, engineers and asset managers to record, review and report on structure inspections) and the spanSense Field companion app (used on site during inspections).
2.2Some content is supplied by Customers themselves — for example, uploaded photographs, free-text inspection notes, and attached documents — and is outside our direct control. We nonetheless design the Service so that this content can be accessed and reviewed using assistive technology.
4.1We have not yet completed a formal, independent WCAG audit of the Service. Based on our own internal review, the known limitations at the time of writing are:
| Area | Limitation |
|---|---|
| Custom interactive controls | Some custom dropdowns, modals and toggles do not yet have complete ARIA labelling, so their state (open/closed, selected value) may not always be announced correctly by a screen reader. |
| Complex data views | Some data-dense views (for example, structure and inspection tables) have not been separately tested with screen readers for logical reading order. |
4.2These are genuine, currently-known gaps rather than an exhaustive list. We expect to identify further issues as testing continues.
5.1We are addressing the limitations listed in Section 4 as part of our ongoing development, prioritising fixes that affect core inspection and reporting workflows.
5.2We intend to carry out a fuller accessibility audit against WCAG 2.1 AA and will update this statement with the results once complete.
6.1spanSense is partially conformant with WCAG 2.1 AA. "Partially conformant" means some parts of the Service do not yet fully conform to the standard, as described in Section 4.
6.2The Service is tested using current versions of major desktop and mobile browsers (Chrome, Edge, Safari, Firefox). Assistive technology compatibility has been checked informally rather than via a formal audit.
7.1If you find any part of the Service that you cannot access, or if you need information in a different format, contact us at [email protected]. Please describe what you were trying to do and which page or screen you were using, so we can investigate.
7.2We aim to acknowledge accessibility feedback within 5 working days.
8.1Where the Service is used by a public sector body in the course of its own public-facing duties, that organisation remains responsible for its own compliance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This statement is provided to support that organisation's own assessment and, where relevant, its own accessibility statement.
8.2If you are not satisfied with our response to an accessibility concern, individuals may be able to contact the Equality Advisory and Support Service (EASS) for advice, or the relevant body's own complaints process where applicable.
9.1This statement was prepared on 4 August 2026, based on an internal review of the Service rather than a formal external audit.
9.2We will review and update this statement at least annually, or sooner if a formal audit is completed or significant changes are made to the Service.