Accessibility Statement
Last reviewed: April 2026 · Next review due: April 2027
1. Our commitment to accessibility
Datumbase is used by construction professionals to manage CDM compliance documents — including Health & Safety Files that must remain accessible to building owners for the life of a structure. We believe the application itself should also be accessible to everyone who needs it, including users with disabilities.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the application.
2. Compliance status
Datumbase is partially compliant with WCAG 2.1 AA. The areas below describe current status and known limitations.
| Area | Status | Notes |
|---|---|---|
| Keyboard navigation | Meets criteria | All core journeys (sign in, site navigation, document upload, CDM forms) are operable by keyboard alone. |
| Focus management | Partially meets | Focus indicators are visible on most interactive elements. Some custom section-navigation tabs in CDM forms have reduced focus visibility — flagged for Q3 2026. |
| Colour contrast | Partially meets | Main content meets 4.5:1. Some secondary labels (file metadata, muted text) sit at approximately 3:1 — under AA threshold. Under review for Q3 2026. |
| Screen reader compatibility | Partially meets | Tested with VoiceOver (iOS/macOS) and NVDA. Core content reads correctly. Multi-step form progress state is not fully exposed to all screen readers — planned Q4 2026. |
| Text resize & zoom | Meets criteria | Content is readable and functional at up to 200% browser zoom without horizontal scrolling on standard viewports. |
| Images & non-text content | Meets criteria | Decorative icons use aria-hidden. Functional icons have accessible labels or visible text. |
| Forms & error messages | Meets criteria | Fields use associated <label> elements. Required fields are marked. Errors are programmatically linked to their fields. |
| Page titles & headings | Meets criteria | Each page has a unique <title>. Heading hierarchy is logical throughout. |
| Links & buttons | Meets criteria | All links and buttons have descriptive accessible names. No "click here" or ambiguous labels. |
| Video & audio | Not applicable | No video or audio content is used in the application. |
| Session timeout | Meets criteria | Sessions are long-lived. No automatic timeout disrupts screen reader users mid-task. |
| Mobile / responsive | Meets criteria | Responsive from 375px upward. All functionality is available on mobile viewports. |
3. Known accessibility issues
- Colour contrast on secondary text — muted metadata labels in the document library are at approximately 3:1 contrast. Target: raise to 4.5:1. Planned Q3 2026.
- Focus visibility on multi-step form tabs— section navigation tabs in the F10 and H&S File forms have a reduced focus ring. Planned Q3 2026.
- ARIA progress state on multi-step forms — current step and total steps are visually shown but not fully programmatically exposed. Planned Q4 2026.
4. Tested assistive technologies
- VoiceOver + Safari (macOS Sequoia)
- VoiceOver + Safari (iOS 17)
- NVDA + Firefox (Windows 11)
- Keyboard-only navigation (Chrome, Safari, Firefox)
- Keyboard-only navigation + 200% zoom (Chrome)
5. What to do if you cannot access content
If you need content in a different format or have found an accessibility barrier, please contact us:
- Email: hello@datumbase.tech
We will acknowledge within 2 business days and aim to respond within 10 business days. If we cannot make content directly accessible, we will provide a reasonable alternative.
6. Enforcement procedure
Datumbase is a commercial SaaS product and is not subject to the Public Sector Bodies Accessibility Regulations 2018. However, we are committed to an accessible service for all users.
If you are unhappy with our response, you can contact the Equality and Human Rights Commission (EHRC) if you feel your rights under the Equality Act 2010 have not been met.
7. How this statement was prepared
This statement was prepared in April 2026 by Brockhurst Property Ltd through a combination of manual keyboard and screen reader testing, and visual review against WCAG 2.1 Level AA. A formal independent accessibility audit is planned before our first enterprise customer. This statement will be updated to reflect audit findings.