Our commitment

FamilySafe is committed to making our website usable for as many people as possible, including people who use screen readers, keyboard-only navigation, magnification, voice control or other assistive technology. This statement explains how accessible the site is, where it falls short, and what to do if you find something that stops you using it.

What this covers

This statement covers www.familysafe.co.uk and the FamilySafe web application. It does not cover third-party services we link to — banks, GOV.UK, the NHS, HMRC and others — which have their own accessibility statements.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 to AA level. These are the accessibility standards published by the World Wide Web Consortium and used by UK public bodies. They cover, among other things:

  • Colour contrast that meets recommended ratios for readable text
  • Full keyboard navigation for people who do not use a mouse
  • Compatibility with common screen readers
  • Sensible text sizes and layouts on any screen
  • Clear focus indicators so you can see where you are on the page
  • Alternative text on images that carry meaning
  • Forms with clear labels and helpful error messages

How accessible the site currently is

We believe FamilySafe is substantially compliant with WCAG 2.2 AA. Some parts of the site do not yet meet every criterion. Known limitations are listed below. We are working through them and will update this statement as each is resolved.

What we have built in

Every template on the site has been designed and tested with the following in mind:

  • Colour contrast of at least 4.5 to 1 for body text and 3 to 1 for large text
  • Every meaningful image has alternative text. Decorative images are marked as such so screen readers skip them
  • Full keyboard navigation with a visible focus indicator on every interactive element
  • A skip-to-content link at the top of every page for keyboard and screen reader users
  • Respect for your reduced motion preference — animations are suppressed if you have that setting turned on
  • Form fields with clear labels, sensible error messages and helpful hints
  • A logical heading structure that follows the outline of each page
  • Language set to en-GB so screen readers use British English pronunciation
  • Text can be resized to 200 percent without breaking the layout
  • The site works with recent versions of macOS VoiceOver, iOS VoiceOver, Windows Narrator, NVDA and TalkBack

How we test

We test in three ways. First, automated scans using axe and Pa11y on every new page and template before it goes live. Second, manual keyboard-only testing on every template. Third, screen reader testing using VoiceOver on Mac and iOS, and NVDA on Windows.

We also commission an independent accessibility audit at least once a year. The findings from each audit are used to update the known limitations section above and to plan fixes.

Reporting a problem

If you find something on the site that is not accessible to you, we want to know. We take these reports seriously and use them to make the site better for everyone.

Email us at accessibility@familysafe.co.uk with:

  • The web address (URL) of the page where you had a problem
  • What you were trying to do
  • What went wrong or was in the way
  • The device, browser and any assistive technology you were using, if you are comfortable telling us

We aim to respond within five working days. If your problem is urgent — for example, you cannot access information you need in a bereavement — please tell us in the subject line and we will prioritise your report.

Technical information

This section is written for technical readers and accessibility auditors.

  • Target standard: WCAG 2.2 to AA level
  • Automated testing tools: axe-core, Pa11y
  • Manual testing tools: VoiceOver (macOS, iOS), NVDA (Windows), Windows Narrator, TalkBack (Android)
  • Testing browsers: Chrome, Safari, Firefox, Edge, all latest two major versions
  • Site framework: server-rendered HTML with progressive enhancement
  • Site language: en-GB
  • Editorial content is managed via a headless CMS. Editorial input does not affect the rendered accessibility of the site because presentation is controlled at the template layer

Preparation and review

This statement was prepared on 7 July 2026 using a self-assessment supported by automated testing tools and manual review.

We review this statement at least every 12 months, or sooner if there is a material change to the site or if an independent audit identifies new issues.

Next review: 7 July 2027