Accessibility.

This website is built to meet WCAG 2.2 level AA. That is the target the site was designed against rather than a claim made afterwards.

What that means in practice

• Every page can be read and navigated without JavaScript. Nothing is hidden behind it, and no content waits for a script to arrive.
• Two things do need it. The service status indicator falls back to a plain link. Forms — the enquiry forms and the package builder — can be filled in without JavaScript but not sent, because the spam check runs in your browser. Each form says so where the send button would be, and gives a phone number and an email address that reach the same place and are no slower.
• Every interactive element can be reached and operated with a keyboard, and has a visible focus outline. We never remove focus outlines.
• Body text meets a contrast ratio of at least 4.5:1, and larger text and interface boundaries at least 3:1.
• Colour never carries meaning on its own. Where a colour indicates something — a service status, a ticket priority — there is always a text label beside it.
• Pages use one h1 and a correct heading order, with landmarks for navigation, main content and the footer.
• A skip link is the first thing a keyboard user reaches.
• Form fields have real labels, and errors are linked to the field they belong to.
• Text reflows to 320 pixels without horizontal scrolling. Tables scroll within their own container rather than the page.
• Animation respects your reduced-motion setting. There is almost none in any case.
• There are no images of text, no carousels, no auto-playing media and no time limits.

How it was tested

Automated accessibility testing runs against every page each time the site is built, and a build that introduces a violation fails rather than deploying. Automated testing catches perhaps half of what matters, so every page template also gets a manual keyboard pass.

Where we know it is imperfect

Automated testing and our own checks are not the same as testing with disabled people who use assistive technology every day, and we have not done that. If you use assistive technology and something here does not work properly, we would genuinely like to know — that feedback is more useful than another audit.

A form you cannot send without JavaScript is a real limitation, not a footnote. It is the price of keeping a public form usable at all, and the way round it is a phone number and an email address rather than a worse form. If that is the wrong trade for you, tell us and we will take the enquiry however suits you.

Two services we link to are outside our control and not covered by this statement: the client portal and the service status page, both run on third-party platforms.

Tell us

Email hello@puzzletech.co.uk or call 01480 570339. Tell us the page and what went wrong, and we will fix it and tell you when it is done. If you need something on this site in another format, ask and we will provide it.

Last updated 24 September 2026.