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

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)
  • interact with the site as we have selected colours, contrast profiles and fonts with accessibility in mind
  • understand the website text as we have tried to present it as simply as possible.

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 are not fully accessible:

  • some images do not have the alt text
  • some older pdf documents are not fully accessible to screen reader software
  • some of the content has low readability score

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website.

If you find any problems not listed on this page or think we're not meeting accessibility requirements please contact help@jisc.ac.uk

Enforcement procedure

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 this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Non accessible content

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

Non-compliance with the accessibility regulations

Content

Headings, labels, text and descriptions have been identified as missing. ‘Bold’ and ‘I’ tags have been used to format text. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and relationships).

There are instances where links are identified only by colour. This does not meet WCAG 2.1 success criterion 1.4.1 (Use of colour).

There are instances where the colour contrast is insufficient. This does not meet WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)).

There is no option to skip repeated content. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass blocks).

There are cases where link text is used for multiple different destinations. This does not meet WCAG 2.1 success criterion 2.4.4 (Link purpose (In context)).

There are cases where an element is not highlights on focus. This does not meet WCAG 2.1 success criterion 2.4.7 (Focus visible).

Select box has no description included. This does not meet WCAG 2.1 success criterion 3.3.2 (Labels or instructions)

There are instances where some user interface components cannot be programmatically determined. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role, value).

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.

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 podcasts

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.

How we tested this website.

This website was tested in September 2020 using the automated test tool SiteImprove.

What we’re doing to improve accessibility

We are looking to correct these compliance issues at the earliest opportunity through development work on the site and we are improving our software development and user experience design processes so that they take account of accessibility requirements as early as possible.

Preparation of this accessibility statement

This statement was prepared on 15 September 2020.

Content modified from the GOV.UK accessibility statement - used through the Open Government Licence v3.0.