Skip to main content

Legal

Accessibility statement

Last updated: 17 April 2026 · Version 1.0

Our commitment

CareCompliant is designed for managers, carers, and auditors across UK care providers. Some users rely on screen readers, keyboard navigation, magnification, or high-contrast settings. We want the platform and this website to work for all of them.

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across both our marketing website and the application. This statement sets out where we are today, what we know does not meet that standard yet, and how to tell us when we get it wrong.

What this statement covers

  • The public website at carecompliant.co.uk and subdomains we operate
  • The authenticated CareCompliant application
  • Customer-facing email templates we send from the platform

It does not cover documents produced by other organisations and uploaded to the platform (for example, a policy document from a third party). We encourage customers to check the accessibility of their own uploads.

How we build for accessibility

  • Colour and contrast: all text meets the WCAG AA 4.5:1 contrast ratio; interactive elements meet 3:1 for non-text contrast.
  • Keyboard navigation: every interactive control can be reached and operated with a keyboard; focus states are always visible.
  • Screen reader support: semantic HTML, ARIA where needed, and tested with VoiceOver, NVDA, and TalkBack.
  • Responsive and mobile-first: designed down to 375px wide, tested across recent iOS and Android devices.
  • Reduced motion: animations respect the prefers-reduced-motion setting.
  • Plain language: CQC terminology is unavoidable, but we explain it where we introduce it.
  • Forms: clear labels, inline validation messages, and explicit error summaries.

Compatibility

The platform is designed to work with:

  • Current and previous versions of Chrome, Edge, Firefox, and Safari on desktop
  • Safari on iOS 16+ and Chrome on Android 12+
  • Screen readers including VoiceOver, NVDA, and JAWS (latest two major versions)
  • Zoom up to 200% without horizontal scrolling
  • Voice control on macOS and iOS

Known issues

We test every release and fix what we find, but we know we are not perfect. Issues we are tracking:

  • Some complex data tables in the Audit module do not yet announce sort state changes to screen readers. Planned fix: Q2 2026.
  • A handful of older PDF templates produced by the platform are not fully tagged for accessibility. We are migrating them to structured HTML exports.
  • The CQC heatmap visualisation relies on colour; a textual equivalent is available via the underlying data table but is not yet offered as the default.

If you hit an issue we don't list here, please tell us. See below.

Testing

We combine automated checks (axe-core in CI, Lighthouse), manual keyboard and screen-reader testing during code review, and periodic reviews by external accessibility specialists. The most recent external review was conducted in March 2026.

Feedback and getting help

If you find something that is hard to use, or if you need content in a different format (large print, easy read, accessible PDF), email [email protected]. We aim to respond within two business days.

Please include:

  • What you were trying to do
  • Where in the site or app it happened (a URL or screen name helps)
  • What assistive technology you were using, if any

Enforcement

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations in the UK. If you're not happy with how we respond, you can contact the EHRC through the Equality Advisory and Support Service.

Preparation of this statement

This statement was prepared on 17 April 2026 and is reviewed at least every six months. It was last reviewed on 17 April 2026.