Accessibility.
We build this to WCAG 2.1 level AA. Here is what that means, what we have actually tested, and where we know we fall short.
Last updated 25 August 2026
The standard we hold ourselves to
WCAG 2.1 level AA, the international standard, on this website and on the pages our customers publish. In practice that means the following, and each of these is checked rather than assumed.
- Text has enough contrast against its background to be read in daylight on a phone.
- Everything works with a keyboard alone, with a visible outline showing where you are.
- Every image either describes itself or is marked as decoration so a screen reader skips it.
- Headings are in order, so somebody navigating by heading gets a real outline of the page.
- Buttons and links say what they do when read on their own. No click here.
- Buttons, form fields and menu controls are at least 44 by 44 pixels. A link inside a sentence or a list of links is at least 24 pixels tall with clear space around it, which is what WCAG 2.2 asks for. This matters here because these pages are used one handed.
- Nothing important is shown by colour alone.
- Animation respects the setting on your phone that asks for less motion.
How we check
- An axe check against WCAG 2.1 A and AA, run by hand before a change ships, at a desktop size and a phone size. Wiring it into the build so it cannot be skipped is on the list below.
- Keyboard walkthrough of every new page before it is called done.
- Contrast maths on every colour pair, rather than eyeballing it.
- Screen reader spot checks on the parts that matter most: making a page, and the enquiry list.
- Last audit
- 25 August 2026
- What was tested
- The landing page, in three combinations: 1440 by 900 in light, 1440 by 900 in dark, and 390 by 844 in light
- Result
- Zero axe violations in all three
- The caveat
- Automatic tools cannot test everything. The next section is what they missed and what we found by hand.
What we know is not right yet
Kept current. When one of these is fixed it comes off the list.
- Most pages have only had automatic checks, not a full screen reader walkthrough.
- A phone at 390 pixels wide has not been checked in dark mode. The automatic run covers desktop in light and dark and a phone in light, and that fourth combination is missing.
- The axe check is run by hand rather than by the build, so a change can ship without it.
- Dark mode has not had the same contrast review as light mode, and the accent colour shifts more than it should.
- Photographs uploaded by our customers do not always have alt text, because we cannot write it for them. We prompt for it and we do not force it, which is a choice we are still arguing about internally.
- The editor has not been tested with voice control software.
The pages people build with us
We can build accessibility into the parts we control, and we do. Colours, spacing, headings, focus outlines and tap targets are set by us, not chosen per page, which means every page starts accessible.
What we cannot control is what somebody types and uploads. If a customer writes a heading in all capitals or uploads a photo of text, that page will be harder to use, and it is not something we can fix from here. What we do is prompt for alt text on every image, warn when a heading is being misused, and keep the templates good enough that the default is the accessible option.
If we have got something wrong
Tell us, with as much or as little detail as you have. The button on the pricing page does not work with my screen reader is enough to start. You do not need to know the standard or the terminology. Message us on WhatsApp with accessibility in the subject.
- First
- We reply and tell you whether we can reproduce it
- Then
- A fix, or a date for one, and a workaround if there is one
If it is blocking you from doing something today, say so, and we will find you a way round it by hand while we fix the real thing. We reply within two working days.
The formal bits
- Standard
- WCAG 2.1 level AA
- Conformance claim
- Partially conformant, with the exceptions listed above. The full site has not yet been audited end to end.
- Assessed by
- CodeEdge Tech and Ventures Private Limited, internally
- Statement prepared
- 25 August 2026
This has not been assessed by an outside auditor. When it has, this section will say who did it and when.