This accessibility statement applies to content published on https://irus.jisc.ac.uk/r5/uk/.
This website is run by the IRUS 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:
- we have some issues with text colour contrast
- we have some issues with interactive elements
- we have some content issues
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 firstname.lastname@example.org with IRUS in the subject.
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.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
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.
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 plan to address these issues as part of a report navigation refresh scheduled for July 2024.
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 plan to address these issues as part of a report navigation refresh scheduled for July 2024.
Issues with interactive tools and transactions
Some of our form fields are marked up incorrectly. For example, because some form fields are missing a 'form' label or 'form control' label. This doesn't meet WCAG 2.1 success criteria 1.1.1 (non-text content), 2.4.6 (headings and labels), 3.3.2 (labels and instructions), and 4.1.2 (name, role, value). We plan to address these issues as part of a report navigation refresh scheduled for July 2024.
Field input errors are not fully announced with screen readers. This doesn't meet WCAG 2.1 success criteria 3.3.1 (error identification) and 4.1.3 (status messages). We plan to address these issues as part of a report navigation refresh scheduled for 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 plan to address these issues as part of a report navigation refresh scheduled for July 2024.
How we tested this website
This website was last tested on 4 August 2023. The test was carried out by Jisc staff using 4 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 prepared on 20 February 2024.