Accessibility Statement

We want everyone who visits our website to be able to access the full range of services available, regardless of their skill or technology.

The current version of this website was launched in 2018, but individual elements of it may have been updated since then.

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 council@bishopauckland-tc.gov.uk.

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

Bishop Auckland Town 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-compliance listed below.

Non-compliance with the accessibility regulations

  • headings: some headings don’t cascade inside some features on some web pages failing success criterion 1.3.1
  • headings: empty headings failing success criterion 2.4.6
  • forms: some have blank labels or titles, failing success criterion 4.1.2
  • frames and iframes: some do not have a title attribute, failing success criterion 2.4.1
  • images: some images do not have an alt tag failing success criterion 1.1.1
  • images: some alt text is the same as the image’s file name, failing success criteria 1.1.1 and 1.2.1
  • images: some adjacent images have identical alt tags causing screen readers to stutter as the same text is read out twice, and failing success criterion 1.1.1
  • background colours: some text / background colours do not have enough contrast, failing success criterion 1.4.3
  • hidden elements: an element with aria-hidden=true contains focusable content, failing success criterion 1.3.1
  • document titles: some documents have no title failing success criterion 2.4.2
  • elements: some elements do not contain text or an img with an alt attribute failing success criterion 2.4.4, 2.4.9 and 4.1.2
  • page language: this is not declared, failing success criterion 3.1.1
  • documents: PDFs are not tagged so are not accessible by screen readers, failing success criterion 1.3.1
  • tables: heading elements are not declared and role=presentation is not used, failing success criterion 1.3.1
  • tables: that have two or more logical levels of row or column headers, markup to associate data cells and header cells not used, failing success criterion 1.3.1
  • page titles: some pages have duplicate title failing success criterion 2.4.2
  • links: these do not have underlining making it hard for colour-blind users to see them, failing success criterion 1.4.1
  • outline / border style: the stylesheet makes it difficult to see the dotted link focus outline, failing success criterion 2.4.7
  • stylesheets: some content is in stylesheet, making it unavailable to screen readers and users who are not using the stylesheet, failing success criterion 1.3.1
  • IDs: some pages has duplicate IDs failing success criterion 4.1.1
  • tags: an end tag strong violates nesting rules, failing success criterion 4.1.1

Accessibility Roadmap

As stated in the non-compliance section, the known issues are listed below:

  • HTML – the underlying code used to create this website.
  • CSS – used to describe how HTML elements are displayed on this website.
  • JavaScript – a development language used to program behaviours on this website.
  • 3rd Party Functionality
  • Content – this could include web page content or associated PDFs on this website.

A program of work is now underway to address these issues and involves working with Durham County Council’s in-house developers/designers as well as third party functionality providers.
We aim to resolve the above items by September 2021.

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 would be disproportionate burden to update, if they are not essential to providing our services.
  • pre-recorded audio and video published before 23 September 2020.
  • live audio and video.
  • interactive maps unless they provide core information.
  • content that’s under someone else’s control that we haven’t paid for or developed.

How we test the site

We re-assess the website for accessibility whenever it undergoes a major modification.
Most page content is checked each time that it is updated.