YorSearch is a web-based discovery system from Ex Libris (Primo) used to search the University of York Library’s collections.
Primo is continually designed and developed to meet Level AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions.
The University is committed to providing equality of access to services and facilities This page provides information about accessibility features and limitations of YorSearch. It also provides tips and tools for improving your experience using YorSearch.
On most pages on our website you should be able to:
AbilityNet’s My Computer My Way pages have advice on adjustments you can make to your computer, laptop, tablet or smartphone to make it easier to use.
We use Siteimprove to monitor the accessibility of our website. We currently score 81 out of 100 for accessibility, based on the automated tests it carries out.
We conduct regular user research with students using assistive software.
We know some parts of this website are not fully accessible:
If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, please report an accessibility issue.
University of York students and applicants can follow our complaints 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, you can contact the Equality Advisory and Support Service (EASS).
The University of York is committed to making its website 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, because of the issues below:
Most of Primo can be navigated with a keyboard alone, but there are a small number of areas that are currently inaccessible or hard to use:
Primo is designed to be used with screen readers. User interface components are given accessible names, roles and values that can be determined and read by assistive technologies. However, there are some features which are currently inaccessible or hard to use:
Primo is built to be responsive, meaning you should be able to use all of Primo’s features regardless of the device you are using, the zoom level in your browser or the orientation (vertical or horizontal) of the device. There are a few areas that may cause difficulty when text is zoomed beyond 200%. Text is clipped in:
In addition, the pagination controls are not displayed when the browser is zoomed to 400%. Part of content (for example, resource title) might be not visible due to "BACK TO RESULTS LIST" overriding its view.
While most text throughout Primo meets minimum colour contrast standards, there are cases where text and icons do not have enough contrast with the background colour.
If colour contrast is a concern for you, we recommend utilizing one of the free browser plugins that can increase text/background colour contrast, such as the High Contrast extension for Google Chrome.
Primo code is checked for accessibility using a range of automated and manual checks including but not limited to:
Primo is tested on the latest versions of Firefox, Safari, Chrome and Edge, and on devices including Mac and Windows computers, and Android and iOS devices.
At the University of York an e-accessibility working group has been formed, with representation from services from around the University. The group is leading on several initiatives to make digital content easier for everyone to use.
Making content accessible is an ongoing effort at Ex Libris. They state a commitment to working with the community to ensure meeting customers’ needs. A list of their ongoing efforts include:
This statement was prepared on 6th January 2022. It was last reviewed on 1st September 2022.
This website was last tested on 2nd February 2022. The test was carried out manually, and using the axe DevTools v4.23.0.