Trust
Accessibility Statement
We aim at WCAG 2.1 Level AA. This page says what we have actually done, what we know is still imperfect, and how to report anything that blocks you.
What is in place
- Colour contrast checked, not assumed. Body text and every button were measured against the WCAG AA threshold of 4.5:1. Our green buttons were failing at 3.37:1 and were darkened until they passed at 4.84:1.
- Keyboard navigation throughout. Every menu, dialog, accordion and form can be reached and operated without a mouse, with a visible focus ring on each.
- Touch targets at least 44px on phones, with real spacing between them.
- A single, correct heading order on every page — one H1, no skipped levels — so screen reader users can navigate by structure.
- Text that reflows. No horizontal scrolling from 320px upwards, and text scales without breaking layout.
- Labelled form fields with hints tied to the input, not floating placeholders that vanish when you type.
- Reduced-motion respected. If your system asks for less animation, transitions are switched off.
- Dark mode with its own contrast values rather than an inverted palette.
What still falls short
Being straight about this is more useful than a clean claim:
- No third-party audit. Everything above is our own testing. We have not paid for an independent WCAG assessment.
- Limited assistive-technology testing. We test with keyboard and browser tooling. We have not tested every page with every screen reader.
- Some tool output is inherently visual. The QR generator and logo maker produce images; the underlying data is available but the preview itself is not describable in text.
- Older blog articles predate this standard and are being brought up as they are revised.
Telling us about a barrier
Email [email protected] with the page address and what you could not do. You get a reply within one business day, and a fix or a date.
If you need something on this site in another format — a document read out, a policy as plain text — ask and we will send it. There is no process to go through.
Accessibility on your project
Every site we build gets the same baseline: real contrast ratios, keyboard operation, focus states and labelled fields. It is included rather than sold as an extra, because a site people cannot use is not finished. See web development.