This accessibility statement applies to:

• the iOS GOV.UK betaapp, app version 1.0.0, first published in July 2025
• the Android GOV.UK betaapp, app version 1.0.0, first published in July 2025
• the test version of the GOV.UK app (available on both iOS and Android)

This mobile application is run by the Government Digital Service. We want as many people as possible to be able to use this mobile application. For example, that means you should be able to:

• toggle between light mode and dark mode using device settings
• increase font size by at least 200%, or use the magnification or zoom features on your device
• listen to most of the app using a screen reader (including the most recent version of VoiceOver or TalkBack)
• navigate most of the app using a keyboard or switch control

We’ve 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 mobile application is

We know that some parts of the mobile application are not fully accessible.

For the Apple iOS version:

• in search results, swiping vertically or horizontally to navigate does not work in the way VoiceOver users would expect
• it’sparts notof possiblethe toapp usecannot ‘Assistivebe Touch’easily andnavigated iOSwith Reachabilityan modeexternal atkeyboard, thepreventing samesome timeusers from accessing all content or selecting links

For the Android version:

• thewhen homeusing pagean hasexternal akeyboard, GOV.UKthere logoare insteadseveral parts of athe textapp heading,where whichit’s maydifficult maketo thesee structurewhat’s being focused on
• parts of the pageapp hardercannot forbe screeneasily readernavigated with an external keyboard, preventing some users tofrom understandaccessing all content or selecting links
• in GOV.UK Chat conversations, users cannot select individual links within Chat’s responses when usingnavigating with an external keyboard,keyboard
• in thereGOV.UK areChat severalconversations, partswhen ofChat gives very long responses, the appscreen wheredoes it’snot difficultautomatically scroll to seeshow what’sthe specific content currently being focusedread onor highlighted

GOV.UK website and services

When you access GOV.UK content through the app, you may be taken to www.gov.uk or to a GOV.UK service.

You can read the accessibility statement for www.gov.uk to find out details of how accessible the website is.

Each GOV.UK service has its own accessibility page, with details of how accessible the service is, how to report problems and how to request information in an alternative format. You can access these pages from the footer inside the service.

Feedback and contact information 

Contact the GOV.UK app team if:

• you find any problems not listed on this page
• you think we’re not meeting accessibility requirements
• you need information in a different format

If you need information in a different format, include in your message:

• the title of the page in the app
• your email address and name
• the format you need - for example, plain text, braille, BSL, large print or audio CD

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 live in England, Scotland or Wales
• the Equality Commission for Northern Ireland (ECNI) if you live in Northern Ireland

Technical information about the accessibility of the GOV.UK app

The Government Digital Service is committed to making its mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status 

The Apple iOS and Android versions of the GOV.UK app have been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

TheBoth the Apple iOS versionand Android versions of this mobile application isare fullypartially compliant with the WebWCAG Content Accessibility Guidelines version 2.2 AA standard.standard.

The Androidtest version of thisthe mobileGOV.UK applicationapp is partiallynot compliant with the WebWCAG Content Accessibility Guidelines version 2.2 AA standard,standard.

More dueinformation toon non-accessible content in the non-complianceapp listedis available below.

Non-accessible content

Non-compliance with the accessibility regulations

HomeDifficult pageto logosee insteadwhat’s ofbeing textfocused headingon when using external keyboard

OnWhen using an external keyboard on the Android version of the app, thethere homeare pageseveral hasparts a GOV.UK logo instead of a text heading, which may make the structureapp ofwhere theit’s pagedifficult harderto forsee screenwhat’s readerbeing usersfocused toon. understand. This fails WCAG 2.2 AAA success criterion 1.3.12.4.7 (Info(Focus and Relationships).Visible).

We plan to fix this issue by OctoberSeptember 2025.2026.

DifficultIssue tonavigating seecontent what’s being focused on when using external keyboard

WhenIn usingboth the Android and iOS versions of the app, parts of the app cannot be easily navigated with an external keyboardkeyboard. onThis prevents some users from accessing all the content in the app or selecting links. 

In the Android version of the app, thereusers arecannot severalselect partsindividual oflinks thewithin appGOV.UK whereChat it’sconversations difficultwhen tonavigating seewith what’san beingexternal focused on. keyboard.

This fails WCAG 2.2 AAA success criterion 2.4.72.1.1 (Focus Visible).(Keyboard).

We plan to fix this issue by OctoberSeptember 2025.2026.

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

Fixing these issues isn’t required as part of the accessibility regulations, but we know they make it harder for some people to use the app. We do not have immediate plans to prioritise these issues, but we are committed to reviewing them in the future.

VoiceOver swipe navigation in search results

In search results on the iOS version, swiping vertically or horizontally to navigate does not work in the way VoiceOver users would expect. Swiping vertically does not navigate users from one search result title to the next. Swiping horizontally does not navigate users from the search result title to the search result description - instead, it navigates them to the next search result title.

Focus does not move with announcements in long GOV.UK Chat responses

WeIn doGOV.UK Chat conversations, when Chat gives very long responses, the screen does not planautomatically scroll to fixshow thisthe issue,specific as:content currently being read or highlighted. This means that while a user may hear the text being read by a screen reader or see a link highlighted by their keyboard, that content is hidden behind other parts of the screen.

• it’s

  Test notversion requiredof asthe partGOV.UK app

  The test version of the accessibilityGOV.UK regulations

Issueapp withcontains Assistivenew Touchfeatures andthat iOSare Reachabilitystill mode

in development. We dotest notthese planfeatures so we can gather feedback to fiximprove them. This means that parts of the issueapp withmay Assistivenot Touchwork as intended and Reachabilitymay mode,not as:be fully WCAG 2.2 AA compliant.

In addition to the issues with the publicly available version of the app, we are aware of several more instances of non-compliant content in the test version of the app only:

• it’s

  The focus order of some screens is not requiredlogical aswhen parttabbing ofusing thea accessibilitykeyboard regulationsor a screen reader. This fails WCAG 2.2 A success criterion 2.4.3 (Focus Order).

• Reachability

  On modethe is‘Driving anand Appletransport’ feature,screen, Android users cannot focus on the ‘Vehicles’ and isn’t‘Licence’ somethingbuttons wewhen canswitch technicallycontrol fixis on. This fails WCAG 2.2 A success criterion 4.1.2 (Name, Role, Value).

• On the ‘Messages’ screen on the iOS version, screen readers do not announce a heading. This fails WCAG 2.2 A success criterion 2.4.1 (Bypass Blocks).

Preparation of this accessibility statement 

This statement was prepared on 18 March 2025. It was last reviewed on 112 JulyAugust 2025.2026.

The Android and iOS versions of the GOV.UK app were last tested on 222 JuneDecember 2025 against the WCAG 2.2 AA standard. 

The test was carried out by theZoonou. Digital Accessibility Centre. It was tested on Android and iOS, using a range of assistive technology combinations.

The test version of the GOV.UK app was last tested on 23 July 2026. The test was carried out by Zoonou.

We also used findings from our own testing when preparing this accessibility statement.