Accessibility

Accessibility statement for Essex County Council

This accessibility statement applies to the Essex County Council website. It also includes web tools needed to complete tasks and user journeys located at:

essex.gov.uk
buslanepayments.essex.gov.uk
essex-self.achieveservice.com
essexcountycouncilcovid19forms.evolutive.co.uk
essex.sishost.co.uk

This website is run by Essex County Council. 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
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using 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).

We’ve made the website text as simple as possible to understand.

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 accessible:

Perceivable

Some images and icons have missing or incorrect alternative text.

Some headings do not look like headings and some text that look like headings are not.

Some pages have multiple heading 1 tags and some heading levels are skipped.

Some links and buttons are used incorrectly.

Lists are not always used correctly, in the contents each item is a list, and some menus are a combination of two lists, some lists have incorrect aria roles, and, on some forms, an unordered list is used when it should be ordered.

On the bus lane payments website there are no page landmarks making it difficult to navigate for assistive technology users.

Tables are used to format content on the bus lane payments website making it difficult for some users to understand the purpose of the content.

On some form inputs there are no autocomplete values making it difficult for some users to fill in the forms.

Some text has low contrast and is difficult to read.

When increasing font-size to 200% some text is difficult to read or obscured.

When zooming in, some text and content Is obscured or difficult to read. This occurs on:

  • the school admissions application form
  • bus lane payments

Inputs have low contrast making them difficult to see when paying bus lane fines.

Adding text spacing can cause content to be obscured on the bus lane payments page.

Operable

Some elements cannot be controlled with a keyboard including the cookie banner.

On some of our forms there is no option to adjust timings.

The bus lane payments page has no option to skip to page content.

On the bus lane payments page the page titles are not clear of the page content.

On some of our forms the page titles are not clear of the page content.

The focus order on some of our forms and our feedback mechanism is not always logical.

Some headings or labels do not clearly describe the purpose of the page or section.

Some items on our form and feedback mechanism and bus payments page have focus styles that cannot be or are impossible to see.

Understandable

On some forms choosing an address or selecting an appointment time creates a change of context.

Navigation on the bus lane payments website is not always consistent.

Some links that are identified differently go to the same destination.

When entering details on the bus lane payments website some inputs do not have clear error identification.

Some inputs do not provide clear suggestions for overcoming errors.

Robust

In many places the correct markup is not used correctly. This may have an effect on users who require the use of assistive technology or want to change the website layout or style to improve their experience. This occurs on:

  • School applications form

On some pages the correct name role or value is not assigned, this could affect users of assistive technologies or require said technologies to provide information about states, properties, and values etc. This occurs on the:

  • school applications form

How to contact our Accessibility team

Contact our accessibility team to request a different format. This could be an accessible PDF, large print, easy read, audio recording or braille.

Email: Accessibility@essex.gov.uk

We’ll consider your request and get back to you within 20 working days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. Contact the accessibility team if you find any problems not listed on this page.

Email: Accessibility@essex.gov.uk

We'll consider your request and get back to you within 20 working days.

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

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops. If you contact us before your visit, we can arrange a British Sign Language (BSL) interpreter.

Technical information about this website’s accessibility

Essex County Council commits to making its website accessible. This is under 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. This is due to the non-compliances listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Essex County Council website

Perceivable

Some images have incorrect or missing alternative text. This makes it difficult for users of assistive technologies to understand the purpose of the image. This fails WCAG 2.1 success criterion 1.1.1 (Non-text content). We plan to ensure all images have the correct alternative text. At this current time we have no fixed resolution date.

Some links, lists and headings are not in a correct format. This fails WCAG 2.1 success criterion 1.3.1 (Info & Relationships). We plan to ensure all elements are correct At this current time we have no fixed resolution date.

Operable

You cannot dismiss the cookie banner with the keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).

Granicus Forms

Perceivable

We build and host our forms using a third-party product. We are upgrading all our forms to the latest version of this product.

The vendor states that ‘citizen facing products are being updated to ensure they meet all required elements of the accessibility directive that require implementation in the EN 301 549 mandate.’

The use of links, lists and roles is not correct. This fails WCAG 2.1 success criterion 1.3.1 (Info & Relationships).

Some forms do not include autocomplete values. This fails WCAG 2.1 success criterion 1.3.5 (Identify input purpose).

When increasing font-size to 200% some options become unavailable or difficult to interact with. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).

When zooming in to up to 400% some content and functionality becomes obscured. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).

Operable

Some form functions such as date pickers and collapsible rows does not work with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).

Some forms have a timeout with no option to extend the form duration and some form messages disappear before the user has time to read them. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable).

When using a keyboard to complete the form the focus order is not always logical. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).

