Accessibility statement

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.

Print entire guide