Skip to main content
Skip to content

Accessibility

Accessibility statement

We want this site to work for everyone, including people using screen readers, keyboard navigation, magnification or reduced-motion settings.

Last updated: August 2026

We want this website to be usable by as many people as possible, including people using screen readers, keyboard navigation, magnification or reduced-motion settings. This statement explains what we have done, what we know needs work, and how to tell us about a problem.

What we have built in

  • Semantic HTML structure with a single main heading per page and a logical heading order.
  • Keyboard access to every interactive element, with visible focus styles.
  • Colour combinations chosen to meet contrast requirements for body text and interface elements.
  • Labelled form fields, with errors described in text rather than by colour alone.
  • Support for the operating system's reduced-motion preference, which removes non-essential animation.
  • Text that reflows without horizontal scrolling down to small mobile widths.
  • Descriptive alternative text for meaningful images, and decorative images hidden from assistive technology.

Standards we are working to

We are working to the Web Content Accessibility Guidelines version 2.2 at level AA. A formal audit has not yet been completed, so we are not claiming full conformance. The results of that audit will be published here.

Known limitations

  • Some interactive components have not yet been tested against every combination of screen reader and browser.
  • Documents you upload during an application are your own files and may not themselves be accessible.
  • Third-party content embedded in future may not fully meet the same standard.

If you need something in another format

If any part of this site is a barrier, contact us and we will help directly — including taking an application over the telephone or providing information in a different format. Tell us what would work best for you.

Reporting a problem

Contact us using the details on our contact page with the page address, what you were trying to do and the assistive technology you were using. We treat accessibility reports as bugs, not feedback, and we will tell you what we intend to do about it.