Accessibility statement

1. Website accessibility

Using this website

East Sussex County Council run this website. We aim to make it as easy to use as possible. 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 only a keyboard
  • listen to our website using a screen reader.

Go to AbilityNet to find out how to make these changes.

All non-text content has a text alternative.

Language

We use plain English to make the text easy to read. We aim to create content for a reading age of 11. We regularly run readability audits on our content and make continual improvements. As of 22 September 2020, our content meets AA accessibility standards.

Sign language readers can visit our BSL introduction to the website.

If you would like to read the website in another language use Google Translate.

This statement was prepared on 18 September 2019. It was last updated on 22 September 2020.

2. How accessible is this website?

We know some parts of this website are not fully accessible:

  • some pages and document attachments are not clearly written
  • some tables do not have row headers
  • some heading elements are not consistent
  • some images do not have good alternative text
  • many documents are in PDF and Word format are not accessible
  • some pages use tables for layout without identifying them as such
  • some pages need improved hyperlinking
  • some form controls and buttons are not labelled

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

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.

Enforcement procedure

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).

4. Technical information about this website’s accessibility

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.

Images

Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This does not meet WCAG success criterion 1.4.5 (Images of Text).

We are working to remove all images that contain text. When we publish new content we’ll make sure our use of images meets accessibility standards.

Links

For some of our links that contain images, link text matches the image alt text. This does not comply with WCAG 2.0 A H2.

Iframes

Some of the iFrames on the forms do not have a title attribute. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass blocks) and WCAG 2.1 success criterion 4.1.2 (Name, Role, Value – Frames must have a title attribute).

We are migrating our website to the GOV.UK framework to address this issue.

Forms

One of our controls has a blank label or title, this does not comply with WCAG 2.0 A F68.

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).

We are migrating our website to the GOV.UK framework to address this issue.

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services, but may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role value).

We are working to either fix these or replace them with accessible HTML pages. Any new PDFs or Word documents we publish should meet accessibility standards.

Other web development issues

  • On some pages the italics-tag ‘i’ is used to highlight text. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (1.3.1 information and relationships). We are working to remove italics tags, (except where they are necessary for a legal term).
  • On some pages, the div and ul elements have been nested as children where they shouldn’t be. This does not comply with HTML5 WCAG 2.0 A 4.1.1. This will be addressed by the migration to the new website.
  • On one page a duplicate ID has been used on more than one element. This does not comply with HTML5 WCAG 2.0 A 4.1.1. This will be addressed by the migration to the new website.

Special sections of the site

Payment pages

Some of our forms use the same ID is used on more than one element. This means that users of assistive technologies will not be able to identify the unique purpose of the form field. This does not meet success criterion WCAG 2.1 A 4.1.1.

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

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.

Schools appeal pages

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.

Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

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.

Freedom of Information pages

The iframes which embeds the Freedom of Information form do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Rights of Way maps

Search results pages have the same title, making it difficult to distinguish pages. This does not comply with WCAG 2.1 A F25.

The code (WAI-ARIA) which is used by screen readers is incorrect or redundant. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role, value).

Support with Confidence

Some of our forms use the same ID on more than one element. This means that users of assistive technologies will not be able to identify the unique purpose of the form field. This does not meet success criterion WCAG 2.1 A 4.1.1.

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Search results pages have the same title, making it difficult to distinguish pages. This does not comply with WCAG 2.1 A F25.

Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.

These issues will be addressed in-house. See What we’re doing to improve accessibility.

Penalty Charge Notice (PCN) viewer

1.1.1 Non-Text Content
There are some personal data fields on the ‘Making a Representation’ screen that do not read out the name of the field whilst using a screen reader (NVDA).

1.2.1 Audio-only and Video-only (Pre-recorded)
1.2.2 Captions (Pre-recorded)
1.2.3 Audio Description or Media Alternative (Pre-recorded)
Images and videos are uploaded onto the portal, as part of evidence of a contravention. However, a user that relies on text-to-speech programs will not be able to watch the video. As well – a user that cannot hear audio (if any are present) will have difficulty. All videos, images, and audio must be made more accessible via text alternatives.

1.4.3 Contrast
Buttons, such as the ‘Pay PCN’ buttons, and the red warning text ‘No mapping data available.’ do not pass the contrast success criteria

2.4.1 Bypass Blocks
Website requires a ‘skip link’ for users that rely on keyboard to skip content such as headers and navigation links.

2.4.4 Link Purpose (In Context)
The final column that is to the right of ‘Street’ in the Pay PCN and Main Display Pages is blank. This is problematic as a user that relies on screen reader technology will not know what that column represents.

2.4.7 Focus Visible
the social media buttons in the website footer and the ‘Online Services’, ‘Contact Us’ and ‘News & Events’ buttons are not being highlighted to indicate their focus when navigating using only the keyboard.

Within the ‘Key Events’ page, there is a table which can’t be focused via tabbing, or strict keyboard use.

3.3.1 Error Identification
There is no error message displayed following the non-upload of file attachments when making a Representation, there is just a coloured border around the Additional Information button.

4.1.1 Parsing
Within the ‘Key Events’ and ‘View Map Location’ pages there is a hidden ID titled ‘SelectedPCNReference’ that is duplicated. This can potentially break accessibility, as screen readers may skip labels, tables etc due to duplicate IDs.

4.1.2 Name, Role, Value
Within the ‘Images’ page on the PayPCN screen, there are two violations. Two listboxes do not have an accessible name:
videoListView and listView.

We plan to rectify all identified issues by 31 March 2021. When we publish new content, we’ll make sure we continue to meet accessibility standards.

5. Third party sites known accessibility issues

