Please note we are currently working to rectify the accessibility issues detailed below and this page will be periodically updated as this process continues.

In the meantime if you have any issues accessing the content on this site please contact us at

This accessibility statement applies to Durham Insight.

We want as many people as possible to be able to use this website. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible the site is

We know some parts of this website aren’t fully accessible.

Feedback and contact information

If you need information on this website in a different format or have any feedback, please email us at

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please email

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

Durham Insight is committed to making its website accessible, in accordance with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

  • documents: some PDFs are not machine readable, failing success criterion 1.1.1
  • documents: some PDFs are not tagged, or headings are not defined correctly, failing success criterion 1.3.1
  • documents: some PDFs do not have a title, or their titles are weak, failing success criterion 2.4.2
  • documents: some larger PDFs do not use bookmarks to aid navigation, failing success criterion 2.4.5
  • tables: heading elements are not declared and role=presentation is not used, failing success criterion 1.3.1
  • links: these do not change appearance when selected, failing success criterion 2.4.7
  • links: there are links throughout the site that point to anchors that do not exist, failing success criterion 2.4.1
  • links: some links use the same text for different destinations, failing success criterion 2.4.4
  • links: some links are not distinguished more than just colour, failing success criterion 1.4.1
  • links: some links cannot be read by screen readers, failing success criterion 4.1.2
  • frames and iframes: some do not have a title attribute, failing success criterion 2.4.1
  • frames: the frame title is the same as the frame ‘src’ file name, failing success criterion 2.4.1
  • document titles: some documents have no title failing success criterion 2.4.2
  • form field labels: some forms do not have labels or do not point to valid IDs, failing success criterion 1.3.1
  • forms: some form inputs do not identify the purpose of fields programmatically, failing success criterion 1.3.5
  • forms: some forms do not have a submit button, failing success criterion 3.2.2
  • outline / border style: the stylesheet makes it difficult to see the dotted link focus outline, failing success criterion 2.4.7
  • page language: this is not declared, failing success criterion 3.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
  • 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
  • colour contrast: some text does not have sufficient contrast, failing success criterion 1.4.3
  • mobile: some pages scroll in two dimensions on smaller screens, failing success criterion 1.4.10
  • lists: some navigation is not marked as lists, failing success criterion 1.3.1
  • code: there are duplicate IDs in the code, 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 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

We are aware of the issues on this website, and we are in the process of creating a remediation plan. We will update this statement with a date to work towards shortly.

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

  • Content that’s under someone else’s control that we have not paid for or developed ourselves.
  • Documents that we must make available and are submitted by the public or an external organisation
  • PDFs/documents (pre-September 2018): The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
  • Pre-recorded audio and video published before 23 September 2020.
  • Live audio and video.

Preparation of this accessibility statement

This statement was prepared on 30th September 2021.

This website was last tested on 30th September 2021. The test was carried out by Durham County Council.

We used Silktide to test a sample of pages.