Accessibility statement for Library Hub Compare

This statement applies to content published on compare.libraryhub.jisc.ac.uk

This website is run by Jisc and 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

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:

  • There is an issue with text colour contrast in the site footer.
  • We have issues with some interactive elements
  • There are issues with navigating parts of the website using just a keyboard

Hotjar non-compliance with the accessibility regulations

  1. 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].
  2. 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].
  3. 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].
  4. The Hotjar branding link is not underlined. This fails WCAG 2.1 success Criterion 1.4.1 (Use of Color [Level A].
  5. 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].
  6. 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].
  7. Radio buttons, checkboxes and text areas have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.11 (Non-Text Contrast) [Level AA].
  8. 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].
  9. 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].
  10. 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].
  11. 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 Hotjar third party software

We assessed the Hotjar survey software tool against WCAG 2.1 AA using

  1. Manual techniques
  2. Firefox accessibility inspector
  3. SiteImprove browser extension for Chrome
  4. Axe browser extension for Chrome, noting this was not capable of testing inside the Hotjar panel

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:

We'll consider your request and get back to you.

If you cannot view the map on our 'contact us' page, call or email us for directions.

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, please contact help@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 website 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.1 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

Some text and background combinations in the page footer don't have enough contrast. They don't meet WCAG 2.1 success criterion 1.4.3 (contrast - minimum). We are working on these.

Some of our interactive forms are difficult to navigate using a keyboard because some form controls are missing a 'label' tag. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value). We are working on these.

Our Search History may be difficult for assistive technologies to parse because of duplicate id attributes. This does not meet WCAG 2.1 success criterion 4.1.1 (parsing). We are working on these.

Problems with the ARIA element may make some pages difficult to navigate. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value). We are working on these.

How we tested this website

The website was last tested in September 2020. The test was carried out by Jisc.

We tested all service interface pages and supporting web pages.

Further testing is also planned during 2022 and we will respond to any recommendations that arise from that work.

Third-party tools: Accessibility statement for Hotjar Surveys - June 2022

We embed pop-up HotJar surveys on the site to collect occasional user feedback. We know there are accessibility issues, but at present we don't have a more accessible alternative which meets our requirements around GDPR and Information Security. We have raised the issues with HotJar, who are working on changes to make their surveys fully accessible. At present they do not have an estimated completion date for this project. Where we include a HotJar survey, we will always provide users with a link to a more accessible alternative at the start.

Hotjar non-compliance with the accessibility regulations

  1. 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].
  2. 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].
  3. 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].
  4. The Hotjar branding link is not underlined. This fails WCAG 2.1 success Criterion 1.4.1 (Use of Color [Level A].
  5. 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].
  6. 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].
  7. Radio buttons, checkboxes and text areas have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.11 (Non-Text Contrast) [Level AA].
  8. 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].
  9. 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].
  10. 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].
  11. 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 Hotjar third party software

We assessed the Hotjar survey software tool against WCAG 2.1 AA using

  1. Manual techniques
  2. Firefox accessibility inspector
  3. SiteImprove browser extension for Chrome
  4. Axe browser extension for Chrome, noting this was not capable of testing inside the Hotjar panel

What we're doing to improve accessibility

We will carry our automated testing of new features to avoid introducing accessbility problems. We will undertake regular service testing and respond to any accessibility issues identified. We're also committed to working on the issues above.

This statement was prepared on 26th August 2020. It was last reviewed on 27th October 2021

.

Content modified from the GOV.UK accessibility statement - used through the Open Government Licence v3.0.