Accessibility statement for Levy Match Leeds

This accessibility statement applies to content published on https://www.levymatchleeds.co.uk/ domain.

This website is run by Employment and Skills Leeds, Leeds City 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 and contrast levels using browser extensions
  • Zoom in up to 200% using your browsers built in zoom functionality without text spilling off the screen
  • Navigate most of the website using a screen reader although we have identified some areas which can be difficult to use
  • Use this website on most modern browsers and devices except Internet Explorer 11
  • Navigate most of the website using only a keyboard
  • Navigate most of the website using speech recognition software

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:

  • Some content does not display correctly in older browsers such as Microsoft Internet Explorer.
  • It is not possible for keyboard only or screen reader users to skip past repeated content such as the header and navigation. This is normally done using a ‘skip to content’ link
  • The navigation is not accessible for keyboard only users on smaller screen sizes
  • When screen reader users incorrectly fill out forms error messages or pop ups appear but aren’t announced to the screen reader
  • The focus styling of interactive elements isn’t always obvious

Dates for improvements

We aim to fix our accessibility issues by 27th November 2021.

Feedback and contact information

If you need information on this website in a different format email [email protected] and tell us:

  • the web address (URL) of the content
  • your name and email address
  • the format you need, for example, audio CD, braille, BSL or large print, accessible PDF

Reporting accessibility problems with this website

If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, email [email protected].

Enforcement procedure

If you contact us with a complaint and you’re not happy with our response contact the Equality Advisory and Support Service (EASS).

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

Technical information about this website's accessibility

Employment and Skills Leeds 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below.

Non-accessible content

Non-compliance with the accessibility regulations

Leeds City Council logo in the footer

The Leeds City Council logo in the footer is contained inside a link but has no accessible text to describe the purpose of the link to screen reader users.

This issue fails WCAG 2.11.1.1 Non-text content (A) and 2.4.4 Link purpose in context (A).

Headings

Some headings on our website have been made to look like normal paragraph text, using CSS to control the styling. This can be confusing for screen reader users as headings are used to understand the hierarchy of content on the page.

This fails WCAG 2.1 1.3.1 Info and Relationships (A) and 2.4.6 Headings and Labels (AA).

Link text

We have a couple of links on our website which do not make sense when taken out of context. This can make it difficult for screen reader users to navigate the page using links.

This fails WCAG 2.1 2.4.4 Link purpose (in context) (A).

Colour contrast issues

Some areas of our website have insufficient colour contrast. This can make text hard to read for users who may be colour blind. Some areas affected are:

  • the footer links when focused on by keyboard only users who have zoomed in
  • form field border colours against the surrounding background colour
  • Default text when user has no calls when signed in as SME
  • Error messages that appear if you incorrectly fill in create new call form

These issues fails WCAG 2.1 1.4.3 Contrast (Minimum) (A) and/or 1.4.1 Use of color (A).

Form field colour

When logged in as SME and creating a new call there is a form that background colour is dusty pink and form fields are white. There is insufficient colour contrast between these two colours. This fails 1.4.11 Non-text contrast (AA).

Focus styling

Some interactive elements on our website do not receive any different visual styling (focus styling) when using a keyboard to navigate down the page meaning users may not be aware which element they are interacting with.

This fails WCAG 2.1 2.4.7 Focus visible (AA).

Resize text

When using a browser extension to increase the font size to 200% some content disappears off the page as it has not moved down to adjust itself. This is apparent in the header and footer.

This fails WCAG 2.1 1.4.4 Resize text (AA).

You are able to resize the whole page content using your browsers built in zoom functionality to 200% and all the content is visible and readable.

Navigation

Keyboard accessibility

It is not possible to open and close the burger navigation (for users who are zoomed in on desktop) using only a keyboard.

This fails WCAG 2.1 2.1.1 Keyboard (A).

Screen reader accessibility

The burger icon does not announce to screen reader users whether it is collapsed or expanded when changing between the two states.

This fails WCAG 2.1 4.1.2 Name, Role, Value (A).

Skip repeated content

It is not possible to skip repeated content on the page as a keyboard or screen reader user. This is normally possible by including a ‘Skip to content’ link as the first interactive element a user can interact with.

This fails WCAG 2.1 2.4.1 Bypass Blocks (A).

Website validation

Our website’s HTML mark-up does not validate when running it through W3C validator. There are numerous errors that need looking into.

This fails WCAG 2.1 4.1.1 Parsing (A).

Form issues

Autocomplete

Where forms collect information about the user (such as sign up forms) we should have auto complete on the form fields so people with language or memory problems can benefit from the browsers auto filling their information in. Some fields don’t currently have auto complete on them.

This fails WCAG 2.1 1.3.5 Identify Input Purpose (AA).

Error messaging

If a user incorrectly fills out a form error messages and an error summary appear but screen reader users aren’t alerted to the errors on the page.

This fails WCAG 2.1 3.3.1 Error identification (A) and 4.1.3 Status message (AA).

Required form fields

The website has asterisks against required form fields but there isn’t information about this before filling in forms. This fails WCAG 2.1 3.3.2 Labels or Instructions (A).

Some form fields have asterisks in their label but haven’t got the appropriate HTML mark-up against the input field that tells screen reader users they are required. This fails WCAG 2.1 3.3.3 Error Suggestion (AA).

Form fields flowing off the page

The form fields on Sign up as SME page flow off the page if a user zooms to 400% using their browsers built in zoom functionality.

This fails WCAG 2.1 1.4.10 Reflow (AA).

Page title

The browser tab page title is the same on Sign up for SME and Sign up as Levy Payer pages. Page titles should be unique so users can quickly navigate between tabs and so screen reader users can quickly identify which page they have navigated to.

This fails WCAG 2.1 2.4.2 Page titled (A).

Multiple ways of finding content

When signed in as SME it is only possible to find some pages using links on the homepage. Users should be offered two methods of finding content.

This fails WCAG 2.1 2.4.5 Multiple Ways (AA).

Create a call pop ups

After submitting the Create new call form a pop up appears. The pop up is not announced to screen reader users and it is not possible to close or interact with the form using only a keyboard. This fails WCAG 2.1 2.1.1 Keyboard (A) and 2.1.2 No Keyboard Trap (A).

Disproportionate burden

Not applicable.

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

Not applicable.

Preparation of this accessibility statement

This statement was prepared on 06/11/2020. It was last reviewed on 27/11/2020.

This website was last tested on the 06/11/2020. The test was carried out by the Web Design Team at Leeds City Council.

We tested a selection of pages, ensuring those tested reflected the variety of different page layouts used on our website.

The pages we tested were:

  • Homepage
  • About
  • Sign up as SME
  • Dashboard
  • Create new call