This website is run by Jisc. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- Change colours, contrast levels and fonts
- Zoom in up to 300% without the text spilling off the screen
- Navigate most of the website using just a keyboard navigate most of the website using speech recognition software
- Listen to 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 know some parts of this website aren’t fully accessible:
- Some older PDF documents aren’t fully accessible to screen reader software
- We have issues with text colour contrast
- We have issues with some interactive elements
- We have some content issues
What to do if you can’t access parts of this website
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.
If you can’t view the map on our ‘contact us’ page, call or email us for directions.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of 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, use the ‘spotted an issue?’ button at the foot of every page, or contact email@example.com.
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’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
Jisc is committed to making jisc.ac.uk 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.1 AA standard, due to the non-compliances listed below.
The content listed below non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some text and background combinations don’t have enough contrast - especially around navigation in the footer, and section ‘tags’. They don’t meet WCAG 2.1 success criterion 1.4.3 (contrast - minimum). We are working on these.
Our older promotional links include adjacent links going to the same place, where a single link is needed. This doesn’t meet WCAG 2.1 success criterion 2.4.4 (link purpose - in context). We are phasing out the pages that have these. This should be complete by the end of 2019.
Heading order doesn’t clearly reflect the structure of the page in some sections. This does not meet WCAG success criterion 1.3.1 (info and relationships). We are addressing these on a rolling basis.
Our footnote and abbreviations aren’t fully accessible to screen readers. This does not meet WCAG 2.1 success criterion 2.1.1 (keyboard). We plan to develop an alternative to our current footnote approach. We are investigating what can be done to improve our abbreviations.
Issues with PDFs and other documents
Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be marked up so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value). Any new PDFs or Word documents we publish should meet accessibility standards.
Issues with images, video and audio
There is unnecessary or unhelpful alt text on some images, especially where diagrams are used. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content). We are working to correct these.
We don’t provide transcripts of all our podcasts. This does not meet WCAG 2.1 success criterion 1.2.1 (audio only and video only - prerecorded). We will start to provide transcripts for all new podcasts.
Issues with interactive tools and transactions
There is inadequate context with some interfaces - especially around listing pages and pagination controls. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to redevelop the pages where this is an issue in 2020.
Role and state information is missing from some interactive elements on older pages. These do not meet WCAG 2.1 success criterion 4.1.2 (name, role value). Older pages will be retired or redeveloped in 2020.
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value). Some of these pages are due to be redeveloped in 2020, we will be reviewing the others and whether to retire them or remove them.
Content that’s not within scope of the accessibility regulations
Older PDFs and other documents
The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
The accessibility regulations don’t require us to provide transcripts for podcasts published before 23 September 2020. Though we will provide them for new podcasts, we won’t provide them for podcasts published before September 2019.
Live video streams don’t have captions. This does not meet WCAG 2.1 success criterion 1.2.4 (captions - live). We don’t plan to add captions to live video streams and live video is exempt from meeting the accessibility regulations.
How we tested this website
An in-depth accessibility audit conducted was completed in 2016. Since then the website is tested every two weeks by an external testing agency.
We tested our main website - jisc.ac.uk. Other service sites conduct their own testing and will have their own accessibility statements.
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.
This statement was prepared on 2 August 2019. It was last updated on 20 August 2019.