Accessibility statement

This statement applies to content published on the domain.

We want as many people as possible to be able to use and understand our website. Our accessibility commitment includes making sure that our website visitors can:

  • easily understand our web pages by making the content as simple as possible
  • zoom in up to 300% on a webpage 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).

How accessible this website is

We’re aware that some parts of this website may not be fully accessible yet.  For example:

  • Some critical ARIA roles may be missing or incorrect
  • Colour contrast may not be strong enough in some places
  • Some images may lack alternative text

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

If you need information on this website in a different format, email

Please include in your email the web address of the content (specific URL) and the format you need. For example:

  • accessible PDF
  • large print
  • easy read version
  • audio
  • braille.

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

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, email

Technical information about this website’s accessibility

The EIDC is committed to making its website accessible.  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 images and <object> elements don’t have a text alternative, so the information isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images and <object> elements by December 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.

Some pages lack required ARIA attributes. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role, value).  We plan to review all ARIA labels on the website and repair/add them as needed. We will complete this work by January 2022.

Some important text elements have insufficient contrast with their background. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (contrast).  We plan to ensure contrast meets required standards by March 2022.

Disproportionate burden

In some cases content is embedded from third party sources such as Twitter and mapping services. We cannot control these elements as they are provided “as is” by the external service, so in such cases - where we cannot source an alternative, more accessible service - we are obliged to accept the mark-up provided.

Some of our PDFs and Microsoft Office documents may not meet accessibility standards. For example, they may not be marked up so they are accessible to a screen reader. These include historic documents.

What we’re doing to improve accessibility

We asked Code Enigma to test the accessibility of the site for compliance with Web Content Accessibility Guidelines version 2.1 as part of an external auditing programme.

They used a sample of pages. These pages were selected by EIDC based on their importance and utilisation. We also included pages from our data catalogue that are as complete as possible, to ensure we capture all key page elements.

We commit to implement all the necessary changes by December 2022.

Preparation of this accessibility statement

This website was tested on 15th July 2021.

This statement was prepared on 21st September 2021. It was last updated on 21st September 2021.