Accessibility statement for Get documents for a marriage or civil partnership abroad

This accessibility statement applies to the Get documents for a marriage or civil partnership abroad service.

This website is run by the Foreign, Commonwealth & Development Office. We want as many people as possible to be able to use this website. For example, that means you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 400% without the text spilling off the screen
• view the browser in a one column format (1280px browser width and zoom in to 400%)
• navigate most of the website using just a keyboard
• navigate most of the website using speech recognition software
• listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet (opens in new tab) has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible.

• Our feedback survey may be difficult to use with assistive technology. Some text can be hard to read and some form fields aren’t clearly labelled or announced. In some places, the page structure also does not support easy navigation.
• Error messages may appear one at a time on some pages of this service, even when there are several errors. This means you might fix one error and then only find out about another one afterwards.
• Old error messages may still be shown on some pages if you go back to them, even if you have corrected the error before. This may cause confusion, as the page may announce errors that are no longer relevant.
• Some fields do not include autocomplete hints. This can make entering personal details more difficult or time-consuming.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, email digitalservicesfeedback@fcdo.gov.uk.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

• email digitalservicesfeedback@fcdo.gov.uk.

We’ll consider your request and get back to you in 5 working days.

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit, we can arrange a British Sign Language (BSL) interpreter.

Find out how to contact us (opens in new tab).

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) (opens in new tab)

Technical information about this website’s accessibility

The Foreign, Commonwealth & Development Office (FCDO) 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.2 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 (opens in new tab) AA standard, due to the non-compliances listed below.

Non-accessible content

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

• Some fields in the service are missing the relevant autocomplete attribute. This means it may be more difficult for users to understand the purpose of these fields and complete them. This fails WCAG 2.2 success criterion 1.3.5 - Identify input purpose. We plan to add autocomplete attributes for all fields in the service by December 2026.
• Old error messages for errors that have been corrected are displayed when a user goes back to a previous page. This can confuse users because it may not be clear whether the errors have been resolved or not. This fails WCAG 2.2 success criteria 3.3.1 – Error identification, 3.3.3 - Error Suggestion and 4.1.3 - Status Messages. We plan to update the service so error messages are cleared when you leave a page and only reappear if the issue is still present by December 2026.

Our third-party survey tool also has the following accessibility issues on some pages.

• Low contrast text. This can mean that users with low vision, colour vision deficiency, or who are viewing the page in poor lighting may not be able to read some content. This fails WCAG criterion 1.4.3 - Contrast (minimum).
• One required field is not clearly marked as required for screen reader users. This may make it harder for users to know what must be completed. This fails WCAG 2.2 success criteria 1.3.1 - Info and Relationships, 3.3.2 Labels or Instructions, and 4.1.2 Name Role Value.
• Some fields use duplicate labels, which can confuse people using assistive technology. This fails WCAG 2.2 success criteria 2.4.6 - Headings and Labels, 3.3.2 - Labels or Instructions, 4.1.2 - Name Role Value.
• Some non interactive elements use title attributes. Content exposed only through a title attribute may be inconsistently available to keyboard, touch, and assistive technology users. This is not best practice under WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
• Some fields are missing autocomplete attributes. This means it may be more difficult for users to understand the purpose of these fields and complete them. This fails WCAG 2.2 success criterion 1.3.5 - Identify input purpose.
• On some pages, the service is missing navigation and main landmarks. This can make the page structure harder for screen reader users to understand. This fails WCAG 2.2 success criteria 1.3.1 – Info and relationships and 2.4.1 - Bypass blocks.
• On one page there is no way to skip repeated content, which can slow down navigation for keyboard and screen reader users. This fails WCAG 2.4.1 – Bypass blocks.
• One heading skips a level. This can make the page structure harder for screen reader users to follow. This is not best practice under WCAG 2.2 success criterion 1.3.1 – Info and relationships.
• A line break is used for layout rather than meaningful structure. This may cause confusing announcements for screen reader users. This is not best practice under WCAG 2.2 success criterion 1.3.1 – Info and relationships.

We plan to explore options for a more accessible survey tool for the service.

Content that’s not within the scope of this accessibility statement

Our service uses a separate payment service, GOV.UK Pay.

Visit the GOV.UK Pay accessibility statement (opens in new tab) for details of:

• the payment service’s accessibility
• how to report accessibility problems
• how to ask for information in an alternative format

Preparation of this accessibility statement

This statement was prepared on 5th August 2026. It was last reviewed on 5th August 2026.

This website was last tested on 29th July 2026. An audit of the service against the WCAG 2.2 AA criteria was carried out by the team responsible for this service.