Accessibility statement for Property Alert

This accessibility statement applies to https://propertyalert.landregistry.gov.uk (opens in new tab).

This website is run by HM Land Registry. 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.

Get advice from AbilityNet (opens in new tab) 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. In particular:

Feedback and contact information

If you find any problems that are not listed on this page or think we're not meeting the accessibility requirements, contact us by:

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, contact us by:

We can also provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

We'll consider your request and get back to you within 5 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) (opens in new tab).

Technical information about this website's accessibility

HM Land Registry 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 not compliant with the Web Content Accessibility Guidelines version 2.2 (opens in new tab) AA standard, due to some of 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

Some error messages on address search forms are not helpful and do not give enough information about how to correct the error. This fails WCAG 2.2 success criterion 3.3.3 Error Suggestion (AA).

When adding a new property alert, the error summary for the address search form includes empty links. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (A).

Some form elements do not correctly identify errors for assistive technology because of incorrect use of attributes such as aria-invalid and aria-describedby.

This fails WCAG 2.2 success criterion 3.3.1 Error Identification (A).

The "We have sent you an email" pages do not announce the status message to assistive technology. This fails WCAG 2.2 success criterion 4.1.3 Status Messages (AA).

The horizontal tabbed interface on the property search page does not fully support expected keyboard navigation. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (A).

We aim to address the confirmed A and AA issues by 2 June 2027. This timeline will be refined as ongoing discovery work clarifies the complexity and delivery approach.

We are currently carrying out further discovery work to understand the complexity of the required changes and whether some issues can be resolved sooner.

We will update this statement as individual issues are fixed, and as we learn more about timescales for the remaining issues.

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

No content within Property Alert falls outside the scope of accessibility regulations.

What we're doing to improve accessibility

We are creating a Statement of Requirements covering the confirmed A and AA accessibility issues and using this to trigger a discovery spike. This will help us understand the effort needed and how best to schedule the work, which may be delivered in stages.

We are also working to better understand the impact of the skip-links implementation by carrying out further testing with appropriate screen reader software. We will update this statement if this work identifies additional accessibility issues or required remediation.

Preparation of this accessibility statement

This statement was prepared in October 2020. It was last reviewed on 2 June 2026.

This website was last formally tested on 30 July 2024 against the WCAG 2.2 AA standard.

Tests were carried out on a selection of pages by an internal audit team using a purpose-built WCAG 2.2 test suite.

More recent internal review work carried out in May and June 2026 has been used to update the list of known accessibility issues and inform our approach to resolving them.

Back to top