We want as many people as possible to be able to use this website. We endeavour to meet the internationally recognised accessible website guidelines produced by the World Wide Web Consortium (W3C), working to AA level where possible.
AbilityNet has advice on making your device easier to use if you have a disability.
What isn’t accessible
We know some parts of this website are not fully accessible:
- you cannot modify the line height or spacing of text
- most older PDF documents are not fully accessible to screen reader software
- some PDFs have been created by third parties (such as journal papers) and may not be fully accessible
What to do if you cannot access parts of this website
If you need information on this website in a different format, like accessible PDF or large print, please contact us via the contact form.
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 us via the contact form.
If you have contacted us about an accessibility problem (e.g. because you needed information in a different format, or you think we’re not meeting the requirements of the accessibility regulations) but you feel that this has not been dealt with satisfactorily we want to know.
The first stage would be to raise your concern informally. The aim of this stage is to achieve a quick and easy solution for you. It would be appropriate to take the concern through the relevant contact listed above for reporting an accessibility problem.
But if we do not deal with your concern satisfactorily you can take it through to a formal complaint. See Lancaster University’s Concerns, complaints and enforcement information.
Technical information about this website’s accessibility
Ensemble 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, 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 links are redundant in that adjacent links go to the same URL.
- Some links on a page contain the same text (eg ‘Read more’).
- This doesn’t meet WCAG success criterion 2.4.4 Link Purpose (In Context) and 2.1.1 Keyboard.
- Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG success criterion 1.1.1 Non-text Content. We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
PDFs and other documents
- Titles: Some PDF documents do not have descriptive titles. This does not meet WCAG success criterion 2.4.2 Page Titled. We aim to update PDFs created within the project to include titles by September 2020.
- Language: Some PDF documents do not specify the default language of the document. This does not meet WCAG success criterion 3.1.1 Language of Page. We aim to update PDFs created within the project to include a language entry by September 2020.
- Bookmarks: Some PDF documents do not provide bookmarks within the document. This does not meet WCAG success criterion 2.4.5 Multiple Ways. Where the PDF is current, we aim to update them to include bookmarks by September 2020. We aim to update PDFs created within the project to include bookmarks by September 2020.
- Some PDFs are generated by third parties, such as journal papers. We do not intend to fix these and the document generation is outside of our control.
Text and content
- Headings: HTML headings are used inconsistently on our web pages, and our content is not always organised into well-defined sections. This makes it harder for users to get an overview of our content and how it is organised. This doesn’t meet WCAG success criterion 2.4.6 Headings and Labels. We continue to revise our content to improve our use of headings.
Navigation and accessing information
- There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
- It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This fails WCAG 2.1 success criterion 1.3.4 (orientation).
- It’s not possible for users to change text size. This fails WCAG 2.1 success criterion 1.4.4 (resize text).
Content that’s not within the scope of the accessibility regulations
- 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.
- Any new PDFs or Word documents we publish will meet accessibility standards.
How we tested this website
This website was last tested on December 2019. The test was carried out by Ensemble’s Project Administrator.
We assessed each page of our site against three lists provided at the following websites as well as using accessibility software ‘Wave’ and ‘Colour Contrast Analyser’.
What we’re doing to improve accessibility
Please contact the project administrator if you wish to see the action plan for improving accessibility. The site will be checked on an annual basis during the life of the project (ie until December 2021.)
This statement was prepared on 28th November 2019. It was last updated on 20th December 2019.