Accessibility
What we have built into this site for accessibility, what we have not verified, and how to tell us when something does not work.
Effective
20 August 2026
Last updated
20 August 2026
We want anyone to be able to read this site and use everything on it, whatever they are reading it with.
This page sets out what we have done, what we have not checked, and how to reach us if you hit something that does not work. It describes this website. Our products are separate services and each needs its own statement.
What we aim at#
We build to the Web Content Accessibility Guidelines version 2.2 at level AA. That is the target we design and review against.
We are not claiming to meet it. Nobody outside Anquin has audited this site, and until someone has, a conformance claim would be a guess dressed up as a result.
What we have done#
These are properties of the site as it is built today, not intentions.
- Colour contrast is calculated as part of the build, from the palette itself. Every text pair clears the AAA threshold of 7 to 1, and the edge of every control clears the 3 to 1 required for non text contrast. A colour that falls short stops the build rather than reaching a page.
- Every interactive element works from the keyboard alone. Menus open on focus, close on Escape, and return focus to the control that opened them.
- A skip link is the first thing in the tab order on every page, so you can jump past the header to the content.
- Focus is always visible, and never removed to tidy up a design.
- Headings follow the document structure. One first level heading per page, and no level skipped to get a particular size.
- Links in body text are underlined rather than shown by colour alone.
- Images that carry meaning have alternative text. Decorative artwork is hidden from screen readers instead of being given a description that adds nothing.
- Motion is a layer on top of a page that already works. If your system asks for reduced motion, animation is switched off and nothing disappears with it.
- Text resizes and reflows with the browser, and the site works at narrow widths and high zoom.
- Pages are ordinary server rendered HTML, so they work with an assistive technology reading the document directly.
What we have not checked#
Being straight about the gaps is the point of publishing this.
- No independent accessibility audit has been carried out.
- We have not completed structured testing with screen readers, voice control, or switch access, so we cannot tell you how the site behaves with a specific one.
- We have not tested with people who use these tools daily, which is the test that finds what automated checks miss.
- The blog and any future content pages depend on whoever writes them adding good alternative text and sensible headings. That is a process we still need to prove.
We intend to close these gaps rather than leave them stated. Until an audit has happened, this section stays exactly as it reads: a list of what we have not done, not a promise about when.
Telling us about a problem#
If something on this site is hard or impossible to use, please tell us at contact@anquin.com. It helps if you can say which page, what you were trying to do, and what you were using, but send it even if you cannot.
We read every one of these and we will tell you what we are doing about it. If you need something on this site in another format, ask and we will get it to you.

