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.
This website launched in November / 2018.
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 visit our contact 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 City Incubator 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.
- Links: ensure links can be used by screen readers failing criterion 4.1.2
- Images: specify alt tags and combine adjacent links with the same destination failing criterion 1.1.1
- Video: ensure captions are provided for all pre-recorded audio and video failing criterion 1.2.2
- Captions: enure captions are provided for all pre-recorded audio and video failing criterion 1.2.2
- Links: ensure links are distinguished by more than just colour failing criterion 1.4.1
- Links: avoid using the same link text for different destinations failing criterion 2.4.4
- Navigation: mark navigation as lists failing criterion 1.3.1
- Headings: ensure headings include text failing criterion 1.3.1
- Tables: Add a scope to table headings failing criterion 1.3.1
- Language: specify the language of every page failing criterion 3.1.1
- Fields: identify the purpose of fields programmatically failing criterion 1.3.5
Accessibility Roadmap
As stated in the non-compliance section, the known issues are listed below:
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 November 2022.
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.