Last reviewed 26 October 2026
Accessibility.
A voice company should be understandable in more than one mode. This statement describes what we have built, what we have tested and where we still have work to do.
Mark the subject “Accessibility”.
Our commitment
We want this site and the client portal to be usable by people with different vision, hearing, motor and cognitive needs. Accessibility is part of the build, alongside performance and security, not a separate project after launch.
This statement covers the public website and the client portal. It does not cover third-party sites we link to, or a client's own systems that we integrate with.
Conformance target
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We aim to meet it across the public pages and the portal. We have not commissioned an independent third-party audit; this statement describes our current practice and testing, and we will update it if an audit changes the position.
What we have done
- Semantic HTML landmarks, one main region and a skip link on every page.
- Keyboard access to navigation, the mobile menu, forms, the password toggle and the portal.
- Visible focus styles that do not rely on colour alone.
- Text and background colour combinations checked against WCAG contrast thresholds.
- Text that reflows at 200% zoom and a responsive layout down to narrow mobile widths.
- Reduced-motion support; no autoplaying audio or video.
- Form labels, descriptions, required fields and error messages announced to assistive technology.
- Text alternatives or text summaries for technical diagrams; decorative graphics are hidden from screen readers.
- No third-party tracking scripts, pop-ups or interstitials blocking the page.
Known limitations
- Technical diagrams. The rack, locator and signal diagrams are illustrative. The surrounding text and tables carry the same information, but the visual form may be harder to parse for some readers.
- Third-party destinations. Map links and external sites are outside our control and may not meet the same standard.
- Portal coverage. The portal is tested with keyboard navigation, zoom and automated checks. It has not yet had a full screen-reader audit across every browser and assistive technology combination.
- Older content. A note published before a design change may use an older component. We fix issues when we find them; tell us if we miss one.
Feedback
If a page is hard to use, or you need information in another format, use the contact form with “Accessibility” in the message. Tell us the page, the browser or assistive technology you are using, and what happened. We aim to reply within five business days.
If you are a client and the issue affects the portal, include your organisation and the time you saw the problem. Do not include passwords or call data in the message.
Accessibility contact
Aldaria
Accessibility contact form
Last reviewed 26 October 2026