Accessibility
Last updated: 9 June 2026
This statement covers the public website at usebluewave.com. The BlueWave platform itself — the office app and the engineer app — will get its own assessment; ask us if you need it for procurement.
Our target
We aim for WCAG 2.2 level AA across this site. We'll say plainly what that aim is worth today: we haven't yet completed a formal WCAG audit, so we don't claim conformance — we claim the target, the engineering below, and a commitment to fix what you find.
What's built in
- Visible keyboard-focus indicators on every interactive element, implemented so they survive Windows High Contrast mode
- A colour palette with text contrast checked against WCAG AA
- Reduced-motion support: animations effectively stop when your system asks for less motion
- Semantic structure — one main heading per page, logical heading order, landmarks, descriptive link text and image alt text
- A keyboard-operable mobile menu that traps focus while open and closes on Escape
Known limitations
None confirmed yet — which mostly reflects the absence of a formal audit rather than perfection. When the audit happens, this section gets honest entries and dates.
⚠ For review: Run at least an automated pass (axe/Lighthouse) plus a keyboard and screen-reader walkthrough before launch, and record findings here. "None confirmed" must not survive contact with an actual audit.
Found a problem?
Tell us at accessibility@usebluewave.com [pending mailbox] — what you were doing, the page, and the assistive tech or browser involved. Accessibility reports get treated like defects, not feedback: triaged and fixed.
Review
We'll review this statement when the site changes materially and at least annually, updating the date at the top.