This website is run by NHS West Lancashire Clinical Commissioning Group.
We want as many people as possible to be able to use our website, and we have designed it to be accessible.
How you can use this website
On this website, you should be able to:
- change colours, contrast levels, and fonts
- zoom in up to 300% with text staying visible on the screen, and most images scaling without resolution loss
- navigate most of the website using a keyboard
- navigate most of the website using speech recognition software
- read most of the website using a screen reader, including the latest versions of JAWS, NVDA, and VoiceOver
- read most of the website on devices without a screen, like a braille computer
- We’ve made the website text as simple as possible to understand, using the principles of plain English.
- Use the Browsealoud features to access read-aloud and translation services.
Some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means.
If you have a disability then AbilityNet has the advice to help you make your device easier to use.
How accessible this website is
The majority of this website is fully accessible, and we regularly review the site to identify any new problems.
We know that some parts of the website aren’t fully accessible:
- we have a large number of old publication documents which are in PDF format and haven’t been designed for accessibility
- some content is embedded in our website, such as maps and videos, and you cannot easily scale these on-screen (but you can open a full-screen version)
How to get information in an accessible format
If you have problems accessing information on this website, or would like any of our work in a different format like a more accessible PDF, large print, easy read, audio recording, or braille:
- email firstname.lastname@example.org
- telephone us on 01695 588 000
We’ll consider your request, and aim to get back to you within 3 days.
Reporting accessibility problems
We’re always looking to improve the accessibility of the website.
If you find any problems which aren’t listed on this page or think that we’re not meeting the requirements of the accessibility regulations then please email email@example.com to let us know.
If you are not happy with your response from the communications and engagement team when you raise an issue please contact our customer care team in the first instance.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing 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
We are committed to making our 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, due to the non-compliances listed below.
Issues with technology
The vast majority of our website works correctly on any web technology.
For security reasons, we only support TLS 1.2 and higher security protocols, and this means that some older browsers will not show the site.
How our site looks and works is based on HTML5, and we test for and support the following browsers:
- Google Chrome (versions in support)
- Mozilla Firefox (versions in support)
- Microsoft Internet Explorer (version 11 only)
- Microsoft Edge (versions in support)
- Apple Safari (versions in support)
We also test in the Lynx browser to ensure that the site renders correctly for non-screen users.
You may experience unexpected behaviour in other browsers, although we use fully validated code which should work on any browser.
Issues with links
We are aware of the following issues within the links on our site:
- some link text doesn’t make sense when read on its own (for example ‘click here’)
- on some pages, there are multiple links with the same link text but different destinations on one page
- many older PDF files contain broken links which do not resolve – we do not intend to resolve these as it is a disproportionate burdenfor files which are no longer in active use
We scan the site regularly for broken links and look to fix them as soon as they are identified.
The communications and engagement team is working through the links which don’t make sense on their own, and we aim to have fixed these by April 2022.
Issues with PDFs and other documents
PDFs are not able to comply with the requirements of the web accessibility standard, and we do not generally upload new PDFs. Where we do create new PDFs, we use the PDF/A standard which is more accessible.
Our site contains a large number of PDFs created in previous years, especially in policies and information publications.
Where these are no longer being updated, we do not intend to recreate them in accessible versions as this would be a disproportionate burden. 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.
By April 2022 we intend to have completed the process of converting PDFs and word documents still in active use into accessible web formats.
We do not generally add new PDFs to our site. There are some exceptions:
- we add some PDFs as downloads of reports or publications, for example governing body papers and policies.
- our annual reports, which must, by law, be laid before parliament in a printed version, and then appear unaltered
- downloads intended for print purposes, such as posters
Issues with images and video
We strive to make all of our content accessible. We are aware of the following issues with images and video on our site:
- Video content uses automated closed captioning and transcripting, and this is often inaccurate. By April 2022 we will review these captions and ensure their accuracy manually.
- Some of the images on our site do not have suitable alt text. By April 2022 we intend to have reviewed all of these images.
Issues with text and content
There are some issues with text and content which we are aware of:
- not all of our content reaches our target of being plain English. We are resolving this as content comes up through its review cycle, and this should be largely complete by April 2022.
- some of our page titles are long, causing a technical fail on descriptive titles for web pageswhich require titles to be short. In most cases, this is related to legal or formal names for publications. We are not going to fix this, as the content is still understandable, and changing titles might cause compliance issues.
How we test this website
We conduct internal testing against known accessibility issues which are not able to be found through automated testing, on a sampled basis.
Accessible features we test manually
There are a number of accessibility features which we test manually, which include:
- colour contrast, which is done at the design stage by using tools to check we meet the AAA standard of a contrast ratio of 4.5:1
- skip links, which feature across the site
- aiming for plain English
- manual check against the W3C validator
- ensuring that page elements render correctly at all sizes, including when zoomed to 500%
- assessing content for readability using a mixture of tools which use mathematical methods to assess readability
- checks of colour contrast
- examining microdatamarkup and alt text using special tools
- checking content in a text-only browser
- using screen readers to read text aloud
- using disability simulation tools to browse the website
What we are doing to improve
We are actively looking to improve the accessibility of our website.
The improvements below have been identified on our current work schedule.
Accessibility improvement roadmap
|Target Date||Item of work||Type of work||Status|
|April 2022||Site links||Content||Ongoing|
|April 2022||Video captions||Content||Ongoing|
|April 2022||Image Alt Text||Content||Ongoing|
|April 2022||PDFs and documents in accessible formats||Content||Ongoing|
|April 2022||Make content plain English||Content||Ongoing|