| |
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.
There are known issues with the:
- HTML: the underlying code used to create the website
- CSS: used to describe how HTML is shown on the pages
- JavaScript: a development language used to program some areas of the site
- 3rd party functionality: areas of the site which are developed by external 3rd party companies
- content: this includes web page content or documents
What to do if you have problems or queries
If you have any accessibility problems or feedback, please
email us at [email protected].
If you need to contact us about any other issues, please use our contact us page.
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 our 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 website fail.
Roadmap
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:
Main site
-
elements: some elements do not have an accessible name,
failing success criterion 1.1.1
-
images in documents: some images / figures do not
have an alt tag, failing success criterion 1.1.1
-
tables: heading elements are not declared and
role=presentation is not used, failing success criterion 1.3.1
-
documents: PDFs are not tagged so are not accessible by
screen readers, failing success criterion 1.3.1
-
tables: nested tables are used which do not make
sense when read in a screen reader, failing success criterion 1.3.2
-
links: these do not have underlining making it
hard for colour-blind users to see them, failing success criterion 1.4.1
-
keyboard users: onclick handlers do not have an equivalent
onkeyup or onkeydown handler, failing success criterion 2.1.1
-
keyboard users: onmouseover handlers are missing
onfocus handlers, failing success criterion 2.1.1
-
keyboard users: onmouseout handlers are missing
onblur handlers, failing success criterion 2.1.1
-
frames and iframes: some do not have a title
attribute, failing success criterion 2.4.1
-
document titles: some documents have no title failing
success criterion 2.4.2
-
page titles: pages titles are not unique, failing success
criterion 2.4.2
-
page language: this is not declared, failing success
criterion 3.1.1
-
markup errors: some pages have markup errors which cause
screen readers to miss content, failing success criterion 4.1.1
-
images/times media: some alt text contains placeholder
text, failing success criteria 1.1.1 and 1.2.1
-
images: an image has been updated but not its alt
attribute, failing success criteria 1.1.1 and 4.1.2
-
colours: some body or element colours are set, but not all
of them, failing success criteria 1.4.3,1.4.6 and 1.4.8
-
elements: some elements do not contain text or an img
with an alt attribute, failing success criteria 2.4.4, 2.4.9 and 4.1.2
Content that�s not within the scope of the accessibility regulations
-
PDFs/documents (pre September 2018): PDFs or other documents published before 23 September 2018 or documents that are not essential to providing our services
-
pre-recorded audio and video published before 23 September 2020
How we test the site
We re-assess a website or system for accessibility whenever
it undergoes a major modification.
We check all new content we add.
|
|
