Skip to main content

Accessibility statement

The short version

  • Every part of the site can be used with a keyboard alone.
  • The page can be zoomed to 200%, or the browser’s text size raised, without losing content.
  • Nothing blocks pinch-zoom on a phone or tablet.
  • Every text colour meets the WCAG AA contrast level.
  • It works with a screen reader, and with JavaScript turned off.
  • Found a barrier? Report it and it will be fixed.

How accessible this site is

The site meets the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA, the standard most of the web is measured against. What that means in plain terms follows.

  • Every link, button and form field works with a keyboard alone, and a clear outline always shows the current position on the page, known as a ‘visible focus indicator’.
  • Text can be enlarged. Zooming to 200%, or raising the browser’s default text size, reflows the page to fit without cutting anything off or forcing sideways scrolling.
  • On a phone or tablet, nothing stops pinch-zooming.
  • Text and background colours meet the AA contrast level so text stays readable, and every colour combination is checked automatically.
  • Buttons and links are large enough to tap, at least 44 by 44 pixels.
  • Headings are in a logical order, so a screen reader can move through a page by heading and nothing is skipped.
  • The site works with a screen reader, and with JavaScript turned off.

How it is tested

Accessibility is the first constraint the site is designed to, not a check at the end. Testing is done in three ways, because each catches what the others miss:

  • Automated checks run every time the code changes. A change cannot ship if it fails a rule, for example an image without a text alternative, a heading level that skips or a colour below the contrast line.
  • A keyboard pass moving through the site page by page using only the keyboard.
  • A screen reader to hear the site the way someone using one would.

Automated tools only catch some problems, so the keyboard and screen-reader testing does the rest by hand.

If something gets in the way

Reports are welcome. If any part of the site is hard to use, or stops a visitor doing what they came to do, it can be reported by email to accessibility@cfdc.org.uk. It helps to name the page and say what happened, with as much or as little detail as is available.

Every message is read, with an aim to reply within five working days. If something cannot be fixed straight away, the reader is told when it will be, and helped to get what they needed another way in the meantime.

Asking for a different format

If a visitor needs something on the site in another format, such as large print, easy read or audio, it can be requested by email to accessibility@cfdc.org.uk. It helps to name the page and the format needed. Replies are aimed within five working days. Every request is considered, though not every format can be promised.

About this statement

This statement describes how the site is built and tested today. When features are added or a problem is found, this page is updated.