This statement applies to content published on https://subscriptionsmanager.jisc.ac.uk/.
Licence subscriptions manager 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:
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website aren’t fully accessible:
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.
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").
Jisc is committed to making Licence subscriptions manager 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.
Some text and background combinations don’t have enough contrast - especially around navigation in the footer, and section "tags". They don’t meet WCAG 2.1 success criterion 1.4.3 (contrast - minimum). We are working on these.
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 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
Our PDF and Word documents don’t meet accessibility standards - for example, they are not marked up so they are not accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
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.
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.
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.
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.
An in-depth accessibility audit conducted was completed in 2019.
Whenever new features are released they must meet WCAG 2.1 AA. We’re also committed to working on the issues above. Specifically we are developing an accessible template for our PDF and Word documents that will meet accessibility guidelines for new documents and will also replace those older documents which are essential to providing our service.
This statement was prepared on 9 August 2019. It was last updated on 28 September 2020.