We want everyone who visits our website to be able to access the full range of services available, regardless of their skill or technology.
How accessible the site is
We know some parts of this website aren’t fully accessible.
What to do if you have problems or queries
If you have any accessibility problems or feedback, please email us at email@example.com.
If you need to contact us about any other issues, please email us at firstname.lastname@example.org.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond, please contact the Equality Advisory and Support Service (EASS).
Technical information about this website's accessibility
Durham County Council is committed to making its website accessible, in accordance with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Under the Equality Act 2010 we must ensure we do not unlawfully discriminate in our service delivery and make reasonable adjustments for people with disabilities where necessary. We are constantly working to improve the accessibility and usability of our site.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non compliance with the accessibility regulations
Information about which areas of the site fail.
A program of work is now underway to address issues, involving both our in-house developers and designers, and the companies who provide 3rd party functionality.
We aim to resolve the following by September 2021:
- Absolute positioning: some elements fail success criterion 1.4.4
- Paragraph tags: there are empty <p> tags which fail success criteria 1.1.1 and 1.3.1
- Icon fonts: these may fail success criterion 1.1.1
- Aria references: some are missing from code which fails success criteria 1.3.1, 3.3.2 and 4.1.2
- Navigation: an area of the navigation uses link text that is ambiguous and fails success criterion 1.3.1, 2.4.4
- Navigation content: some elements are too small to use accurately, failing success criteria 1.3.1, 1.4.5, 3.2.4, 1.4.4
- CSS for headings: this fails success criterion 1.3.1
- Block capital text: the homepage has some block capital text which fails success criteria 1.3.1, 1.4.5, 3.2.4 and 1.4.4
- Text alternative: CSS images need text alternatives, failing success criterion 1.1.1
- Skip navigation: local of skips may need to be updated to pass success criterion 2.4.1
- PDFs: the reading order of the PDF may not be correct (1.3.2, 2.1.1, 2.1.3, 2.4.3), the title is an image (1.1.1, 2.4.2), and images have no alt text (1.1.1)
Content that's not within the scope of the accessibility regulations
- pre-recorded audio and video published before 23 September 2020
- maps unless they provide core information
- content that's under someone else's control that we haven't paid for or developed ourselves:
- social media buttons
How we test the site
We re-assess a website or system for accessibility whenever it undergoes a major modification.
The code is checked using Tenon. Page content is manually checked every time it is updated.