Accessibility statement for Unity HomeMatch (RAMS)
This accessibility statement applies to Home Connections Unity HomeMatch software (RAMS).
This website is run by Home Connections on behalf of the Home Office. 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, contrast levels and fonts.
- Zoom in up to 400% without the text spilling off the screen.
- Navigate most of the website using just a keyboard.
- Navigate most of the website using speech recognition software.
- Listen to most of the website using a screen reader, including the most recent versions of JAWS, NVDA and VoiceOver.
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 accessible this website is
Our site is currently undergoing accessibility improvements. We are actively working to address the remaining issues, which span a range of accessibility barriers identified during manual testing. These include issues with keyboard navigation, screen reader compatibility, focus management, and visual presentation of content.
You can see a full list of any issues we currently know about in the non-accessible content section of this statement.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: resettlementaccommodationmatching@homeoffice.gov.uk.
If you need information on this website in a different format, such as an accessible PDF, large print, easy read, audio recording or braille, email:
resettlementaccommodationmatching@homeoffice.gov.uk.
We will consider your request and get back to you in 20 days.
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).
If you are in Northern Ireland and are not happy with how we respond to your complaint, you can contact the Equality Commission for Northern Ireland, which is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 in Northern Ireland.
Technical information about this website’s accessibility
The Home Office 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.2 due to the issues detailed below in the non-compliances and exemptions list.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
We plan to fix these accessibility issues by June 2026.
Keyboard-only navigation
On the Manage Property page, when changing tabs, for example from Overview to Details, either by mouse click or keyboard, the focus resets to the top of the page. Focus should remain where it is.
Keyboard navigation users may experience confusion or frustration because they have to navigate back to the main content area after switching tabs. This fails WCAG 2.4.3 – Focus Order. Reference: QAT-881.
Tables
When navigating table data using a screen reader, some non-interactive data is announced as a button. This is due to sorting buttons in the column headers but could be confusing to screen reader users.
This fails WCAG 1.3.1 – Info and Relationships and WCAG 4.1.2 – Name, Role, Value. Reference: QAT-880.
Magnification
When using browser zoom at magnifications such as 200% or 400%, it can be difficult to scroll content vertically. Due to sticky elements, the active region of the page can also become a small envelope-shaped area.
When using a touchpad, two-finger swiping can help to mitigate the scrolling issue. This fails WCAG 1.4.10 – Reflow. Reference: QAT-806.
On the Property Description – Edit page, some field labels do not wrap and are visually truncated. Users with sight disabilities may struggle to read the whole field label when entering data.
This fails WCAG 1.4.4 – Resize Text. Reference: QAT-817.
Assistive technology compatibility
On the Property Description – Edit page, when using the JAWS screen reader, the contents of the text-edit field are not announced.
JAWS users may not know that there is already data in the field and may have difficulty getting the screen reader to announce it. A workaround is to use the NVDA screen reader.
This fails WCAG 1.3.1 – Info and Relationships and WCAG 4.1.2 – Name, Role, Value. Reference: QAT-822.
Dragon users cannot navigate to the combo boxes by using the “show all links” command to reveal interactive elements, or by saying “click Available” to reach the Available combo box. The same issue occurs on other fields that use the same component.
This means Dragon users may find it challenging to use the filter functions. They can use workarounds such as the “tab” command to access each combo box or the mouse grid function. However, this is likely to increase the amount of time required to use the function.
This fails WCAG 1.3.1 – Info and Relationships. Reference: QAT-842.
Dragon users cannot navigate to the “Records per page” combo box by using the “show all links” command or by saying “click Records per page”.
This means Dragon users may find it challenging to adjust the number of records displayed per page. They can use the mouse grid function, but this is likely to increase the amount of time required to use the function.
This fails WCAG 2.5.3 – Label in Name. Reference: QAT-844.
Login page
On the Login page, autocomplete is not enabled for the username and password fields. It may take extra effort for keyboard-only users, screen reader users or users with memory disabilities to log in.
This fails WCAG 1.3.5 – Identify Input Purpose. Reference: QAT-824.
Field labels
Infospots are more difficult to activate when using speech recognition software. They do not have unique visible labels and do not display their contents when users try to activate them using voice commands such as “click Information”.
Speech recognition users have to issue “tab” commands to activate the infospots. This fails WCAG 2.5.3 – Label in Name. Reference: QAT-819.
In the Property Information Form, after adding a property, the “Submit Another Property” button is displayed. However, the accessible name of the button is “Submit new property registration”.
Users of speech recognition software may have difficulty activating the button and may have to complete additional steps. This fails WCAG 2.5.3 – Label in Name. Reference: QAT-884.
Combo boxes
In the Property Offer Form, when expanding some combo boxes or select boxes, the first option is automatically selected and it is not obvious how to deselect it.
It can be deselected by expanding the list again and tabbing out of the field, or by clicking the selected option with a mouse. This is not expected behaviour and could lead to incorrect data entry or frustration when entering the correct data.
This fails WCAG 2.1.1 – Keyboard. Reference: QAT-832.
Date fields
In the Property Offer Form, date fields do not give an example of the format in which the date should be entered. Some users with disabilities may experience frustration when trying to enter the date correctly.
This fails WCAG 3.3.2 – Labels or Instructions. Reference: QAT-833.
Error identification
On the List Properties page, if a filter is added where the Property Name contains numbers, for example “Property Name = 155”, an error message is displayed that does not describe the issue in a helpful or informative way.
This fails WCAG 3.3.1 – Error Identification. Reference: QAT-882.
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Preparation of this accessibility statement
This statement was prepared on 23 September 2025. It was last reviewed on 14 July 2026.
This website was last tested on 9 February 2026. The test was carried out by Home Connections Lettings Ltd and the Home Office.
We tested the service using the NVDA screen reader tool by choosing a representative sample of pages that covered all of the user interface components and main functionality that make up the site.