This website is run by the British Tourist Authority t/a VisitBritain. We want as many people as possible to be able to use this website. For example, that means you should be able to:
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
Please contact us on the details below should you require any content appearing on this website in a more accessible format, for example, a PDF.
More accessible formats may include: large print; easy read; audio recording and; braille.:
We’ll consider your request and get back to you within ten days.
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:
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’). Should you not be happy with how we respond to your complaint, please contact the Equality Advisory and Support Service (EASS)
VisitBritain is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Some images do not have a text alternative, so users with a screen reader are currently unable to access this information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
Some text does not have sufficient colour contrast, so users with low vision may have difficulties separating foreground from background. This fails WCAG 2.1 success criteria 1.4.3 Contrast (Minimum).
Some of our hyperlinks are missing a meaningful description, so users with a screen reader may face challenges in understanding the meaning of content. This fails WCAG 2.1 success criterion 2.4.4 Link Purpose.
It’s not possible for users to change text size without some of the content overlapping. This fails WCAG 2.1 success criterion 1.4.4 (resize text).
Some of our interactive elements, like maps are not accessible for users with a screen reader. This fails WCAG 2.1 success criterion 1.1.1 Non-text Content.
We plan to replace all our websites over the next 2-3 years. As part of that and our ongoing work on accessibility we will resolve the areas of non-compliance mentioned above. Some areas do however represent a disproportionate burden to resolve prior to the launch of our new websites.
This statement will be updated regularly with timings of fixes. If you require any material on the website in an accessible format, please contact firstname.lastname@example.org
Many of our older PDFs and Word documents do not meet accessibility standards. For example, they may not be structured to be accessible for a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services and forms published as Word documents.
The accessibility regulations do not require us to fix PDFs or other documents which were published prior to 23 September 2018 if they’re not essential to providing our services.
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
We have tested this website by using an accessibility testing tool - Monsido.
We tested our main website platform, available at https://www.visitbritain.com/
We have implemented training for relevant staff, developed documentation and checklists, and we have carried out work to implement multiple fixes in 2020. We will be developing a plan to implement other priority fixes between October 2020 and March 2021. Timings will be updated on this page.
This statement was prepared on 23rd September 2019. It was last updated on 22nd September 2020.