Accessibility statement for Modern Gov

This accessibility statement applies to content published on democracy.leeds.gov.uk. This website is run by Leeds City Council & Civica. We want as many people as possible to be able to use this website. For example, that means you should be able to:

We’ve also 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 accesible the website is

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

 

Feedback and contact information

If you need information on this website in a different format email Governance.And.Scrutiny@leeds.gov.uk and tell us:

 

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 Governance.And.Scrutiny@leeds.gov.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

Studio 12 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 listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Form inputs must have labels

There is a text area throughout the website that is visually hidden at the bottom of the page that has no label associated with it.

This fails WCAG 2.1 success criteria 1.3.1 Info and relationships and 4.1.2 Name, Role, Value.

<li> elements must be contained in a <ul> or <ol>

The breadcrumbs are not wrapped in a <ul> or <ol> element.

This fails WCAG 2.1 success criteria 1.3.1 Info and relationships.

Incorrect markup for data tables

Data tables (Date Picker) that contain both row and column headers use the scope attribute to identify cells.

This fails WCAG 2.1 success criteria 1.3.1 Info and relationships.

Pages have no descriptive title

Pages have the same title throughout the website so assistive technology users will not be easily able to determine if they’re on the correct page. This fails WCAG 2.1 success criteria 2.4.2 Page Titled.

Only one form of navigation

There needs to be multiple ways to find content on the site, currently there is only a menu bar.

This fails WCAG 2.1 success criteria 2.4.5 Multiple Ways.

Focus styling is not visible

The submit button, icon and list buttons do not have focus styling and can cause keyboard only users to be unaware of their current focus.

This fails WCAG 2.1 success criteria 2.4.7 Focus Visible.

Components are not responsive

Tables do not respond down for smaller devices and content is lost in reflow.

This fails WCAG 2.1 success criteria 1.4.10 Reflow.

Contrast ratio (minimum)

Calendar dates that are dimmed (not active), PDF file size text and committee links do not meet contrast ratio requirements of 4.5:1.

This fails WCAG 2.1 success criteria 1.4.3 Contrast (Minimum).

Link purpose

Date range links for earlier and later need don’t have descriptive titles so when read out of context by the user may not understand the purpose.

This fails WCAG 2.1 success criteria 2.4.4 Link purpose.

Images don’t have text alternative text

Icons used across the site don’t have alternative text so users may not be able to understand their purpose.

This fails WCAG 2.1 success criteria 1.1.1 Non-text content.

Broken images

The back button on the document library is broken.

This fails WCAG 2.1 success criteria 4.1.1 Parsing.

ARIA attributes must conform to valid values

The table wrapper has a labelled-by but there is no linked id in the DOM.

This fails WCAG 2.1 success criteria 4.1.2 Name, Role, Value.

Device orientation

When switching between portrait and landscape on mobile devices the content does not respond to changes in dimensions and the content overlaps.

This fails WCAG 2.1 success criteria 1.3.4 Orientation.

Resizing text and spacing

The councillor’s page does not respond well to changing font sizing and line heights as content overlaps and cannot be read correctly.

This fails WCAG 2.1 success criteria 1.4.4 resize text and 1.4.12 text spacing.

 

PDFs

There are a significant number of documents of varying size and complexity on this website not all of which will be accessible in line with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. A review will be undertaken and this statement updated in due course.

 

What we’re doing to improve accessibility

There are a significant number of documents of varying size and complexity on this website. Documents generally do not comply with accessibility requirements, so we will be reviewing how these are added to the site. We'll also be reviewing the technical non-compliant items listed above. We will update this statement by the end of April 2021 with a more detailed plan.

 

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 18/01/2021. It was last reviewed on 03/03/2021. This website was last tested on 17/12/2020. The test was carried out by 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: