Accessibility Statement
Last reviewed 14 June 2026 · Privacy Policy · Terms of Service · Accessibility
1. Our commitment
Building Digital Limited wants Validate to be usable by as many people as possible, including those who rely on assistive technologies such as screen readers, keyboard-only navigation, or browser zoom. Accessibility is part of how we judge whether a feature is finished, not an afterthought.
2. Standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is the standard widely referenced by UK public-sector and main-contractor procurement. We design with semantic HTML, labelled form controls, visible focus states, sufficient colour contrast, and keyboard operability in mind across the platform and the engineer field app.
3. How we test
Accessibility checks run automatically as part of our continuous-integration pipeline: an automated WCAG sweep (axe-based) runs against key pages on every release. Automated tools catch a meaningful share of issues but not all of them, so we also test common flows with keyboard navigation. We have not yet commissioned a formal independent WCAG 2.2 AA audit; we are honest that our conformance is "substantially conformant" rather than fully certified.
4. Known limitations
Some areas of Validate are richer and harder to make fully accessible, and we are actively improving them. Known limitations include: complex data-dense views such as the Gantt-style programme and some commercial tables, which can be difficult to navigate by screen reader; certain generated PDF outputs, which may not yet be fully tagged for assistive technology; and a small number of legacy interactions still being migrated to our current accessible component library. If any of these block you, please contact us and we will help directly while we improve them.
5. Reporting a problem
If you encounter an accessibility barrier in Validate, we want to hear about it. Email accessibility@validate.software (or hello@validate.software) describing the page, what you were trying to do, and the assistive technology or browser you were using. We aim to respond within 5 working days and will work with you to provide the information or function you need in an accessible form.
6. Enforcement
If you contact us about an accessibility problem and are not satisfied with our response, individuals in the UK can contact the Equality Advisory and Support Service (EASS). We will always try to resolve issues directly with you first.
7. Review
We review this statement and our accessibility approach periodically and when we ship significant changes. This statement was last reviewed on 14 June 2026.