Website Accessibility Statement

Using this website

This website is run by Darlington Borough Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

AbilityNet has advice on making your device easier to use if you have a disability.

 

How accessible this website is

Most of this website is compliant with the W3C WCAG 2.1 AA accessibility standard.  However, there are some parts of this website that are not fully accessible:

  • empty table header cells on show price lists
  • most of our older pdf documents
  • some forms are missing the correct labels
  • some videos are not correctly labelled
  • some out of date code is present on the site
  • there are some colour contrast issues on the pagination controls

 

What to do if you can’t access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll consider your request and get back to you in 10 working days.

 

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact the Web team by emailing the issue to mydarlington@darlington.gov.uk

 

Enforcement procedure

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’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

Darlington Borough Council is committed to making its websites 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 link text is used to link to different destinations which means people using a screen reader will hear the same link phrase but the links will take them to different pages or websites. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).

    We plan to make all exsting unique URLs on our pages have unique and descriptive link phrase by March 2020.  When we publish new content, we will make sure our hyperlinks meet this accessibility standard.

  • Some of our interactive elements do not have the required descriptive tags to inform screen reader users of the current state of the widget. This does not meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value, Missing required WAI-ARIA states or properties.

    We plan to make all existing interactive elements/widgets compliant by March 2020.  When we launch new interactive elements/widgets we will make sure they meet this accessibility standard.

  • Some of the links on the blog are only identifiable by their colour making them hard to see when in certain situations. This does not me WCAG 2.1 success criterion 1.4.1 Link identified only by colour.

    We plan to make all links compliant by March 2020. When we launch new features onto the website will make sure they meet this accessibility standard.

  • The Accessible show filter form doesn’t have a button on it. This does not me WCAG 2.1 success criterion under 3.2.2 On Input, Missing button in form.

    We plan to make the Accessible show filter option compliant by March 2020. When we launch new features onto the website will make sure they meet this accessibility standard.

  • Some pages are using HTML to format the content. Specific issue under 1.3.1 Info and Relationships HTML is used to format content

    We plan to make remove all HTML formatting and inline styling by March 2020. When we launch new features onto the website will make sure they meet this accessibility standard.

  • Some elements are not using unique IDs to identify themselves. This does not me WCAG 2.1 success criterion 4.1.1 Parsing Element ID is not unique and Specific issue under 1.3.1 Info and Relationships Element ID is not unique.

    We plan to make all components use unique IDs by March 2020. When we launch new features onto the website will make sure they meet this accessibility standard.

  • The is currently no option to skip repeated elements. This does not me WCAG 2.1 success criterion specific issue under 2.4.1 Bypass Blocks No option to skip repeated content.

    We plan to add these controls to the website by March 2020. This will be added to the core code of the site so this standard will always be met.

  • A calendar plugin that is used to select dates identifies itself in a way that could be misunderstood by a screen reader as an error. This does not me WCAG 2.1 success criterion specific issue under 3.3.1 Error Identification Aria-atomic="true" missing on error container

    We plan to upgrade the plugin or write a patch to fix this by March 2020.


Content that’s not within the scope of the accessibility regulations

PDFs and other documents

Some of  older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value). 

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages. 

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 is tested every 10 days. The tests are carried out by the Darlington Borough Council web team using Siteimprove’s accessibility reports.  Tests are scheduled automatically and are monitored by the web team.

What we are doing to improve accessibility

Our accessibility road map below shows how we aim to improve accessibility across this website.

Issue

Target Fix Date

2.4.4 Link Purpose (In Context)

March 2020

4.1.2 Name, Role, Value, Missing required WAI-ARIA states or properties

March 2020

1.4.1 Link identified only by colour

March 2020

3.2.2 On Input, Missing button in form

March 2020

1.3.1 Info and Relationships HTML is used to format content

March 2020

4.1.1 Parsing Element ID is not unique

March 2020

1.3.1 Info and Relationships Element ID is not unique

March 2020

2.4.1 Bypass Blocks No option to skip repeated content.

March 2020

3.3.1 Error Identification Aria-atomic="true" missing on error container

March 2020

 

This statement was prepared on 08/10/2019.