Accessibility Statement for JUSP

This accessibility statement applies to content published on jusp.jisc.ac.uk.

This website is run by the JUSP team at 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 have 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 this website is

We know some parts of this website are not fully accessible:

  • Some older pdf documents are not 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
  • Some of our online forms are difficult to navigate using just a keyboard

How to request content in an accessible format

If you need information on this website in a different format like accessible pdf, large print, easy read, audio recording or braille then contact us:

We will consider your request and get back to you.

Reporting accessibility problems with this website

We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact help@jisc.ac.uk with JUSP in the subject.

Enforcement procedure

If you are not happy with how we respond to your complaint, 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 partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Third-party tools

We use Slide Share on the site. We know there are some accessibility issues with these embedded players. You can click through to the Slide Share site where you can download a pdf of the presentation - but there are also accessibility issues with these auto-generated pdfs. We don't have a suitable alternative and, as we don't control the platform, are unable to make the changes required to improve it. Please let us know if you would like an accessible version of any of our presentations and we will send one through to you.

Content

Some text and background combinations don't have enough contrast. They don't meet WCAG 2.1 success criterion 1.4.3 (contrast - minimum). We will address these issues in all parts of the site except R4 Journals by July 2024.

Some linked images are missing alternative text. This doesn't meet WCAG 2.1 success criterion 1.1.1 (non-text content). We will address these issues in all parts of the site except R4 Journals by July 2024.

Some links do not have alternative text. This doesn't meet WCAG 2.1 success criterion 2.4.2 (link purpose – in context). We will address these issues in all parts of the site except R4 Journals by July 2024.

Main language is not declared on all pages. This doesn't meet WCAG 2.1 success criterion 3.1.1 (landing page). We will address these issues in all parts of the site except R4 Journals by July 2024.

Issues with pdfs and other documents

Some of our pdfs do not have a title element to aid navigation. This fails WCAG 2.1 success criteria 2.4.2 (page title). We will address these issues in all parts of the site except R4 Journals by July 2024.

Issues with interactive tools and transactions

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). We will address these issues in all parts of the site except R4 Journals by July 2024.

Some pages have element IDs that are not unique. This doesn't meet WCAG 2.1 success criterion 4.1.1 (parsing). We will address these issues in all parts of the site except R4 Journals by July 2024.

Disproportionate burden

At this time we consider that it would be a disproportionate burden to fix all of the accessibility issues in a low-use area of the site which we plan to review, scale back and replace. This work is planned for completion by February 2025. We consider it appropriate to invest our resources into the new fully accessible service rather than into a website that is being replaced.

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.

Older recordings

The accessibility regulations don't require us to provide transcripts for recordings published before 23 September 2020. Though we will provide them for new webinars as standard. Please contact us for support with webinars published before September 2019.

How we tested this website

This website was last tested on 3 August 2023. The test was carried out by Jisc staff using four pieces of accessibility software: axeDevTools from Deque Systems Inc; Lighthouse from Google Chrome; SiteImprove Accessibility Checker Extension; and WAVE from WebAIM at Utah State University.

We tested a sample of pages by working through use cases encompassing a range of user activities and functionality.

What we are 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 updated on 14 February 2024.