Accessibility
Built to be usable by everyone
What we have done to make this site accessible, what we know is still missing, and how to tell us when we have got something wrong.
On this page
Draft — not yet in force
Unreviewed draft
This document is a structural skeleton, not legal advice, and it does not yet describe how this business actually operates. The highlighted passages mark decisions only you can make. Have a qualified lawyer review it before this site goes live — see src/content/legal.ts to edit the text.
What we are aiming for
We are working towards WCAG 2.2 Level AA on this site — the benchmark US courts and the Department of Justice look to when applying the Americans with Disabilities Act to websites.
That is a target we are building against, not a conformance claim: no independent audit has been carried out yet, so we cannot and do not state that the site conforms.
ONCE AN AUDIT HAS BEEN DONE, REPLACE THIS SECTION WITH A PROPER CONFORMANCE STATEMENT — the standard, the level, the date, who assessed it, and the scope of pages covered. If you sell to federal agencies, Section 508 applies too and you will need a VPAT.
What is in place today
These are measures actually built into the site, not intentions:
- A skip link to the main content as the first focusable element on every page.
- Semantic landmarks — header, nav, main and footer — so screen readers can navigate by region.
- Menus that open on keyboard focus as well as hover, with the open state exposed via aria-expanded.
- Breadcrumbs marked up as a navigation landmark, with the current page flagged by aria-current.
- Decorative graphics hidden from assistive technology, and meaningful images given text alternatives.
- Animation that respects the operating system's reduce-motion setting.
- Form fields with real labels, and icon-only buttons with accessible names.
Known limitations
We would rather list these than let you discover them:
- The site has not been tested end to end with screen readers or by disabled users. Run that testing and record what it found.
- Colour contrast has not been formally verified against the 4.5:1 threshold across every state, including hover and focus styles on the navy panels.
- The mega-menu has not been validated against the WAI-ARIA authoring practices for disclosure navigation.
- ADD ANYTHING ELSE YOU FIND. A known-issues list that never grows reads as one nobody maintains.
Tell us about a barrier
If something on this site blocked you, we want to hear about it — including which page, what you were trying to do, and the browser or assistive technology you were using. That detail is usually what makes a fix possible.
Questions about this document can go to CONTACT_EMAIL, or through the form on our contact page. We aim to respond within RESPONSE_WINDOW, e.g. five business days.
NAME A RESPONSE COMMITMENT AND AN ESCALATION CONTACT HERE. A documented, honoured response process is among the strongest defences against an ADA website claim — and several states impose their own deadlines on top.
Looking for something else? Get in touch.
Tell us what you are trying to build
A short call with an engineer, not a sales team. If we are not the right fit we will say so and point you somewhere better.