When using a keyboard focus styles are not always visible. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).

Understandable

When selecting an address, there is a change of focus without warning. This fails WCAG 2.1 success criterion 3.2.2 (On Input).

Robust

The forms include invalid HTML and HTML attributes as well as incorrectly implemented CSS. This fails WCAG 2.1 success criterion 4.1.1 (Parsing).

Some form inputs do not have connected labels. Some form elements are in tables. This makes it difficult for users of assistive technologies to interact with. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Some role attributes are not correct. Some form values contain prior information given to the user. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Stopford bookings

Perceivable

There are no autocomplete attributes set in the form. This makes it difficult for some users to complete the form. This fail WCAG 2.1 success criterion 1.3.5 (Identify input purpose).

Bus lane payments

Perceivable

Some images have no or inadequate alt text. This fails WCAG 2.1 success criterion 1.1.1 (Non-text contrast).

There are multiple level 1 headings, and some heading levels are skipped, there are no page landmarks or regions and lists and tables are used incorrectly. This fails WCAG 2.1 success criterion 1.3.1(Info and Relationships).

Some form fields do not have autocomplete attributes making it difficult for some users to complete the form. This fails WCAG 2.1 success criterion 1.3.5(Identify input purpose).

Some heading text falls below a 4.5:1 contrast ratio. This fails WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)).

Some font is obscured or overlapped on the menu and navigation when font-size is increased making it difficult to read. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).

When zooming in, the page does not reflow making it impossible to view some of the page content. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).

Inputs have low contrast below the required 3:1 contrast ratio making it difficult to see. This fails WCAG 2.1 success criterion 1.4.11 (Non-text Contrast).

When increasing text-spacing some text in the menu becomes obscured. This fails WCAG 2.1 success criterion 1.4.12 (Text Spacing).

Operable

DixerIT accessibility features cannot be operated with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).

There is no way to adjust any timings used on forms. This fails WCAG 2.1 success criterion 2.2.1(Timing Adjustable).

There is no option to bypass blocks such as the menu or navigation making it difficult for keyboard only users to access content. This fails WCAG 2.1 success criterion 2.4.1 (Bypass blocks).

The homepage title is not descriptive of the purpose of the page. This could be confusing for some users who rely on a screen reader. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).

The focus order when filling out the appeals form is illogical and does not move to the start of the next form section when it is loaded. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).

Headings and labels do not clearly describe the topic or purpose of the content. Making it difficult for some user to identify or find the right content they require. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).

There are no focus styles on many of the interactive elements. This makes it difficult for Keyboard only users to navigate through the website. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).

Understandable

When making an appeal the navigation changes making it potentially confusing for some users. This fails WCAG 2.1 success criterion 3.2.3 (Consistent Navigation).

Some links that got to the same destination are labelled differently making it difficult for some users to identify where to navigate. This fails WCAG 2.1 success criterion 3.2.4 (Consistent Identification).

When submitting a form some inputs are not identified clearly. This fails WCAG 2.1 success criterion 3.3.1(Error identification).

When entering information in to inputs not all required inputs provide clear error suggestions. This fails WCAG 2.1 success criterion 3.3.3 (Error Suggestion).

Content not within the scope of the accessibility regulations

PDFs and other documents

Some of Essex County Council’s older PDFs do not meet accessibility standards.

We're working towards making as many PDFs as possible meet WCAG 2.1 AA Accessibility standards.

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

We are prioritizing PDFs as they often:

  • contain information on how users can access our service
  • are most frequently downloaded
  • have information that has a statutory requirement.

We have developed training and guidance for document creators to make accessible documents.

Our plan is to ensure that all essential PDFs meet accessibility regulations by 1st December 2022.

Live Video

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

What we are doing to improve accessibility

We are currently working with internal teams and external suppliers to improve accessibility on Essex.GOV.UK and it’s connected services.

We will continue to monitor accessibility using automated and manual checks.

Preparation of this accessibility statement

This statement was prepared on 26 June 2019. It was last reviewed on 09 February 2022.

This website was last tested on 16 June 2021. The test was carried out by the Central Data and Digital Office.

The website was tested using Windows 10 Pro, Google Chrome and Firefox, NVDA and Axe testing software on a range of pages and user journeys. This included:

  • Home
  • Accessibility Statement
  • Contact us
  • Coronavirus
  • Current dates and locations for mobile testing units
  • Admissions
  • Secondary school places
  • Admissions booklet, policies and forms
  • School terms and holidays
  • News
  • Search
  • Admissions common application form
  • Register a birth page and form
  • Covid-19 Business support form
  • HotJar feedback

Updated 09 February 2022

Print this page