Skip to main content

Legal

Accessibility Statement

Our conformance position against WCAG 2.2 Level AA and EN 301 549, known limitations, and how to report an accessibility barrier.

Version
1.0
Last reviewed
Governing law
England and Wales

We want everyone to be able to use this website, including people who use screen readers, keyboard-only navigation, magnification, or speech recognition. This statement explains where we stand, what we know is not yet right, and how to tell us when we have got something wrong.

1. Scope

This statement covers the public marketing pages of this website and the authenticated client portal at the same domain. It does not cover third-party services embedded in the payment flow, which are covered by their own providers' statements.

2. Standard We Are Working To

We aim to meet Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA, and the requirements of EN 301 549, the harmonised European standard that incorporates WCAG at that level.

3. Conformance Status

This website is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means most of the content meets the standard but some parts do not, and we have listed what we know about below. We would rather say this plainly than claim full conformance we have not independently verified.

4. Accessibility Features in Place

  • A skip link to the main content as the first focusable element on every page.
  • Semantic HTML landmarks — header, nav, main, footer — and one h1 per page with no skipped heading levels.
  • Full keyboard operability, including the navigation menus and all disclosure components. Nothing is reachable by mouse only.
  • A visible focus indicator on every interactive element, and scroll offsets set so the sticky header never obscures the element you have just focused (SC 2.4.11).
  • Interactive targets sized at least 24 by 24 CSS pixels, and at least 44 pixels for primary actions on touch (SC 2.5.8).
  • No interaction requires a dragging movement (SC 2.5.7).
  • Text and background colour combinations meeting the 4.5:1 contrast ratio for body text and 3:1 for large text and interface components.
  • Form fields with programmatically associated labels; errors described in text rather than by colour alone, and linked to the field they relate to.
  • Pasting into password fields is permitted and password managers work normally (SC 3.3.8).
  • Contact and help routes appear in the same position on every page (SC 3.2.6).
  • Content reflows at 320 CSS pixels wide without two-dimensional scrolling, and text can be resized to 200% without loss of function.
  • Meaningful alternative text on informative images; decorative images marked so screen readers skip them.
  • Animation and transitions are disabled for visitors whose system requests reduced motion.
  • Accordion and tab content is present in the page source rather than injected later, so it is available to assistive technology and to search engines alike.

5. Known Limitations

We are aware of the following, and are working on them:

IssueEffectPlanned fix
No independent third-party audit has been completed Our conformance claim is based on internal testing only, so issues may exist that we have not found External audit to be commissioned; findings will be published here
Invoice PDFs Generated PDFs are not yet tagged for screen reader navigation Under review; an accessible HTML invoice view is available on request in the meantime
Third-party payment pages The hosted payment step is provided by Stripe and is outside our control We monitor Stripe's own accessibility conformance and will offer an alternative payment route on request

6. How We Assessed This

This statement is based on a self-assessment carried out by our development team, using automated testing with axe-core, manual keyboard-only navigation, and screen reader spot checks. It has not been independently verified. Self-assessment finds fewer problems than an expert audit does, which is why section 5 says so explicitly.

7. Tell Us About a Problem

If you hit a barrier on this site, please tell us — it is the fastest way for us to fix it, and we treat these reports as bugs rather than as feedback.

We aim to acknowledge within 2 business days and to give you a fix or a timescale within 10 business days. If you need information from this site in another format — large print, plain text, or a different document format — ask and we will provide it.

8. If You Are Not Satisfied

If you have raised a problem with us and are not happy with our response, you can escalate it to the relevant accessibility or equality body in your jurisdiction. In the United Kingdom that is the Equality Advisory and Support Service; within the European Union, the national enforcement body designated under the European Accessibility Act. We would much rather resolve it directly first.

9. Our Ongoing Commitment

Accessibility is checked as part of our normal development work rather than as an annual exercise: automated checks run in our build pipeline, and keyboard and screen reader testing is part of reviewing any new interface. We review this statement at least annually, and whenever we make a significant change to the site.