Accessibility Statement

What we aim for

This site targets WCAG 2.2 Level AA. People reach a site like this one under stress, sometimes on an old phone, sometimes using a screen reader. It should work anyway.

How that is checked

Accessibility here is enforced by the build rather than assumed. Colour contrast is verified against WCAG 2.2 thresholds on every build and the build fails if any pair drops below its minimum. Pages are checked for a single heading hierarchy without skipped levels, for horizontal overflow from 320px upwards, and for tap targets below the minimum size.

The site is also built to work without JavaScript: navigation, menus and expandable sections all function with scripting disabled.

What that means in practice

A skip link to the main content, semantic landmarks, visible keyboard focus on every interactive element, form fields with real labels and error messages tied to them, no motion for anyone who has asked their system to reduce it, and text that reflows without a horizontal scrollbar.

Known limitations

To be completed after a screen-reader review. This statement will list anything found and not yet fixed, rather than claiming full conformance. Automated checks catch a minority of accessibility problems; a manual review with assistive technology is scheduled before launch.

Telling us about a problem

If any part of this site is difficult or impossible for you to use, please tell us. Describe the page and what happened. Reports of this kind are treated as defects, not suggestions, and we will also tell you what we are doing about it.

Getting the information another way

If a page is not working for you, the information on it is available by phone or email. Nobody should have to fight a website to find out whether their probation can end early. Telephone enquiries are accepted 24/7.