This accessibility statement applies to the MyHomeLLR app.
This app is run by HomeConnections Ltd on behalf of Leicester City Council. We want as many people as possible to be able to use our app. For example, that means you should be able to:
AbilityNet has advice on making your device easier to use if you have a disability.
We are aware of some issues that may affect the accessibility of some parts of the app:
If you need information on this app in a different format like accessible PDF, large print, easy read, audio recording or braille you can email MyHomeLLR@leicester.gov.uk. We’ll consider your request and get back to you in 10 days.
We’re always looking to improve the accessibility of this app. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us at MyHomeLLR@leicester.gov.uk.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Apps 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).
Both Home Connections Ltd and Leicester City Council are committed to making its app accessible, in accordance with the Public Sector Bodies (Apps and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This app is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to ‘the non-compliances and exemptions’ listed below.
The content listed below is non-accessible for the following reasons.
Colour is used as the only means of distinguishing some text links within the app. This may be imperceivable to some users and fails WCAG success criterion 1.4.1 (Use of Colour).
We plan to add an underline to all text links to ensure they do not rely on colour by October 2023.
Colour contrast of text is insufficient in places making it hard from some people to read content on our app. This fails WCAG success criterion 1.4.3 (Contrast (Minimum)).
We plan to change all colours that do not pass contrast requirements by October 2023. Any new colours will be tested for compliance before being used on the app.
The purpose of links is not always clear from the text alone. This can make it difficult for screen reader users to distinguish between the different links and fails WCAG success criterion 2.4.4 (Link Purpose (In Context)).
We plan to change all links so they are meaningful without the context of the surrounding text by October 2023
On some versions of Android, a back button is a missing programmatic label so is not announced in a meaningful way by the screen reader. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to add programmatic labels to all buttons by October 2023 Any new buttons will be added with programmatic labels as standard.
On some versions of Android, form fields are not always clear to use with a screen reader due to how they are labelled and how clearly their role is described. This can make it difficult for blind users to understand what information they are required to input or how the interact with the form element. This fails WCAG success criteria 1.3.1 (Info & Relationships) and 4.1.2 (Name, Role, Value).
We plan to add programmatic labels and define clear roles for our form fields by October 2023
The focus order through dropdown form fields does not always preserve meaning. This fails WCAG success criterion 2.4.3 (Focus Order).
We plan to resolve this issue by October 2023
The error messaging on some form questions is generic in places and does not describe how to correct the error. This fails WCAG success criterion 3.3.3 (Error suggestion) We plan to change our error messaging, so it accurately describes the issue and how to fix it by October 2023
This statement was prepared on 30/05/2023 It was last reviewed on 13/06/2023
The app was last tested on 24th March 2023. This app was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and the test was carried out by Web Usability Partnership Ltd.
We used the Web Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of screens to test.