Built to be used by everyone who handles confidential work.
The people we build for do not all read, see or move the same way. This page sets out what we do to make Hush usable for as many of them as possible, and how to tell us when we fall short.
We work to WCAG 2.2 AA.
We aim to meet the Web Content Accessibility Guidelines version 2.2 at level AA, the standard UK public-sector and NHS organisations look for. We are an early-stage company and we treat accessibility as ongoing work rather than a box already ticked, so this statement describes what is in place today and what we are still improving. If a page falls short, we want to know, and we fix it.
Features you can use right now.
- A dyslexia-friendly reading mode that changes the typeface and spacing to make text easier to read, saved for your next visit.
- Light and dark themes, so you can choose the contrast that is comfortable for you.
- Keyboard navigation. The site and its menus can be reached and operated without a mouse, and a skip-to-content link lets you jump straight past the menu.
- Semantic, structured markup with real headings, landmarks and link text, so screen readers can make sense of each page.
- Text that scales. You can zoom or increase text size in your browser without the layout breaking.
- Descriptive alternatives for meaningful images, and plain, specific link text rather than "click here".
- Fast, lightweight pages. The site is built as static HTML, so it loads quickly on modest devices and slow connections.
These are not bolt-ons. The same choices that make a page accessible, clear structure, honest headings and readable text, are the choices that make it work well for everyone, including the AI assistants your colleagues now use to find tools like ours.
Honest about the gaps.
We have not yet commissioned a full independent WCAG 2.2 AA audit, so we describe the site as partially conformant and actively improving. As we add pages and features we test them for keyboard access, contrast, focus visibility and screen-reader clarity, and we prioritise fixes that affect real use over cosmetic ones. If you rely on assistive technology and something does not work, your report goes to the top of that list.
If something does not work, email a person.
Write to [email protected] with the page and what went wrong, and a person will read it and reply. We treat accessibility problems as bugs, not suggestions, and we will tell you what we are doing about it and when.
This statement was last reviewed in July 2026. We will update it as the site changes.