UK
Accessibility statement for www.gov.uk - GOV.UK
Accessibility statement for www.gov.uk - GOV.UK
Cookies on GOV.UK
We use some essential cookies to make this website work.
We’d like to set additional cookies to understand how you use GOV.UK, remember your settings and improve government services.
We also use cookies set by other sites to help us deliver content from their services.
You have accepted additional cookies.
You can
change your cookie settings
at any time.
You have rejected additional cookies.
You can
change your cookie settings
at any time.
View cookies
Accessibility statement for www.gov.uk
This accessibility statement applies to the www.gov.uk website. It does not cover other GOV.UK subdomains such as service subdomains (for example design-system.service.gov.uk) or the blog subdomain (www.blog.gov.uk), which have their own accessibility statements.
This website is run by the Government Digital Service. Other government departments and agencies publish content on www.gov.uk.
How you should be able to use this website
We want as many people as possible to be able to use this website. You should be able to:
change colours, contrast levels and fonts using browser or device settings
zoom in up to 400% without the text spilling off the screen
navigate most of the website using a keyboard or speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We also make the website 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
Parts of this website are not fully accessible. For example:
some pages and document attachments are not written in plain English
some tables do not have row or column headers
some documents have poor colour contrast
some heading elements are not consistent
some images do not have image descriptions
some images used to convey information have poor colour contrast
some information in tables cannot be reached with a keyboard
many documents are in
PDF
format and are not accessible
GOV.UK services
Each 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
Tell us if you need information in a different format
In your message, include:
the web address (URL) of the content
your email address and name
the format you need - for example, plain text, braille,
BSL
, large print or audio CD
You can request a
PDF
in an accessible format from its page. Click ‘Request an accessible format’ to contact the organisation that published the document.
You can also view the organisation’s
accessible document policy
to report any problems or request documents in an alternative format.
Reporting accessibility problems with this website
If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements,
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
The Government Digital Service is committed to making its websites 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
Web Content Accessibility Guidelines version 2.2
AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Images on some pages do not always have suitable image descriptions. Users of assistive technologies may not have access to information conveyed in images. This fails
WCAG
2.2 success criterion 1.1.1 (Non-text Content).
Some tables do not have table row or column headers. This means assistive technologies will not read the tables correctly. This fails
WCAG
2.2 success criterion 1.3.1 (Info and Relationships).
Some tables are structured incorrectly, so screen readers cannot understand the relationships between information in the table. This fails
WCAG
2.2 success criterion 1.3.1 (Info and Relationships).
Some headings do not display correctly. They may look like normal text or a different type of heading. This fails
WCAG
2.2 success criterion 1.3.1 (Info and Relationships).
Some images use colour as the only way to convey meaning. This fails
WCAG
2.2 success criterion 1.4.1 (Use of Color).
Some images include text with poor colour contrast to its background. This fails
WCAG
2.2 success criterion 1.4.3 (Contrast (Minimum)).
Some pages use images of text instead of text. This fails
WCAG
2.2 success criterion 1.4.5 (Images of Text).
Some images include elements with poor colour contrast to the background. This fails
WCAG
2.2 success criterion 1.4.11 (Non-text Contrast).
If a table is too wide to fit on the screen, the hidden information cannot be reached with a keyboard. This fails
WCAG
2.2 success criterion 2.1.1 (Keyboard).
Some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails
WCAG
2.2 success criterion 2.4.2 (Page Titled).
Some headings don’t accurately describe the content underneath. This fails
WCAG
2.2 success criterion 2.4.6 (Headings and Labels).
On some pages the back to top link at the bottom of the page can hide focussed elements. This fails
WCAG
2.2 success criterion 2.4.11 (Focus Not Obscured (Minimum)).
Some images of text that are used as links have image descriptions that don’t include all of the text. This fails
WCAG
2.2 success criterion 2.5.3 (Label in Name).
The change in the default written language is not correctly identified on some pages. This means screen readers will not read content correctly. This fails
WCAG
2.2 success criterion 3.1.2 (Language of Parts).
Some pages have inconsistently-placed language navigation. This fails
WCAG
2.2 success criterion 3.2.3 (Consistent Navigation).
Translation Navigation is inconsistently named. This fails
WCAG
2.2 success criterion 3.2.4 (Consistent Identification).
Some links that reveal more content can cause some screen reader users to lose their position on the page. This fails
WCAG
2.2 success criterion 4.1.2 (Name, Role, Value).
Some pages include videos without captions. This fails
WCAG
2.2 success criterion 1.2.2 (Captions)
Some pages contain instructions that depend on visually identifying checkboxes to answer questions. This fails
WCAG
2.2 success criterion 1.3.3 (Sensory Characteristics)
Some pages contain videos without a transcript. This fails
WCAG
2.2 success criterion 1.2.3 (Audio Description or Media Alternative)
Many documents are in non-HTML formats, for example
PDF
. They are not accessible in a number of ways including missing text alternatives and missing document structure.
View the
accessible document policy
of the organisation that published the document to report any problems or request documents in an alternative format. If more than one organisation is listed, view the accessible document policy of the first.
Content that’s not within the scope of the accessibility regulations
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
What we’re doing to improve accessibility
We are working alongside other government departments and agencies to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.
Preparation of this accessibility statement
This statement was prepared on 23 September 2019. It was last reviewed on 29 January 2026.
This website was last tested in March 2025 against the
WCAG
2.2 AA standard. This test of a representative sample of pages was carried out by the Digital Accessibility Centre (
DAC
).
We also used findings from our own testing when preparing this accessibility statement.
Updates to this page
Related content
Is this page useful?
Maybe
Thank you for your feedback
Help us improve GOV.UK
To help us improve GOV.UK, we’d like to know more about your visit today.
Please fill in this survey (opens in a new tab