Accessibility

This page is a starter. The commitments below are real, but the dated statement at the end needs the team's sign-off before it should be published. Review it, remove this paragraph, and switch the page to indexable.

What we aim for

We build this site to meet WCAG 2.2 Level AA. That is the target we design and review against, and it is what we hold ourselves to when something falls short.

What we have actually done

Being honest about this matters more than a badge:

• Every page is checked by an automated accessibility scan built into our own publishing system — colour contrast, focus visibility, keyboard reachability, landmarks, headings, form labels and alternative text.
• Nothing on this site moves, resizes or reflows when you hover over it or move focus to it. Every interactive element still shows a visible change, but it does so with colour, outline or shadow.
• Animation respects your system's reduced-motion setting. If you have asked your device for less movement, the drifting, sweeping and flickering effects stop.
• Colour contrast is measured against the rendered page rather than assumed from the stylesheet, and pages are re-checked when they change.

What automated testing cannot tell us

An automated scan cannot certify accessibility, and we do not claim it does. It finds the machine-checkable failures — a missing label, a contrast ratio, an unreachable control. It cannot judge whether alternative text describes the right thing, whether a heading structure makes sense to somebody navigating by headings, or whether a form is understandable under stress.

So there will be problems on this site that our scans have not found. If you hit one, we want to hear about it.

We do not use an accessibility overlay

We deliberately do not install a widget that claims to fix accessibility from the outside. Overlays interfere with the assistive technology people already use and configure, and they do not repair the underlying page. We fix the page.

Known limitations

• Third-party embeds — video players, maps — are outside our control and may not meet the same standard.
• Some older pages predate the current review process and are being worked through.

Telling us about a problem

Write to [email protected] with the page address and what went wrong — including which browser, device and assistive technology you were using, if you know. You do not need to use technical language; "the menu traps my keyboard on this page" is exactly the right amount of detail.

We aim to acknowledge within two working days and to tell you what we are going to do about it, and by when.

If you need something on this site in another format, ask, and we will get it to you.