Our commitment
We want everyone to be able to use zenlio.io, including people who use a screen reader, navigate by keyboard, zoom in, or find low-contrast text hard to read. We build websites for other businesses and tell them accessibility matters, so we hold our own site to the same standard.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We don't fully meet it yet. This page explains what works, what doesn't, and what we're doing about it.
How we checked
On 10 October 2026 we ran automated checks across every page on the site, 145 in all. The checks covered colour contrast (including text on dark and gradient backgrounds), image text alternatives, form labels, link and button names, heading structure, page language, duplicate IDs and whether zooming is allowed. We fixed what they found the same day, then ran them again.
Automated checks only catch part of the picture. We haven't yet had the site tested by disabled users or with a full manual screen reader and keyboard audit. We'll update this page when we have.
What we fixed in October 2026
- We darkened our orange brand colour so text and buttons meet the 4.5:1 contrast ratio on our cream and white backgrounds, and used lighter versions of the orange and the Studio blue on dark sections.
- We darkened grey secondary text, such as dates, captions and breadcrumbs, and made faint footer text easier to read.
- Every form field now has a visible label that's properly tied to it, including the enquiry forms on the Local and Studio pages and the full project brief form.
- Every page now has a "Skip to content" link. Press Tab once when a page loads and it appears in the top corner.
- Footer headings and a few page headings no longer skip levels, so screen reader users can move around a page by heading.
- The plan picker in our comparison calculator can now be used with a keyboard.
- We fixed a menu link that was invisible on blog and guide pages.
What works well
- Every image has a text alternative, or is marked as decorative.
- Every page has its language set to English (UK), so screen readers pronounce it properly.
- Each page has a single main heading.
- The site doesn't block zooming, and pages reflow to fit small screens.
- Links and buttons have readable names.
- Pages are built from plain HTML with very little JavaScript, which tends to work well with assistive technology.
Known issues
Our automated checks no longer find contrast, label or heading problems. These are the gaps we know remain:
| Issue | Where | WCAG |
|---|---|---|
| Text placed over photographs isn't covered by our automated contrast checks, so some may fall short. | Case studies and some page headers | 1.4.3 Contrast (minimum) |
| Hover and focus colours haven't all been checked for contrast. | Sitewide | 1.4.3 Contrast (minimum), 1.4.11 Non-text contrast |
| The interactive tools, such as the scorecards and calculators, haven't had a full manual keyboard and screen reader test. Results that update as you type may not be announced to screen readers. | Free tools | 4.1.3 Status messages |
Tell us about a problem
If you find something on this site hard to use, or you need information in a different format, please tell us. Email [email protected] or call 07737 548 072. Tell us the page and what went wrong, and we'll get back to you as soon as we can.
About this statement
This statement was prepared on 10 October 2026, and updated the same day after our fixes, based on our own testing. We'll review it whenever we make significant changes to the site, and at least every six months. For background on what UK law expects from business websites, see our guide to website accessibility in 2026.