East Sussex County Council run this website. We aim to make it as easy to use as possible. You should be able to:
Go to AbilityNet to find out how to make these changes.
We know some parts of this website are not fully accessible:
We are always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we are not meeting the requirements of the accessibility regulations please contact us.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
This statement was prepared on 23 September 2020. It was last updated on 23 September 2020.
As part of our commitment to accessibility we are required to publish where we know there are issues with our website.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following issues.
Some pages have errors with aria controls. This does not meet success criterion WCAG 2.1 A 1.3.1.
Some pages use CSS to markup bold text instead of using semantic markup. This means that changes in text to convey meaning will not be picked up by assistive technology. This does not comply with WCAG 2.1 A F2.
Some content on our website is automatically inserted using CSS. This means it cannot be read out by a screen reader or will not be available to users who turn stylesheets off. This does not comply with WCAG 2.1 A F87.
The contrast of some of the colours is not high enough. This means that some users will have difficulty reading the content. This does not meet with success criterion WCAG 2.1 AA 1.4.3.
Some tables are not marked up correctly. This means that assistive technologies will read the content of these tables out of context. This does not comply with WCAG 2.1 A F91.
Some of our forms have duplicate field labels, making it difficult to identify their purpose. This does not meet WCAG 2.1 AA success criterion 2.4.6 (Headings and Labels).
On some of our pages, headings have been left blank. This means that their purpose cannot be understood by assistive technology. This does not meet with success criterion WCAG 2.1 AA G130.
The language attribute is not used to identify the language of the page. This means that assistive technologies will not be able to discern the default language to convert text into synthetic speech. This does not meet with success criterion WCAG 2.1 A 3.1.1.
Some pages on this website have the same title. This means that web visitors may not be able to identify whether the information contained in the Web page is relevant to their needs. This does not comply with WCAG 2.1 A F25.
On some pages the links do not contain any text or an image with alt text. This means that assistive technologies cannot identify the purpose of the links. This does not comply with WCAG 2.1 A F89.
Some pages have disabled zoom on the ‘viewport’. This means that users cannot control the size of parts of the page. This does not meet with success criterion WCAG 2.1 AA 1.4.4.
The focus outline styling has been switched off through CSS. This means that users cannot see where they are on the page when they tab through links. This does not comply with WCAG 2.1 AA F78.
Many of our 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. For example, we don’t plan to fix [example of non-essential document].
Any new PDFs or Word documents we publish will meet accessibility standards.
This site was most recently tested in September 2020. This website was and is currently being tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and these tests have been carried out internally.
We are currently working with our developers to address the accessibility issues noted in this statement. We will update this section when we have a clear roadmap for the fixes.