Accessibility statement for Homes for Londoners

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

• Some overlays do not have focus to be trapped within them and are not using dialogs in the markup.
• The titles for some pages (Create an account step 1 and 2) do not properly convey the purpose of the page.
• There are duplicate links (Featured properties component and Home page) where one link does not identify the link target.
• The search result pagination links do not have additional context to be meaningful.
• On property pages, there may be links to download a floor plan and/or Energy certificate. This is shown with an icon, but no text alternative is provided for screen reader users.
• On some pages, there are some visible labels that do not match the programmatic names.
• On some pages, there are fields that allows character input, but resets due to error detection. The user is not notified of this.
• On the send enquiry to seller page, there are error messages that are provided in text but, not programmatically associated with the input elements.
• The required fields in various forms (Send enquiry to seller, Create an account step 1 of 2, Sign in) do not use the required attribute.
• The date of birth fields need labelling for day, month and year.
• Instructions to notify users that fields are required are missing on the send enquiry to seller page.
• Placeholder text is used for labelling text boxes.
• Some input fields that collect an individual’s personal data on some pages (Send enquiry to seller, Create an account step 1 of 2, Sign-in) do not have the necessary “autocomplete” attributes.
• Some of the navigation links are not displayed when resizing text to 200%.
• With the browser window width set to 1280px and magnification at 400%, not all of the links in the main navigation are visible. There are some components that has content that is no longer displayed or the main content area is restricted to a third of the user's visible area of a webpage on a screen.
• Some forms have error messages that are only displayed for 5 seconds.

Issues affecting people who use keyboard navigation

• The filter sort control, add to favourite control, property image carousels, save property and copy link controls, expand and collapse control, info overlays, maps, checkboxes, radio buttons and radio button fields and map pins (Local area information map), close buttons within modals on some pages cannot be operated using the keyboard.
• On some pages when information modals are opened focus is not constrained to the modal. Focus should move to the first focusable element inside the modal.
• There are some tile controls on the home page that contain 2 tab stops.
• The CAPTCHA links in the create an account step 1 of 2 page are not in the correct focus order.

Issues affecting screen reader users

• Carousel images for properties share the same text alternatives and are not sufficiently descriptive.
• Some components have content that is exposed to the screen reader when it is not displayed on the screen.
• Some pages include characters used as graphics that do not have appropriate text alternatives.
• Some images in the search result page do not have alt text and some have text alternatives that are not descriptive.
• Some headings are not marked-up correctly so screen reader users cannot identify the structure of the pages.
• The property image carousel and the breadcrumb links are not marked-up correctly. The container for the carousel and the container for the breadcrumb links do not have a label to convey their purpose.
• Within the search results pagination links, the current page is not identified for screen reader software users. The numbered list (Affordability calculator page) is not marked-up correctly.
• Some accordion controls, dropdown lists, zoom controls, radio buttons, checkboxes, filter buttons, sort controls, links, unordered lists, controls and form fields, controls in the property image carousel, next and previous controls in the search results page, are not marked-up correctly and are not conveyed correctly to assistive technologies.
• Status messages are not announced to screen reader software users.

Issues affecting people with low vision

• Various colour contrast issues with the foreground and background colours of the page.
• Focus is not visible on some controls (Search and filter, FAQs).

If you need information on this website in a different format (accessible PDF, large print, easy read, audio recording or braille) or would like to report an accessibility problem with the website, please:

• call 020 7983 4000 (Monday to Friday, 9am - 5pm)
• get in touch via our online form
• or email [email protected]

We’ll consider your request and get back to you within five working days, to advise further.

If you cannot view the map on our contact us page, please call or email us for directions.

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

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

Find out how to contact City Hall.

The Greater London Authority (GLA) is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

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

Non-compliance with the accessibility regulations

