Accessibility statement for Yewno Discover
This accessibility statement applies to discover.yewno.com, which hosts the University of Nottingham visual discovery system Yewno Discover, produced by the supplier Yewno. Yewno Discover features an interface known as a ‘knowledge map’ which arranges concepts visually, showing how concepts are related and clustered within the research literature.
This website is run by University of Nottingham Libraries in partnership with Yewno. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours and contrast levels
We’ve also made the website text as simple as possible to understand.
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:
- It is not possible to navigate to all elements of the site using a keyboard.
- You may have difficulty reading the interface when using a mobile device or zooming in.
- You may have issues with accessing the site using assistive technology, for example a screen reader, due to missing or misapplied attributes within the code.
- You may have difficulty interacting with some parts of the interface due to low colour contrast.
- Yewno searches a similar collection of resources to our discovery system NUsearch. If you experience trouble accessing Yewno, we recommend you try your search in NUsearch instead.
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 within 10 working days.
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, contact University of Nottingham Libraries via library-helpline@nottingham.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).
Contacting us by phone or visiting us in person
Find out how to contact us: https://www.nottingham.ac.uk/Library/help/.
Technical information about this website’s accessibility
University of Nottingham 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Navigation using a keyboard
You may find it difficult to navigate using a keyboard. We are reporting these issues to Yewno and will work with them to address.
- There are several areas where the system is not accessible by keyboard only. This fails WCAG 2.1 success criterion 2.1.1 (keyboard). Key issues are:
- Areas which cannot be accessed using the tab key including the knowledge map, the slider to ‘Adjust from most to least relevant’, the ‘Settings’ and ‘Help centre’ buttons and the documents list accessed by selecting a concept on the knowledge map and then the ‘Documents’ tab.
- When selecting a concept on the knowledge map and then the ‘Concepts’ tab, the tab key moves between the concept and the language indicator (such as ‘EN’) rather than between concepts.
- When selecting a concept on the knowledge map, and then the ‘Overview’, ‘Concepts’ or ‘Documents’ tabs, it is not possible to use the the left and right keys to switch between tabs.
- After selecting the ‘Settings’ button it is not possible to exit the opened section using the keyboard. This fails WCAG 2.1 success criterion 2.1.2 (no keyboard trap).
- After selecting the ‘Settings’ button or when selecting a concept on the knowledge map, the ‘Documents’ tab and then the documents list, it is possible to tab out of the opened sections around the screen. This fails WCAG 2.1 success criterion 2.4.3 (focus order).
- The keyboard focus indicator is not visible on the ‘Sign into your account’ button or ‘Settings’ button. This fails WCAG 2.1 success criterion 2.4.7 (focus visible).
Appearance of interface
You may have difficulty reading the interface when using a mobile device or zooming in. Some elements of the page also have low colour contrast. We are reporting these issues to Yewno and will work with them to address.
- The interface does not orientate appropriately on a mobile device. This fails WCAG 2.1 success criterion 1.3.4 (orientation).
- It is not possible to use the page when zoomed to 200%. This fails WCAG 2.1 success criterion 1.4.4 (resize text).
- The page does not reflow when zoomed. This fails WCAG 2.1 success criterion 1.4.10 (reflow).
- There is insufficient colour contrast on the text which appears upon choosing ‘Multiple-select’ i.e. ‘Generate relationship…’ and ‘Create knowledge map…’ or on the text under ‘Notebook’ when signed in. This fails WCAG 2.1 success criterion 1.4.3 (contrast (minimum)).
- There is insufficient colour contrast on the arrow button used to close the panel which appears when clicking ‘Search’, ‘Journey’ or ‘Notebook’, on the ‘Notes’, ‘Snapshot’, ‘Multi-select’ options, and on the tool to ‘View and select knowledge map layers’. This fails WCAG 2.1 success criterion 1.4.11 (non-text contrast).
Use of markup
You may have trouble interpreting the contents of the page due to missing or misapplied markup which can otherwise aid systems in interpreting and presenting web content. This can cause particular issues when using assistive technology. We are reporting these issues to Yewno and will work with them to address.
- Images such as the knowledge map and ‘Zoom in’ and ‘Zoom out’ and ‘Multi-select’ buttons are coded as decorative, but they convey information that is not available elsewhere. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
- The ‘Search concept’ bar needs instructions to show the user what to do – this is not clear from the label alone. This fails WCAG 2.1 success criterion 3.3.2.
- When selecting a concept on the knowledge map and then a concept from the ‘Concepts’ tab, headings are displayed incorrectly. There is also a missing heading level. This fails WCAG 2.1 success criterion 2.4.6 (headings and labels).
- The page has no language attribute assigned in html. This fails WCAG 2.1 success criterion 3.1.1 (language of page).
- The ‘Filter Documents By’ box uses incorrect tags. This fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence).
- There are multiple duplicate IDs in the code. This fails WCAG 2.1 success criterion 4.1.1 (parsing).
- There are missing elements for accessibility. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 4.1.2 (name, role, value). Key issues are:
- There are missing ARIA roles in some elements.
- The ‘Search concept’ bar has an ARIA role but no label.
- The ‘Settings’ button is set as a link but does not function as one.
- When using the ‘Search concept’ bar the produced search results have an inappropriate widget role assigned.
What we’re doing to improve accessibility
We are actively reviewing content and have introduced new working practices with a focus on user needs and providing inclusive content to our diverse audiences.
We are engaging with Yewno to highlight and develop accessibility requirements. We will consider accessibility as a key requirement when reviewing our pilot of Yewno Discover, which ends in September 2021.
Preparation of this accessibility statement
This statement was prepared on 5 February 2021. It was last reviewed on 5 February 2021.
This website was last tested in February 2021. The test was carried out by University Nottingham Libraries.
We used this approach to deciding on a sample of pages: testing by stratified sampling. We sampled the main page, and example pages within the page types Yewno generates, including searches of Yewno, subpages on concepts, and documents lists. We tested features when signed in and not signed in.