Accessibility statement

For the MitsuruTech Learning Platform and this website.

We want as many people as possible to be able to use this website and the learning platform behind it. That means you should be able to:

  • change colours, contrast levels, the text size and the line spacing from your profile, once, for every page;
  • read the site in Verdana or Arial if that suits you better;
  • navigate most of the site using a keyboard alone;
  • navigate most of the site using speech recognition software;
  • listen to most of the site using a screen reader.

We have also made the text as simple as we can, and the site says what it is doing rather than showing a symbol and leaving you to guess.

How accessible this website is

Parts of this website are not fully accessible. The list below is what we know about. It is short because we have measured it rather than guessed, and it is honest because you are entitled to rely on it.

What is not accessible

  • The code editor. Pressing Tab inside it indents your code rather than moving to the next control, which is what a code editor normally does. You can press Ctrl+M to make Tab move out of the editor instead, and the editor says so on the page and when a screen reader enters it. We know that this is more work than it should be, and a plain text box that still saves, runs and shows your test results is the route we intend to add for anybody who cannot use the editor at all.
  • The code editor with a screen reader. The editor is a third-party component (Monaco) and, while it is usable, it announces more than it needs to and is not as clear as the rest of the site.
  • We have not yet tested with a real screen-reader user. Everything above was found by reading and measuring our own code. That is not the same thing, and we say so rather than implying an audit we have not had.

Feedback and contact information

If you need information on this website in a different format, or you find a problem that is not listed above, email [email protected]. Tell us the page, what you were trying to do and what happened. We will reply within five working days.

If you are a student, your college’s learning support team can also ask us on your behalf, and we would rather hear from either of you than from neither.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

We are committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed above.

How we tested this website

We test the site automatically on every change: every public page and every page behind the door is checked against the axe accessibility rules as part of our test suite, and the colour of every pair of text and background on the site is measured against the 4.5:1 contrast requirement by a test that reads the stylesheets themselves, so a colour edited lighter fails a build rather than a screen.

We have not yet carried out an audit with an external tester or with a student who uses a screen reader daily. When we do, this statement will say when and by whom.

This statement was prepared on 29 September 2026. It was last reviewed on 29 September 2026. This website was last tested on 29 September 2026, by Mitsuru Technologies, using the automated checks described above.