We use many third party applications to deliver the functionality of this site. These are listed below.

Parents portal

HTML

  • There are some errors in the markup. This includes incorrectly nested and elements. This does not comply with WCAG 2.1 A 4.1.1.
  • 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.

Tables

  • Some presentation tables are not marked up as such. 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.

Links

  • The underlining has been removed from some links making it hard for colour-blind users to see them. This does not comply with WCAG 2.1 A F73.

Content

  • 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.

Site map

  • The website has no site map. This does not meet success criterion WCAG 2.1 AA 2.4.5.

Recruitment Hub

Forms

  • Some multi-part form fields are not named. This means that assistive technologies will not be able to discern the purpose of the control. This does not comply with WCAG 2.1 A F86.
  • Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.
  • Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.
  • Some of our forms have blank labels. This means that assistive technologies will not be able to discern the purpose of the control. This does not meet with success criterion WCAG 2.1 A 4.1.2.
  • Some of our input types are not properly identified. This means that assistive technologies will not be able to discern the purpose of the control. This does not meet with success criterion WCAG 2.1 1.3.5.

Content

  • 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.
  • 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.

Tables

  • Some presentation tables are not marked up as such. 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 tables are nested. This means that they will not be read in the correct order by assistive technologies. This does not comply with WCAG 2.1 A F49.
  • Some tables have not been structured correctly. This does not comply with WCAG 2.1 A 1.3.1.

iframes

  • Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Links

  • The underlining has been removed from some links making it hard for colour-blind users to see them. This does not comply with WCAG 2.1 A F73.
  • 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.

HTML

  • Some pages have errors with aria controls. This does not meet success criterion WCAG 2.1 A 1.3.1.
  • The lang 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.
  • The contrast of the navigation bar 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 users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. This does not comply with WCAG 2.1 A F54.

News and Health and Social Care News

iframes

  • Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Content

  • 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 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.

Images

  • Some images on the website are purely for decorative purposes and don’t have meaningful alternative text. This means that screen readers will not be able to discern the purpose of the image. This does not comply with WCAG 2.1 A F30.

Links

  • 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.

Tables

  • 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.

East Sussex public transport map

HTML

  • 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.
  • The lang 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.
  • 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 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.
  • Some content is positioned with CSS rather then by using standard markup.This means that content may be ordered in correctly for assistive technologies. This does not comply with WCAG 2.1 AA F1.

Financial assessment

  • Some pages have errors with aria controls. This does not meet success criterion WCAG 2.1 A 1.3.1.
  • On one page a duplicate ID has been used on more than one element. This does not comply with HTML5 WCAG 2.0 A 4.1.1. This will be addressed by the migration to the new website.

Provider portal

Tables

  • Some tables are nested. This means that they will not be read in the correct order by assistive technologies. This does not comply with WCAG 2.1 A F49.
  • 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.

HTML

  • Background and foreground colours have not been specified correctly in the CSS. This means that users will not be able to apply their preferred colour scheme. This does not comply with WCAG 2.1 AA F24.
  • The lang 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.

Content

  • 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.

Other

  • The website has no site map. This does not meet success criterion WCAG 2.1 AA 2.4.5.

Committees and meetings

HTML

  • Errors in setting 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 success criterion WCAG 2.1 A 1.3.2 and WCAG 2.1 A 3.1.1.
  • Several coding and nesting errors. This does not meet success criterion WCAG 2.1 A 4.1.1.

iframes

  • Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Content

  • 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.

Tables

  • Some tables are nested. This means that they will not be read in the correct order by assistive technologies. This does not comply with WCAG 2.1 A F49.
  • 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.

Forms

  • Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.

Open for Parents

Forms

  • Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

iFrames

  • Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Images

  • Some images on the website convey meaning, but do not have alternative text. This means that screen readers will not be able to discern the purpose of the image. This does not comply with WCAG 2.1 A F65.

Links

  • 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.
  • The underlining has been removed from some links making it hard for colour-blind users to see them. This does not comply with WCAG 2.1 A F73.

HTML

  • Some content is positioned with CSS rather then by using standard markup.This means that content may be ordered in correctly for assistive technologies. This does not comply with WCAG 2.1 AA F1.
  • 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.
  • 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.
  • Some pages have coding and nesting errors. This does not meet success criterion WCAG 2.1 A 4.1.1.

Content

  • 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.

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

PDFs and other documents

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 the cycling routes and maps leaflet.

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

7. How we tested this website

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 used automated testing software SortSite. For some sections we also used WAVE Web Accessibility Evaluation Tool.

We tested:

  • our main website
  • a range of microsites and third party websites

8. What we’re doing to improve accessibility

The team are currently working on an entirely new version of the website based on the Government Digital Services Design System. This framework has been developed by GOV.UK to provide a more accessible experience for our web visitors. Each component and pattern has been researched with a representative range of users, including those with disabilities. We plan to migrate the site section by section to the new template starting in October 2020. We expect this to fix most of the issues. Once the new website is launched, we will test it with a panel of impartial experts.

Other fixes are listed below.

In-house applications

We will redevelop in-house templates in order of priority determined by:

  • user volumes
  • work already planned in

This will address some known accessibility issues. Once completed, we will carry out a further accessibility audit. We will publish the report with priorities for redevelopment in due course. To support this work, we are committed to ongoing staff development and training.

Third party suppliers

We have raised issues with our third party suppliers and asked them to provide us with timetables for fixing errors. In some cases, for instance Meetings and Committees, the website is currently being redeveloped. We expect this to address most accessibility issues.

Non-HTML documents

We are training our staff in accessibility and how to create accessible documents. We are updating documents which are essential to providing our services to make sure they are fully accessible.