• Images for properties in carousel components and in search results share the same alt text and are not sufficiently descriptive. (WCAG 2.2 A criterion 1.1.1 - Non-text content).
• some pages include text characters used as graphics that do not have appropriate text alternatives. (WCAG 2.2 A criterion 1.1.1 - Non-text content).
• Some headings are not marked-up correctly to identify the structure of the content.(WCAG 2.2 A criterion 1.3.1 - Info and relationships).
• The purpose of the containers for the property image carousel and the breadcrumb links are not programmatically conveyed. (WCAG 2.2 A criterion 1.3.1 - Info and relationships).
• On the pagination component, the current page is not programmatically conveyed. (WCAG 2.2 A criterion 1.3.1 - Info and relationships). The numbered list (Affordability calculator page) is not marked-up correctly. (WCAG 2.2 A criterion 1.3.1 - Info and relationships).
• Some components within various pages have content that is exposed to the screen reader when it is not displayed or in a collapsed state. (WCAG 2.2 A criterion 1.3.2 - Meaningful sequence).
• The filter sort control, add to favourite control, property image carousels, save property and copy link controls, info overlays, maps, checkboxes, radio buttons and radio button fields and map pins (Local area information map) on some pages cannot be operated using the keyboard. (WCAG 2.2 A criterion 2.1.1 - Keyboard Navigation).
• On some pages when information modals are opened focus is not constrained to the modal. (WCAG 2.2 A criterion 2.1.1 - Keyboard Navigation).
• There are some tile controls on the home page that contain 2 tab stops. (WCAG 2.2 A criterion 2.1.1 - Keyboard Navigation).
• The CAPTCHA links in the create an account step 1 of 2 page are not in the correct focus order. (WCAG 2.2 A criterion 2.4.3 - Focus order).
• The form in the "Create an account step 2 of 2 page and the Affordability calculator page) uses native HTML5 data validation that has error messages that are only displayed for 5 seconds. (WCAG 2.2 A criterion 2.2.1 - Timing Adjustable).
• In the "Property search" page there are confirmation messages for saved searches and creating alerts that are not persistent. (WCAG 2.2 A criterion 2.2.1 - Timing Adjustable).
• The title for the Create an account step 1 and 2 does not properly convey the purpose of the page. (WCAG 2.2 A criterion 2.4.2 - Page Titled).
• On some pages when information modals are opened, focus is sent to the modal. (WCAG 2.2 A criterion 2.4.3 - Focus Order).
• There are duplicate links (Featured properties component and Home page) where one link does not identify the link target and should have single link with the appropriate link text instead. (WCAG 2.2 A criterion 2.4.4 - Link Purpose (In Context)).
• On some pages, there are some visible labels that that do not match their programmatic names. (WCAG 2.2 A criterion 2.5.3 - Label in Name).
• On some pages, there are fields that allow character input but resets due to error detection but the user is not notified of this. (WCAG 2.2 A criterion 3.3.1 - Error identification).
• On the send enquiry to seller page there are error messages that are provided in text that are not programmatically associated with the input elements. (WCAG 2.2 A criterion 3.3.1 - Error identification).
• The required fields in various forms (Send enquiry to seller, Create an account step 1 of 2, Sign in) do not use the required attribute. (WCAG 2.2 A criterion 3.3.1 - Error identification).
• Instructions to convey that all fields are required is missing on the send enquiry to seller page. (WCAG 2.2 A criterion 3.3.2 - Labels or Instruction).
• Placeholder text should not be used for labelling text boxes. (WCAG 2.2 A criterion 3.3.2 - Labels or Instruction).
• The name role or value of some accordion controls, dropdown lists, zoom controls, radio buttons, checkboxes, filter buttons, sort controls, form input elements, controls in the property image carousel, next and previous controls in the search results page, cannot be programmatically determined. (WCAG 2.2 A criterion 4.1.2 - Name, Role, Value).
• Some input fields that collect an individual’s personal data in some pages (Send enquiry to seller, Create an account step 1 of 2, Sign-in) do not have the necessary “autocomplete” attributes. (WCAG 2.2 A criterion 1.3.5 - Identify Input Purpose).
• A limited number of text components do not provide sufficient contrast between the foreground and background colours. (WCAG 2.2 AA criterion 1.4.3 - Colour Contrast).
• In the main navigation, some of the links are unavailable when resizing text to 200%. (WCAG 2.2 AA criterion 1.4.4 - Resize Text).
• With the browser window width set to 1280px and magnification at 400%, not all of the links in the main navigation are visible and there are some components that have content that is no longer displayed or the main content area is restricted to a third of the user's visible area of a webpage on a screen. (WCAG 2.2 AA criterion 1.4.10 - Reflow).
• A limited number of non-text elements do not provide sufficient contrast between the foreground and background colours. (WCAG 2.2 AA criterion 1.4.11 - Non-text Contrast).
• Focus is not visible on some controls in some components (Search and filter, FAQs). (WCAG 2.2 AA criterion 2.4.7 - Focus Visible).
• Status messages in some components are not read out without receiving focus first. (WCAG 2.2 AA criterion 4.1.3 - Status Messages).

Disproportionate burden

N/A - we are planning to fix all the issues we have so far identified in testing.

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

N/A

We will resolve all non-compliance issues that are within our control (detailed under ‘non compliance with the accessibility regulations’) and update this statement.

This website has been audited to ensure compliance with WCAG 2.2 AA. A sample of pages was tested which reflected all the key user journeys for the Homes for Londoners service target users.

We tested: Homes for Londoners website, available at: https://homes-uat.london.gov.uk/

This website was last tested on 18 November 2025. The test was carried out by Test Partners Ltd.

This statement was prepared on 20 November 2025. It was last reviewed on 21 November 2025.

We followed GOV.UK guidance on deciding how to check the Homes for Londoners website as follows:

1. We manually assessed all the “unique” pages such as the "Sign-in" page to determine the type of content on those pages.
2. We identified a minimum representative subset of pages that contain examples of the most common layouts, components and features, including:
   1. Important “unique pages”.
   2. Pages with text content.
   3. Interactive elements such as forms and content filtering.
3. We conducted a manual WCAG audit on the representative subset of pages.