Accessibility statement for jisc.ac.uk
This statement applies to content published on www.jisc.ac.uk. It does not apply to content on service.jisc.ac.uk subdomains.
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 400% 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 know some parts of this website aren’t fully accessible. For example:
- Not all videos are completely accessible
- Issues with the cookie banner when the page is zoomed to 200% on certain screen sizes
- Some visited links are inaccessible
- Some links do not have focus styles for Safari / macOS users
- Some sections of the site do not use unique ID attributes
- If you remove the CSS styling, some icons appear enlarged which can make it difficult to navigate
- Issues with the homepage header hero minimum colour contrast on certain screen sizes when the page is zoomed to 200%
Feedback and contact information
If you need information on this website in a different format like accessible pdf, large print, easy read, audio recording or braille contact us:
- Email - help@jisc.ac.uk
- Call - 0300 3002212
- Speak to your relationship manager
We’ll consider your request and get back to you.
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, contact web@jisc.ac.uk.
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 (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 its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 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
- If a video has captions, we do not always provide a separate transcript or audio description as well. This fails WCAG 2.1 success criterion 1.2.1 (audio-only and video-only - prerecorded)
- Not all videos have edited, synchronised captions, which fails WCAG 2.1 success criterion 1.2.2 (captions - prerecorded) – in these instances, a downloadable transcript will be available instead
- Some visited links do not meet the minimum colour contrast. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum)
- We do not currently provide audio descriptions for all prerecorded video content. This fails WCAG 2.1 success criterion 1.2.5 (audio description - prerecorded)
- Some functionality of the cookie banner is not available on 600-700 pixel wide screens when text is resized without assistive technology up to 200 percent. This fails WCAG 2.1 success criterion 1.4.4 (resize text)
- For Safari / macOS users, some links have no focus styles. This fails WCAG 2.1 success criterion 2.4.7 (focus visible)
- ID values used in ARIA and in labels are not always unique. This fails WCAG 2.1 success criterion 4.1.1 (parsing)
- Removing styling (CSS) on pages causes enlarged icons to appear, which can make it difficult to navigate and read content. This causes a minor CSS dependence issue
- When resizing text to 400%, the site footer navigation text overlaps. This fails WCAG 2.1 success criterion 1.4.10 (reflow)
- When text is resized without assistive technology to 200% (to meet Success Criterion 1.4.4 Resize Text), some words in the homepage header hero do not meet the minimum colour contrast on certain screen sizes. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum)
Third-party tools
YouTube
We embed YouTube videos on the site. We know there are accessibility issues with this feature. We don't have accessible alternatives and, as we don't control the platform, are unable to make the changes required to improve them. Let us know if you would like an accessible version of any video we put live, we will send it through to you.
Hotjar
We use Hotjar to better understand our users’ needs and optimise the experience of this website. 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. We are aware of a number of accessibility issues - particularly with buttons - detailed in full below.
Adestra
We use Adestra to enhance our understanding of user interactions and improve the effectiveness of our email communications. Since we do not have full control over the platform, we are limited in our ability to make specific improvements. We are aware of a number of accessibility issues.
Accessibility audit for Hotjar (4 October 2021)
Non-compliance with the accessibility regulations
- The button to open/close the survey panel has no text alternative. This fails WCAG 2.1 success criterion 1.1.1 (Non-text content) [Level A]
- The survey panel label does not have descriptive enough text. This fails WCAG 2.1 success criteria 1.1.1 (Non-text content, level A) and 2.4.6 (Headings and labels) [Level AA]
- The survey panel content is not included in an HTML5 or WAI-ARIA landmark. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships) [Level A]
- The Hotjar branding link is not underlined. This fails WCAG 2.1 success Criterion 1.4.1 (Use of colour [Level A]
- Disabled buttons have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.3 (Contrast - minimum) [Level AA] and WCAG 2.1 success criterion 1.4.11 (Non-text contrast) [Level AA]
- When a user resizes text to 200% the size of text and controls do not change. This fails WCAG 2.1 success criterion 1.4.4 (Resize text) [Level AA]
- Radio buttons, checkboxes and textareas have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.11 (Non-text contrast) [Level AA]
- The button to open/close the survey panel, radio buttons, checkboxes, textareas, the “Next” button, the “Skip” button, the “Close” button and the Hotjar brand link do not have a visible focus indicator. This fails WCAG 2.1 success criterion 2.4.7 (Focus visible) [Level AA]
- Radio buttons and checkboxes do not have a “name” attribute, so the accessible name does not match the visible label. This fails WCAG 2.1 success criterion 2.5.3 (Label in name) [Level A]
- The button to submit each “screen” of the survey is not a form submit button. This fails WCAG 2.1 success criteria 3.2.2 (On input) [Level A] and 4.1.2 (Name, role, value) [Level A]
- The name and role of the button to open/close the survey panel cannot be programmatically determined. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value) [Level A]
How we tested this third party software
We assessed the Hotjar survey software tool against WCAG 2.1 AA using:
- Manual techniques
- Firefox accessibility inspector
- SiteImprove browser extension for Chrome
- Axe browser extension for Chrome, noting this was not capable of testing inside the Hotjar panel
Non-compliance with the accessibility regulations
- The button to open/close the survey panel has no text alternative. This fails WCAG 2.1 success criterion 1.1.1 (Non-text content) [Level A]
- The survey panel label does not have descriptive enough text. This fails WCAG 2.1 success criteria 1.1.1 (Non-text content, level A) and 2.4.6 (Headings and labels) [Level AA]
- The survey panel content is not included in an HTML5 or WAI-ARIA landmark. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships) [Level A]
- The Hotjar branding link is not underlined. This fails WCAG 2.1 success Criterion 1.4.1 (Use of colour [Level A]
- Disabled buttons have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.3 (Contrast - minimum) [Level AA] and WCAG 2.1 success criterion 1.4.11 (Non-text contrast) [Level AA]
- When a user resizes text to 200% the size of text and controls do not change. This fails WCAG 2.1 success criterion 1.4.4 (Resize text) [Level AA]
- Radio buttons, checkboxes and textareas have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.11 (Non-text contrast) [Level AA]
- The button to open/close the survey panel, radio buttons, checkboxes, textareas, the “Next” button, the “Skip” button, the “Close” button and the Hotjar brand link do not have a visible focus indicator. This fails WCAG 2.1 success criterion 2.4.7 (Focus visible) [Level AA]
- Radio buttons and checkboxes do not have a “name” attribute, so the accessible name does not match the visible label. This fails WCAG 2.1 success criterion 2.5.3 (Label in name) [Level A]
- The button to submit each “screen” of the survey is not a form submit button. This fails WCAG 2.1 success criteria 3.2.2 (On input) [Level A] and 4.1.2 (Name, role, value) [Level A]
- The name and role of the button to open/close the survey panel cannot be programmatically determined. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value) [Level A]
How we tested this third party software
We assessed the Hotjar survey software tool against WCAG 2.1 AA using:
- Manual techniques
- Firefox accessibility inspector
- SiteImprove browser extension for Chrome
- Axe browser extension for Chrome, noting this was not capable of testing inside the Hotjar panel
What we’re doing to improve accessibility
Whenever new features are released, they must meet the WCAG 2.2 AA standard. We’re also committed to working on the issues above. We will update this page when issues are fixed.
Preparation of this accessibility statement
This statement was prepared on 5 January 2022. It was last updated on 17 April 2024.
Content modified from the GOV.UK accessibility statement - used through the Open Government Licence v3.0.