This website is managed by Calderdale Metropolitan Borough Council. We want as many people as possible to be able to use this website.
This means you should be able to:
- Change text format, colours and contrast.
- Zoom to 300% without problems.
- Navigate most of the website using just a keyboard or speech recognition software.
- Use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
For advice on how to make your device easier to use, visit: My Computer My Way (AbilityNet).
How accessible is this website
Parts of this website are not fully accessible. For example:
- Many PDF documents are missing document structure and alternative text.
- Some colour combinations have low contrast levels.
- Some links rely on the context of surrounding content to make sense.
- We use third party providers to deliver parts of our online service.
- We cannot guarantee their level of accessibility.
- Where possible, we are working with external providers to improve accessibility.
Feedback and contact
If you need information on our website in a different format, please email email@example.com and tell us:
- The web address (URL) of the page
- The information you need and the format you require
We will consider your request and get back to you within 10 working days.
Report issues with our website
We are always looking to make our website more accessible.
If you find a problem not listed on this page or believe the site is not accessible, let us know:
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 are 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. this is 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. (Non-compliances and exemptions listed below.)
Non-compliance with the accessibility regulations
- Some images may have limited or no alternative text. Others that are decorative may not be published in a way that allows assistive technology to ignore them. This relates to Success Criterion 1.1.1 Non-text Content.
- Some videos may not have suitable text alternatives such as transcripts and closed captions. This relates to Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).
- There are instances where structural mark-up has been used in a way that represent relationships in the content. An example of this is the idiomatic text element being used for icons. This relates to Success Criterion 1.3.1 Info and Relationships.
- Certain colour combinations need updating to improve contrast. An example of this is our old style alert banners that contain red text on a light red background. This relates to Success Criterion 1.4.3 Contrast (Minimum).
- Some pages contain elements that cannot be fully operated using a keyboard alone. This includes elements that do not receive focus or have limited or no visible focus state. This relates to Success Criterion 2.1.1 Keyboard and Success Criterion 2.4.7 Focus Visible.
- The search button is labelled as 'go' on older version 1 themed pages. On newer version 2 themed pages it is labelled as 'search'. This relates to Success Criterion 3.2.4 Consistent Identification.
- Some pages contain elements that are not nested according to specification. For example, the
<a>elements must not be a descendant of the
<button>element. This relates to Success Criterion 4.1.1 Parsing..
- There are instances where embedded frames such as Google maps or YouTube videos do not contain titles or labels. This relates to Success Criterion 4.1.2 Name, Role, Value.
- Some web forms display error messages when incorrect information is provided. Sometimes these messages cannot be programmatically determined through role or properties. This relates to Success Criterion 4.1.3 Status Messages.
PDFs and non-HTML documents
Many of our PDFs are not fully accessible due to:
- Missing titles.
- Missing document language.
- Missing text alternatives.
- Missing document structure.
- Incorrect reading order.
Content not within the scope of the accessibility regulations
The regulations do not require us to:
- Fix PDFs or other documents published before 23rd September 2018;
- unless they are essential to provide our services.
For essential PDFs, we plan to either fix or replace these with accessible HTML pages.
What we are doing to improve accessibility
We plan to move our website to a new system in 2022. At this time, we will:
- Focus on it being more accessible;
- and fix all areas listed under 'Non-compliance with the accessibility regulations'.
We are reducing the number of PDFs we publish in favour of HTML web pages. Where PDFs are the right format to use:
- We correct all issues before they are published.
- If this is not possible, we publish the PDF along with an accessible alternative.
We are moving our web forms into a new system as well as converting PDF forms into web forms.
We are investing in resources and training, to:
- Make teams aware of the barriers posed by content not being accessible;
- and to help teams create accessible content going forward.
Preparation of this accessibility statement
This statement was prepared on 19th November 2019. It was last reviewed on 4th February 2022.
This website was last tested on 15th December 2021. The test was carried out by Calderdale Council's Webteam.
How this site was tested
Website analytics were used to find popular pages. A sample of these were used that had varied page layouts and different functionality.
Tests were done using:
- A Windows 10 device with:
- A 14-inch screen (resolution of 1366 by 768 pixels)
- and also 24-inch monitor (resolution of 1920 by 1080).
- Smaller devices were emulated using developer tools.
- Pages were loaded in the Google Chrome web browser.
- Tests were both automated and manual checks.
Automated tests using:
- WAVE (Web Accessibility Evaluation Tool).
- SiteImprove Accessibility Module.
- aXe dev tools.
- Use a page without a mouse.
- Read a page with NVDA screen reader software.
- View a page at different zoom settings.
- Accurate media alternative text.
- Distinguishable and accurately labelled hyperlinks.
- Use of sensory characteristics.
- Enough colour contrast.
- Use of semantic markup.