Guidance

Accessibility statement for Provide evidence of your identity for Companies House

Published 9 December 2025

This accessibility statement applies to the ‘Provide evidence of your identity for Companies House’ service.

There is a separate accessibility statement for the ‘Verify your identity for Companies House’ service.

Feedback and contact information

We’re always looking to improve the accessibility of our services. If you find any problems not listed on this page or have difficulty using any part of this service, contact Companies House.

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

Technical information about this website’s accessibility

Companies House 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.

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

We plan to test it against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard soon.

Non-accessible content

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

• The default language is not defined, so information may be miscommunicated to people using a screen reader. This fails WCAG 2.2 success criterion 3.1.1 (language of page).
• Some pages use identical or incomplete page titles, so it may be difficult for people using screen readers to identify the purpose of each page. This fails WCAG 2.2 success criterion 2.4.2 (page titled).
• When selecting a different language, the images of flags given alternative text which duplicates corresponding text. This may be unnecessary for people who use screen readers. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
• When selecting a different language, the different options do not have labels defined which may result in people who use screen readers not being able to understand their purpose. This fails WCAG 2.2 success criterion 2.4.6 (headings and labels).
• When selecting a different language, colour alone is used to identify which item is in focus. This may cause issues for users who have difficulty distinguishing colours. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).
• When selecting a different language, people who use screen readers may not be able to distinguish which language has been selected. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
• On some screens text is presented only within an image without a text alternative, making it impossible for people who use screen readers to access the information. People with low vision who rely on text resizing or high-contrast settings cannot adjust the text, and users with cognitive impairments may struggle because the text cannot be adapted for easier reading. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
• On some screens there are missing or skipped headings, meaning people who use screen readers or other assistive technologies may find it difficult to understand the structure of the content. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
• On multiple screens the colour of the text is not of sufficient enough contrast against the background, which may make it difficult for people with low vision to read. This fails WCAG success criterion 1.4.3 (contrast (minimum)).
• Some input fields do not have associated labels, meaning people who use screen readers may not be able to understand the purpose of the field. This fails WCAG success criterion 1.3.1 (info and relationships).
• On multiple screens the colour of the border on input fields is not of sufficient enough contrast against the background, which may make it difficult for people with low vision to distinguish the field. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).
• The purpose of some input fields has not been declared, which means they will not automatically populate with the user’s pre-saved information, such as their email address. This may present issues for users with learning or mobility impairments. People who use screen readers may also be unclear as to the purpose of the field. This fails WCAG success criterion 1.3.5 (identify input purpose).
• Some links do not have a visible focus indicator, meaning people who navigate using a keyboard as well as users with low vision may not be able to easily navigate. This fails WCAG success criterion 2.4.7 (focus visible).
• Some checkboxes are not programmatically linked to their corresponding label, meaning people who use a screen reader may not understand their purpose. This fails WCAG success criterion 1.3.1 (info and relationships).
• Some content is presented within iFrames that do not have titles, meaning people who use screen readers may not understand the purpose of the iFrame. This fails WCAG success criterion 4.1.2 (name, role, value).
• Some content is only visually presented as a list but not defined as a list. This will make it difficult for people who use a screen reader to quickly navigate the list. This fails WCAG success criterion 1.3.1 (info and relationships).
• Some input fields have inaccurate labels, meaning people who use screen readers may not understand their purpose. This fails WCAG success criterion 2.4.6 (headings and labels).
• Some interactive elements do not identify themselves as buttons in the code, which means screen reader users cannot tell they are clickable or understand what action they perform. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
• Some interactive elements cannot be used with a keyboard, which means people who rely on keyboard navigation or use screen readers cannot access the actions they provide. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).
• Some content updates automatically, but the change is not announced by screen readers. This means people using screen readers may not know that new information has appeared. This fails WCAG 2.2 success criterion 4.1.3 (status messages).
• Some content is visually hidden, but is still available to screen readers, which may cause confusion for people who use them. This fails WCAG 2.2 success criterion 2.4.3 (focus order).
• There is no way to pause or stop a moving decorative image, which can make it hard for people with attention difficulties, low vision, or those using keyboard navigation to focus on the content. This fails WCAG 2.2 success criterion 2.2.2 (pause, stop, hide).
• Some image buttons do not have a text description, so people using screen readers cannot understand what the buttons do. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
• Users are required to scan an ID to complete the process, but there is no alternative method provided. This makes it difficult for people with mobility impairments and those using screen readers to complete the task. This fails WCAG 2.2 success criterion 2.5.4 (motion actuation).
• There is no button to pause or play moving instructions, which makes it hard for people with attention difficulties, low vision, screen reader users, and those who navigate using a keyboard to read and follow the content. This fails WCAG 2.2 success criterion 2.2.2 (pause, stop, hide).
• Some text is incorrectly marked up as a heading, meaning people using screen readers may not understand the page structure. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
• Some informative images have incorrect alternative text, which means people using screen readers cannot understand the information the image is meant to convey. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
• Some decorative images have been given descriptive alternative text, which is unnecessary for people using screen readers. This fails WCAG 2.2 criterion 1.1.1 (non-text content).

Preparation of this accessibility statement

This statement was prepared on 9 December 2025.

This website was last tested in August 2025 against the WCAG 2.1 AA standard.

The testing was carried out by BarrierBreak following the complete customer journey for identity verification and face matching. This involved simulating the actual user experience, starting from initiating the identity verification process, uploading or capturing identity documents, performing biometric checks, and completing the verification steps.