Accessibility
These websites are run by Jisc. They are 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 using browser plugins
- 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)
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible are the websites
We know some parts of this website are not fully accessible:
- some areas are not fully operable via keyboard
- you cannot modify the line height or spacing of text
- you cannot change colours, contrast levels and fonts
Although there are currently no accessible alternative formats available, please email help@jisc.ac.uk to discuss any requirements you may have.
Reporting accessibility problems with these websites
We're always looking to improve the accessibility of these websites. If you find any problems not listed on this page or think we are 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
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Success Criterion 1.3.1: Info and Relationships
- Main navigation WAI-ARIA Menubar Role: child elements within the menubar have roles that are prohibited by WAI-ARIA specifications. This may affect how assistive technologies interpret the menu and its items. This does not meet WCAG 2.2 success criterion 1.3.1.
Success Criterion 2.1.1: Keyboard
- Main navigation menu: while sub-menu items are keyboard accessible, the dropdown menus do not visually expand when navigated using the keyboard. This does not meet WCAG 2.2 success criterion 2.1.1.
- Accordion panels: cannot be expanded or collapsed using the keyboard. This limitation affects users who rely on keyboard navigation, preventing them from accessing the content within the accordion panels. This does not meet WCAG 2.2 success criterion 2.1.1.he content listed below is non-accessible for the following reasons.
digitalcapability.jisc.ac.uk content
- Embedded YouTube videos do not have title attributes. This is a limitation of the YouTube platform. This does not meet WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Some SVG elements are without a text alternative. This does not meet WCAG 2.2 AA success criterion 1.1.1 (Non-text Content)
- Some navigation items and accordion panels do not visually expand while using a keyboard. This does not meet WCAG 2.2 AA success criterion 2.1.1 (Keyboard).
- Some child elements within the menubar have roles that are prohibited by WAI-ARIA specifications. This does not meet WCAG 2.2 AA success criterion 1.3.1 (Info and Relationships).
We plan to revisit these non-compliances in 2025. When we develop new user-interface elements we’ll test them against the relevant accessibility standards.
Discovery tool content
Graphs within reports do not have text descriptions. Graph results are included elsewhere on the page in text format. This does not meet WCAG 2.2 success criterion 1.1.1 (Non-text Content)
The BDC discovery tool content is hosted on a third party platform, provided by Potential.ly. Potential.ly carry out manual and automated accessibility testing, and currently the platform meets WCAG 2.1 AA requirements. Jisc works with Potential.ly to ensure that the platform continues to meet accessibility standards, and we conduct our own automated and manual accessibility tests to confirm compliance. Potential.ly has published an accessibility statement. Since we do not have full control over the platform, we are limited in our ability to make specific improvements.
Disproportionate burden
We are not claiming that it is a disproportionate burden to fix the issues on this site.
Content that's not within scope of the accessibility regulations
Although not within scope of the regulations, we are committed to improving the accessibility of the items highlighted below.
Older pdfs and other documents
The accessibility regulations do not require us to fix pdfs or other documents published before 23 September 2018 if they are not essential to providing our services.
Links to archived sites
Where services have closed we sometimes point to archived copies of old websites which are likely to have accessibility issues. Updating these archived copies is outside of our control as they are managed by third parties.
How we tested these websites
The accessibility of these websites was tested in November 2024 using several automated tools, including Site Improve, AQA, and Lighthouse, and where possible issues raised were addressed.
What we're doing to improve accessibility
Our roadmap includes the commission of work to improve accessibility on this website to address the non-compliance with accessibility regulations as outlined above.
Preparation of this accessibility statement
This statement was updated on 28th January 2024.
These websites were tested in November 2024. The tests were carried out by Jisc and third-party partners. These websites will be next retested in 2025 and the accessibility statement will be reviewed accordingly.
Content modified from the GOV.UK accessibility statement used through the Open Government Licence v3.0.