This statement applies to content published on the library.nhs.uk domain.
This website is run by Library and Knowledge Services. 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:
- 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)
How accessible this website is:
Parts of this website are not fully accessible. For example:
- some tables do not have row headers
- some images do not have good alternative text
- many documents are in PDF format and are not accessible
Reporting accessibility problems with this website:
If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, contact us.
Enforcement procedure
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
Library and Knowledge Services 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 partially complies with the Web Content Accessibility Guidelines version 2.1 AA standard.
Content that’s not within the scope of the accessibility regulations
Images on pages do not always have suitable alternative text. Some images are missing alternative text, some have incomplete text and some have ‘placeholder’ as alternative text. This fails WCAG 1.1.1A success criterion (Non-text Content).
We will create guidance to help content authors understand the requirements for captions and audio description for all new videos. This relates to WCAG 2.1A success criteria 1.2.2 (Captions (Prerecorded)) and 1.2.3 Audio Description or Media Alternative (Prerecorded).
PDFs and other documents
Many documents are not accessible as they are missing text alternatives.
To report any problems or request documents in an alternative format please contact us.
How we tested this website
This website is being tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA. Library and Knowledge Services carry out these tests internally.
Statement publication date: 20 February 2020. Last update: 07 April 2020.
Home page issues
| # | Issue and description | Where the issue was found | 12-week update | Comments |
|---|---|---|---|---|
| 1 | WCAG 2.1.1 Keyboard Users should be able to use a keyboard to access all content and functionality of a web page. This means the page can be used by people with no vision as well as people who use alternative keyboards or input devices that act as a keyboard. | The close button within the cookie settings is not accessible using the keyboard | Fixed | |
| 2 | WCAG 2.4.7 Focus Visible A visible focus helps users know which element has keyboard focus and where they are on the page. When an element gets focus there should be a visible border around it. Highlighting the element that has keyboard focus or is hovered over can provide information like whether the element is interactive or the scope of that element. Operating systems have a native indication of focus, which is available in many browsers. The default display of the focus indicator is not always highly visible and may even be difficult to see especially on coloured backgrounds. | The keyboard focus is not visible on the ‘Search’ button The keyboard focus is not visible on the map under ‘Find your local NHS knowledge and library service’ | Fixed | |
| 3 | WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast. Poor colour contrast makes it difficult for someone with sight loss to see the content properly. If there is a big difference between the background and foreground colours it should be much easier to see the difference between them. | Placeholder text for ‘Search this site’, at the top of the webpage, does not have sufficient colour contrast | Fixed | |
| 4 | WCAG 2.4.4 Link Purpose (In Context) and WCAG 4.1.2 Name, Role, Value: Links must have discernible text. Issue found using Deque Axe. All link names should be accessible by a screen reader and be descriptive enough to tell a user where that link will take them. Common issues include: the inner link text not being visible duplicate link labels the link not being focusable All links should receive focus and link text should not be hidden as this will stop a screen reader from relaying the link information. | This refers to the link at the bottom of the map. Element Location: a[href$=”hlisd.org/”] <a href=”https://www.hlisd.org/“> | Fixed |
Contact page issues
| # | Issue and description | Where the issue was found | 12-week update |
|---|---|---|---|
| 1 | WCAG 2.1.1 Keyboard | The close button within the cookie settings is not accessible using the keyboard | Fixed |
| 2 | WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast. | Placeholder text for ‘Search this site’, at the top of the webpage, does not have sufficient colour contrast | Fixed |
Knowledge Hub page issues
| # | Issue and description | Where the issue was found | 12-week update |
|---|---|---|---|
| 1 | WCAG 2.1.1 Keyboard | The close button within the cookie settings is not accessible using the keyboard | Fixed |
| 2 | WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast. | Placeholder text for ‘Search this site’, at the top of the webpage, does not have sufficient colour contrast There is poor colour contrast when the keyboard tabs onto ‘Start your search’ | Fixed |
Health Information page issues
| # | Issue and description | Where the issue was found | 12-week update |
|---|---|---|---|
| 1 | WCAG 2.1.1 Keyboard | The close button within the cookie settings is not accessible using the keyboard | Fixed |
| 2 | WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast. | Placeholder text for ‘Search this site’, at the top of the webpage, does not have sufficient colour contrast | Fixed |
Embedded Knowledge and Library Specialist Roles within Primary Care Training Hubs: Summary of the final evaluation, July 2024 issues
| # | Issue and description | Where the issue was found | 12-week update |
|---|---|---|---|
| 1 | WCAG 2.4.2 Page titled PDF documents should have titles that describe the topic or purpose of the page. Titles help users understand the topic without having to read the entire document. Without a descriptive title a user may need to spend time searching the document to decide whether the content is relevant. When a PDF is displayed in a browser the title will usually be displayed in the top title bar or as the tab name. | The page title is missing within the settings of the PDF document | Document was deleted by site owner |
| 2 | WCAG 1.1.1 Non-text content People with sight loss may not see an image clearly on a page. You need to use a text alternative to share the information. The alternative text must describe the information or function represented by the image. Screen readers can share the alternative text with the user. In PDF documents you must ensure that images are tagged correctly with alternative text. | The document has elements that do not have alternative text | Fixed |
Accessibility statement page issues
| # | Issue and description | Where the issue was found | 12-week update |
|---|---|---|---|
| 1 | WCAG 2.1.1 Keyboard | The close button within the cookie settings is not accessible using the keyboard | Fixed |
| 2 | WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast. | Placeholder text for ‘Search this site’, at the top of the webpage, does not have sufficient colour contrast | Fixed |
Accessibility statement comments
https://library.nhs.uk/accessibility-statement/
An accessibility statement for the website was found but we found the following issues.
| # | Issue and description | 12-week update |
|---|---|---|
| 1 | The compliance status does not match the results of our testing or is not using the correct wording.Please note the statement advises it is compliant to WCAG 2.1, however the legal standard is WCAG 2.2. | |
| 2 | A heading for “Non-accessible content” was not found. | |
| 3 | Known accessibility issues are not included within the ‘non-accessible content’ section. You need to review your accessibility statement to cover the issues found in this report and any others found during your own audit. | |
| 4 | Content is included in the out of scope section that should be listed in another part of the statement. | |
| 5 | A heading for “Preparation of this accessibility statement” was not found. | |
| 6 | A statement preparation date was included but needs to be worded correctly. | |
| 7 | A statement review date was included but needs to be worded correctly. | |
| 8 | The statement has not been reviewed in the last year and is out of date. | |
| 9 | The heading for “Feedback and contact information” is not worded correctly. |