GOV.UK ID Check app: accessibility statement
How we've tested the accessibility of the GOV.UK ID Check app, issues we've found, and how you can report problems.
This accessibility statement applies to:
- the iOS GOV.UK ID Check mobile application, first published in July 2022
- the Android GOV.UK ID Check mobile application, first published in October 2022
- web pages that check if your device is suitable to use these apps
The mobile applications and website are run by the Government Digital Service (GDS).
We want as many people as possible to be able to use these applications. For example, that means you should be able to:
- change colours, contrast levels and font size
- zoom in up to 300% without the text spilling off the screen
- navigate most of the application using just a keyboard
- navigate most of the application using speech recognition software
- listen to most of the application using your device’s screen reader (including VoiceOver and TalkBack)
- listen to most of the web pages using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the content as simple as possible to understand.
AbilityNet has advice on making your devices easier to use if you have a disability.
How accessible the mobile applications are
Apple iOS application
The app will use your iOS language setting rather than the language you choose on the GOV.UK One Login website.
If you’ve turned on the Reduce Motion feature on your device, you may find that some animations still play.
If you’re using a screen reader, you may have difficulty using the app because:
- the instructions about how to scan the chip in your photo ID are not read out in a logical order. As you move through the carousel - you’ll need to swipe up with 2 fingers to start reading from the top of the screen on each slide
- the button to replay a decorative animation about how to scan the chip in your photo ID is announced
If you’ve increased the font size on your device, the instructions for how to scan the chip in your photo ID might be difficult to see. You’ll need to scroll down in each section to see the all the text.
Android application
The app will use your Android system language setting rather than the language you choose on the GOV.UK One Login website.
On some devices, you might find it difficult to interact with the ‘open source licences’ link on the first page of the app. This is because it’s smaller than the recommended size.
If you’re using an external keyboard and you access the carousel with instructions about how to scan the chip in your photo ID, you may find that you cannot close the carousel.
How accessible the website is
We know some parts of the website are not fully accessible – you can find full details on the accessibility statement for GOV.UK One Login.
When you go through the web pages that check if your device is suitable to use the app, your language preference might not persist if you use the ‘back’ link. This means you may need to select your preferred language again.
Feedback and contact information
If you have difficulty using the applications or the website, contact us.
Reporting accessibility problems with the mobile application
We’re always looking to improve the accessibility of this service. If you find any problems that are not listed on this page or think we’re not meeting accessibility requirements, contact us.
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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service, which is run on behalf of EHRC.
Technical information about this mobile application’s accessibility
GDS is committed to making its website and applications 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 aims of the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
If you find an issue that we have yet to identify, please contact us using the details in the ‘Reporting accessibility problems with this mobile application’ section of this statement.
Non-accessible content in the Apple iOS application
The iOS application does not fully comply with accessibility regulations for the following reasons:
- users may find it difficult to predict which language setting the website and application will use because of the technical complexity of implementing language switching between devices
- when a user goes through the web pages that check if their device is suitable to use the app, the technical implementation of the ‘back’ link means their language preference might not persist if they use the ‘back’ link - this means they may need to select their preferred language again
- some animations still play even when a user has turned on the Reduce Motion feature – this fails WCAG 2.2 success criterion 2.2.2 Pause, stop, hide (Level A)
- instructions about how to scan the chip in a photo ID are not read out in a logical order to screen reader users - this fails WCAG 2.2 success criterion 2.4.3 Focus Order (Level A)
- a replay button for decorative animations is sometimes announced to screen reader users - this fails WCAG 2.2 success criterion 3.2.4 Consistent Identification (Level AA)
Non-accessible content in the Android application
The Android application does not fully comply with accessibility regulations for the following reasons:
- users may find it difficult to predict which language setting the website and application will use because of the technical complexity of implementing language switching between devices
- when a user goes through the web pages that check if their device is suitable to use the app, the technical implementation of the ‘back’ link means their language preference might not persist if they use the ‘back’ link - this means they may need to select their preferred language again
- the ‘open source licences’ link on the first page of the app is displayed with a target size that is smaller than Google’s recommended 48 device pixels on some Android devices- this fails WCAG 2.2 success criterion 2.5.8 (Target Size) and WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured)
- the only way for keyboard users to close the carousel with instructions about how to scan the chip in a photo ID is with a keyboard command, which may not be a standard exit method - this fails WCAG 2.2 success criterion 2.1.2 No Keyboard Trap (Level A)
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
At this time, we have not identified any content that is not within scope of the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 18 July 2022. It was last reviewed and updated in September 2025.
These mobile applications were last tested in September 2025 by the GOV.UK One Login Accessibility Team. The Digital Accessibility Centre carried out testing in July 2023. All parts of the mobile application journey were tested.