Accessibility statement for RDMToolkit.jisc.ac.uk
This statement applies to content published on RDMToolkit.jisc.ac.uk. It does not apply to content on other jisc.ac.uk subdomains (for example, my.jisc.ac.uk) or the main jisc website (www.jisc.ac.uk).
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 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)
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:
- Some older PDF documents aren’t 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
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 contact us:
We’ll consider your request and get back to you.
Reporting accessibility problems with this website
If you find any problems that aren’t listed on this page or think we’re not meeting the requirements of the accessibility regulations, contact firstname.lastname@example.org.
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 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 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 this type of embedded player. 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.
We embed YouTube videos on the site. We know there are accessibility issues with this type of 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 and we will send one through to you.
Some text and background combinations don’t have enough contrast – especially section ‘tags’. They don’t meet WCAG 2.1 success criterion 1.4.3 (contrast – minimum). We are working on these.
Some of our links include adjacent links going to the same place, where a single link is needed. This doesn’t meet WCAG 2.1 success criterion 2.4.4 (link purpose – in context). We are addressing this on a rolling basis.
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 are addressing these on a rolling basis.
Our footnote and abbreviations aren’t fully accessible to screen readers. This does not meet WCAG 2.1 success criterion 2.1.1 (keyboard). We plan to develop an alternative to our current footnote approach. We are investigating what can be done to improve our abbreviations.
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.
Issues with images, video and audio
There is unnecessary or unhelpful alt text on some images, especially where diagrams are used. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content). We are working to correct these.
Issues with interactive tools and transactions
There is inadequate context with some interfaces – especially around listing pages and pagination controls. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to redevelop the pages where this is an issue in 2020/2021.
Role and state information is missing from some interactive elements on older pages. These do not meet WCAG 2.1 success criterion 4.1.2 (name, role value). Older pages will be retired or redeveloped in 2020/2021.
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). Some of these pages are due to be redeveloped in 2020, we will be reviewing the others and whether to retire them or remove them.
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.
Links to archived sites
Where services have closed we sometimes point to archived copies of old websites. There are likely to be issues with these copies. As snapshots taken by a third-party we wouldn’t be able to update these. As archived sites however, they are exempt from meeting the accessibility regulations.
What we’re 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 18 September 2020. It was last updated on 18 September 2020.
Content modified from the GOV.UK accessibility statement – used through the Open Government Licence v3.0.