This statement applies to content published on The JCS management portal.
This website is run by Jisc. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:
- Change colours, contrast levels and fonts
- Zoom in up to 300% without problems
- Navigate most of the website using just a keyboard
- Navigate most of the website using speech recognition software
- Use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is this website
We have not identified any parts of this website which aren’t fully accessible
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille contact us:
We’ll consider your request and get back to you.
Reporting accessibility problems with this website
If you find any problems that aren’t listed on this page or think we’re not meeting the requirements of the accessibility regulations, contact email@example.com.
If you contact us with a complaint and you're not happy with our response contact the Equality Advisory and Support Service (EASS)
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).
Technical information about this website’s accessibility
Jisc is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is fully compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
How we tested this website
We use the Web Content Accessibility Guidelines V2.1 level A and level AA to test how accessible this website is.
What we’re doing to improve accessibility
Whenever new features are released they must meet WCAG 2.1 AA. We’re also committed to working on the issues above.
Preparation of this accessibility statement
This statement was prepared on 30 July 2020. It was last reviewed on 3 November 2021.