Accessibility statement

Accessibility statement for Golden Ledger

This accessibility statement applies to the Golden Ledger website at goldenledger.co.uk, including the public pages and the signed-in service used by building owners, managing agents and councils.

Golden Ledger is run by MatchKey Technology Limited on behalf of local councils. We want as many people as possible to be able to use it. For example, you should be able to:

• change text size, line spacing and contrast using the Display settings button on every page, and your browser's own settings
• zoom in up to 400% without the text spilling off the screen
• turn off moving parts of the page, using Display settings or your device's "reduce motion" setting
• move around the website using just a keyboard, with a "Skip to main content" link
• use the website with a screen reader, such as JAWS, NVDA or VoiceOver

We have also made the 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

The website is designed to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. It has not yet been independently audited. We know some parts are not fully accessible:

• some PDF documents are not fully accessible to screen reader software
• documents uploaded by building owners, and HM Land Registry registers, are not produced by us and may not be accessible
• some pages have moving graphics when they load or as you scroll; you can turn these off

Feedback and contact information

If you need information on this website in a different format, such as accessible PDF, large print, easy read, audio recording or braille, email support@goldenledger.co.uk.

We will consider your request and get back to you within 10 working days.

If you are a building owner and cannot use Golden Ledger at all, contact your council. It can tell you other ways to send your information.

Reporting accessibility problems with this website

We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, email support@goldenledger.co.uk. Tell us the page address, what you were trying to do and what went wrong.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the "accessibility regulations"). They apply to the councils that use Golden Ledger. MatchKey is a private company, so they do not apply to us directly, but we publish this statement in the same form and follow the same standard. We also have a duty to make reasonable adjustments under the Equality Act 2010. If you are not happy with how we respond to your complaint, contact your council or the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

MatchKey Technology Limited is committed to making its website accessible, and follows the accessibility regulations as if they applied to it.

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.

Non-accessible content

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

Non-compliance with the accessibility regulations

• Council report PDFs. The status reports councils download as PDF are generated without tags, so screen readers may not read headings and tables in the right order. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). The same report is available as a CSV file, and we can send it in another format on request. We are working to produce tagged PDFs.
• Moving graphics on public pages. Some headings, charts and illustrations fade, rise or draw in when the page loads or as you scroll, and one marker pulses three times, for about 5.4 seconds. They stop when your device asks for reduced motion or when you choose "Reduce motion" in Display settings, and the full page is always shown without them. Because the pulse runs for more than 5 seconds, it does not meet WCAG 2.2 success criterion 2.2.2 (Pause, Stop, Hide) unless you use one of those settings. We are shortening it to under 5 seconds.
• The website has not yet been independently audited. Anything an audit finds will be listed here.
• The signed-in service has not yet been tested in the way described under Preparation below, so it may have problems we do not know about yet.

Content that is not within the scope of the accessibility regulations

• Documents uploaded by building owners (for example fire risk assessments and EWS1 forms) and HM Land Registry registers are third-party content that we do not produce, fund or control, so they are not within scope (regulation 4(2)(e)).

What we are doing to improve accessibility

• Commission an independent WCAG 2.2 AA audit and publish its findings here.
• Produce council reports as tagged, accessible PDFs.
• Test with screen readers (NVDA, JAWS, VoiceOver), and test the signed-in service, and add the results to this statement.
• Shorten the pulsing marker to under 5 seconds.
• Every public page is checked with automated accessibility testing (axe-core) before any change to the website goes live.
• Our automated checks already require every animation to stop under reduced motion.

Preparation of this accessibility statement

This statement was prepared on 21 October 2026. It was last reviewed on 23 October 2026.

This website has not yet been independently audited. On 23 October 2026 MatchKey tested it against WCAG 2.2 AA itself. We tested every public page, the sign-in page, the page shown for an address that does not exist, and the steps an owner takes up to claiming a building, including entering a wrong access code. We did not sign in.

We used:

• automated testing with axe-core in the Chrome browser, at desktop width (1440 pixels) and phone width (375 pixels)
• a keyboard only, checking that every link and control can be reached in a sensible order, that you can always see which one has focus, and that the header and cookie bar never hide it
• the size of every link and button you can tap
• the page at 320 pixels wide (the same as zooming to 400%), with extra spacing between letters, words, lines and paragraphs
• the reduce motion setting on the device and in Display settings, and the other Display settings
• the names a screen reader gives every drawing and chart, and the page language
• how the access code form tells you about a mistake

We fixed what we found: two forms with the same name, a heading out of order, buttons that ran off the edge of a narrow screen, a table that could not be scrolled with the keyboard, links that could hide under the header when moving backwards with the keyboard, smooth scrolling that ignored the reduce motion setting, and a photo caption that was hard to read. Display settings for text size, line spacing and contrast did not change most pages; they now do.

We have not yet tested with screen readers, with Windows high contrast mode, or in browsers other than Chrome, and we have not tested the signed-in service. We will update this statement with those results and with the results of the audit.