Accessibility statement for www.ebbsfleetdc.org.uk

Accessibility statement for Ebbsfleet Garden City

This accessibility statement applies to the website: www.ebbsfleetdc.org.uk

We are currently in the process of assessing the cost to fix the issues identified and identifying a timeline to implement these.

This website is run by the Ebbsfleet Development Corporation. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • 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)

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

How accessible this website is

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

  • Alternative text attributes for images are not always meaningful
  • Pre-recorded videos across the site lack text or audio descriptions
  • The cookie notice is the last element in the tabbing order, and users are required to tab through all sub-menu items
  • Skipped and empty heading levels are present, potentially causing issues for screen reader software
  • Some text has a low colour contrast against the site background
  • Video iframes are not appropriately titled
  • Some content is announced twice whilst using screen reader software
  • Some user interface components have a low colour contrast to the site background
  • Text overlaps on the ‘Contact us’ page when zooming in, or modifying the line height or spacing of text
  • Content is obscured when zooming in to 300% or above
  • Some PDFs created since September 2018 and most older PDFs are not accessible to screen reader software
  • Menu content that appears on hover or focus cannot be dismissed without moving hover or focus

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

  • email mark.templeton@ebbsfleetdc.org.uk
  • call 0303 444 2586

Address The Observatory, Castle Hill Drive, Castle Hill, Ebbsfleet Valley, DA10 1EE

We’ll consider your request and get back to you in 72 hours.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: mark.templeton@ebbsfleetdc.org.uk

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

Ebbsfleet Garden City is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Accessible names are not provided or incorrectly given to non-text content such as decorative images, linked images, and informative images. People using a screen reader cannot access the information. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-Text Content.

We plan to resolve this by: 01/12/21

Alternatives for non-text content is not correctly provided for PDF documents. Images and figures within lack an alternative text value, and other non-text content is not tagged. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-text Content

We plan to resolve this by: 01/12/21

Text or audio descriptions are not present for pre-recorded video without a soundtrack. People who are not able to see the visuals of the videos will not be able to access the information conveyed within them. This is a failure of WCAG 2.1 success criterion 1.2.1 Audio-only and Video-only (Pre-Recorded).

We plan to resolve this by: 01/12/21

Some pages contain empty headings. People navigating with a screen reader may miss content if navigating via headings. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: 01/12/21

Contrast issues are present for some text copy on the site. People with low vision may have difficulty reading text. This is a failure of WCAG 2.1 success criterion 1.4.3 Contrast (Minimum).

We plan to resolve this by: 01/12/21

Text overlaps on the ‘Contact us’ page when zooming text only to 200%. This is a failure of WCAG 2.1 success criterion 1.4.4 Resize Text.

We plan to resolve this by: 01/12/21

Some pages contain images of text. People with low vision may have trouble reading the text with the authored font family, size and/or colour. This is a failure of WCAG 2.1 success criterion 1.4.5 Images of Text.

We plan to resolve this by: 01/12/21

Some content is obscured when viewing the site at 400% zoom. This is a failure of WCAG 2.1 success criterion 1.4.10 Reflow.

We plan to resolve this by: 01/12/21

When applying custom text styling, text overlaps on the ‘Contact us’ page. People who require increased space between lines, words, and letters may be unable to read text within this page. This is a failure of WCAG 2.1 success criterion 1.4.12 Text Spacing.

We plan to resolve this by: 01/12/21

No functionality is present within the website that allows users to dismiss hover content. This is a failure of WCAG 2.1 success criterion 1.4.13 Content on Hover or Focus.

We plan to resolve this by: 01/12/21

Embedded content is not labelled in a way that assistive technologies are informed of its purpose. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.

We plan to resolve this by: 01/12/21

The heading structure on some pages is incorrect due to skipped heading levels. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.

We plan to resolve this by: 01/12/21

Some page titles have a duplicated page title. People may be unable to differentiate content when multiple web pages are open. This is a failure of WCAG 2.1 success criterion 2.4.2 Page Titled.

We plan to resolve this by: 01/12/21

PDF documents have a blank title. This is a failure of WCAG 2.1 success criterion 2.4.2 Page Titled.

We plan to resolve this by: 01/12/21

The tabbing order is illogical, with the cookie notice being the last element in the focus order, and users are required to tab through all sub-menu items. This is a failure of WCAG 2.1 success criterion 2.4.3 Focus Order.

We plan to resolve this by: 01/12/21

Several instances of identical link text and empty links are present. People with visual disabilities will be unable to determine the purpose or context of the link. This is a failure of WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).

We plan to resolve this by: 01/12/21

Duplicate form labels are present on several pages. People using a screen reader may be unable to determine the context of the different form fields. This is a failure of WCAG 2.1 success criterion 2.4.6 Headings and Labels.

We plan to resolve this by: 01/12/21

A visible focus indicator is not always present when navigating the site using a keyboard. People who rely on the keyboard to operate the page may not be able to visually determine the component on which keyboard operations will interact. This is a failure of WCAG 2.1 success criterion 2.4.7 Focus Visible.

We plan to resolve this by: 01/12/21

The visual label does not match the accessible name for links on the ‘Latest Schools News’ page. This is a failure of WCAG 2.1 success criterion 2.5.3 Label in Name.

We plan to resolve this by: 01/12/21

The language of PDF documents has not been defined; this may influence the way screen reader software announces text. This is a failure of WCAG 2.1 success criterion 3.1.1 Language of Page.

We plan to resolve this by: 01/12/21

HTML validation errors are present which may influence how assistive technology software handles content on the site. This is a failure of WCAG 2.1 success criterion 4.1.1 Parsing.

We plan to resolve this by: 01/12/21

Excessive white space is present on several pages. People who use zoom tools may become disorientated when navigating the site. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role Value

We plan to resolve this by: 01/12/21

When navigating the site using a screen reader, some controls are announced twice causing the screen reader to stutter. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role Value.

We plan to resolve this by: 01/12/21

Some PDF documents do not include the PDF/UA identifier within the metadata stream in the Catalog dictionary. Users of assistive technology may be unable to access the information needed within the document, such as the document title. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role Value.

We plan to resolve this by: 01/12/21

Disproportionate burden

We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in 01/01/2024.

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

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. We are in the process of improving the accessibility of these or replacing these with HTML where possible.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

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

Video Content

Pre-recorded video present on the site lacks a text or audio description. This is a failure of WCAG 2.1 success criterion 1.2.1 Audio-only and Video-only (Pre-Recorded); however, this is exempt as it has been created prior to September 2020. All future video will be clearly marked-up with a media alternative or will have captions provided.

Preparation of this accessibility statement

This statement was prepared on 11/05/2021. It was last reviewed on 11/05/2021.

This website was last tested on 09/05/2020. The test was carried out by Zoonou.

We used this approach to deciding on a sample of pages to test WCAG-EM.