Skip to the Academy content

Accessibility

Make it read the way you need

Change any of these and it applies across the whole Academy straight away. Nothing is sent anywhere, and you do not need an account.

Theme
Contrast

High contrast works with light and dark rather than replacing them, so you can have both.

Text size

This scales spacing and component sizing as well as the type, so the layout stays balanced. Your browser zoom works too, and the Academy reflows without horizontal scrolling up to at least 200%.

Line spacing
Motion

Nothing in the Academy depends on animation to convey meaning, so reducing motion never costs you information.

Links

Links in body text are already distinguished by more than colour. This underlines every link everywhere, for anyone who wants them unmissable.

Your settings are kept in this browser only. Nothing is sent anywhere and no account is needed. They apply across the whole Academy immediately.

How the Academy approaches accessibility

The formal accessibility statement for FEFunding, including the Academy, is on the accessibility statement page. This section describes how the Academy itself is built and tested.

FEFunding Academy is built to meet WCAG 2.2 level AA as a minimum, with some level AAA enhancements where they genuinely help. Accessibility is built into the component library rather than added afterwards, which is why the settings above change the whole product rather than one page.

What we have done

  • Semantic HTML with landmarks, a logical heading order and a skip link on every page.
  • Full keyboard operation, including the menu, tabs, filters, search and scenario choices.
  • Visible focus indicators in every theme, including high contrast.
  • Nothing conveyed by colour alone: status carries a label and a shape as well as a hue.
  • Touch targets that meet the WCAG 2.2 target size expectations.
  • Text alternatives for every diagram.
  • Diagrams built as accessible HTML rather than images, so they scale, reflow and print.
  • Reflow without horizontal scrolling at 200% zoom, and a layout that works from 320px.
  • Live regions that announce search results, answers and status changes.
  • Respect for your operating system's colour, contrast and motion preferences.
  • No CAPTCHA. Abuse is handled with rate limiting rather than a puzzle.

How it is tested

  • Automated accessibility checks run in continuous integration against representative routes.
  • A critical accessibility regression fails those checks.
  • Manual testing with screen readers (NVDA, VoiceOver and TalkBack), keyboard-only use, zoom to 400% and voice control has not yet been carried out. It is planned, and this page will be updated when it has been done.

Known limitations

Because manual testing with assistive technology has not yet been carried out, there may be barriers that automated checks cannot find. If you meet one, please tell us.

Some official documents we link to are hosted elsewhere and are outside our control. Where one of them is difficult to use, tell us and we will describe the relevant part in the Academy itself.

If something is not working for you

Tell us and we will fix it. Describe what you were trying to do, what happened and what you are using, and we will come back to you. Report an accessibility barrier.