Accessibility statement for the housing tenant portal

This website is run by 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:

use this website on most modern browsers and devices
navigate most of the website using only a keyboard
zoom in up to 200% without the text spilling off the screen

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:

navigating using a screen reader
navigating using a speech recognition software
drop down menus are not fully accessible
some parts of our website do not have sufficient colour contrast between the text and background colour
CAPTCHA Code
the order of our headings is not logical
focus styling is not prominent for some elements

Feedback and contact information

If you need information on this website in a different format email HousingEnquiries@leeds.gov.uk 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

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 HousingEnquiries@leeds.gov.uk.

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

Leeds City Council 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

Focus order

Dynamically loaded content inserted into the page does reset focus order. This fails WCAG criteria 2.4.3 Focus order.

Focus styling is not prominent enough

Focus styling used across the site is not prominent enough, in some cases the focusable element is barely visible at all. This fails WCAG criteria 2.4.7 Focus Visible.

General mark-up errors

General mark-up errors across the site that could cause problems for users of assistive technology. This fails WCAG criteria 4.1.1 Parsing.

Page transitions

Transition between pages are not announced to screen reader users so they won't know the status of a page load. This fails WCAG criteria 4.1.3 Status message.

Registration captcha

The registration captcha has no alternative so visually impaired users are unable to complete the form. This fails WCAG criteria 1.1.1 Non-text content.

Contrast

Page titles, hover states and component titles do not meet contrast ratio requirements and visually impaired users will be affected. This fails WCAG criteria 1.4.3 Contrast (Minimum).

Error identification

Invalid entries on the registration page or not programmatically linked to their input. This fails WCAG criteria 3.3.1 Error identification and 3.3.3 Error suggestion.

Aria attributes

Date of birth selector is not using valid aria attributes, this will cause problems for visually impaired users. This fails WCAG criteria 4.1.2 Name, Role, Value.

Hamburger menu does not meet contrast ratio requirements and will cause problems for users with visual impairments. This fails WCAG criteria 1.4.11 Non-text contrast.

<i> elements

The use of <i> element is depreciated and is not handled well by assistive technology. This fails WCAG criteria 1.4.4 Resize text.

Missing labels

'use graphical tool' checkbox has no associated label attached so users will not know it's purpose. This fails WCAG criteria 1.3.1 Info and Relationships.

Empty table headers

There are instances of table columns not having headers . This fails WCAG criteria 1.3.1 Info and Relationships.

Iframes

Frames do not have an accessible name. This fails WCAG criteria 4.1.2 Name, Role, Value.

What we're doing to improve accessibility

We are currently awaiting deployment of an updated build from the third-party supplier which is scheduled for February 2022 which will address these issues. A further audit will be completed at that time and statement to be addressed.

Disproportionate burden

Not applicable.

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