skip to main content

Accessibility

Culture Collections Accessibility statement

This website is run by UKHSA. 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 
  • navigate most of the website using just a keyboard 
  • navigate some of the website using speech recognition software 
  • listen to some of the website using a screen reader (including the most recent versions of JAWS, NVDA, TalkBack and VoiceOver) 

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. 

 

How accessible this website is 

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

  • A correctly formed heading structure is not present to facilitate navigation. 
  • Decorative imagery contains inappropriate alternative attributes. 
  • Informative imagery lacks alternative attributes. 
  • The autocomplete attribute is not available on forms. 
  • The page titles are not descriptive or unique on the website and PDF documents. 
  • There is only one way to locate some of the webpages. 
  • Dragon Naturally Speaking cannot be used to navigate some of the pages. 
  • Multiple issues surrounding the use of screen readers, including buttons not being announced, and incorrect focus order. 
  • The registration and order submission pages are not announced. 
  • The focus indicator is not visible on the list view and grid view element. 
  • PDF documents are not fully accessible to screen reader users. 

 

Feedback and contact information 

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

  • culturecollections.marketing@ukhsa.gov.uk
  • call Technical Support Telephone: +44 (0)1980 612684

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

If you cannot view the map on our ‘contact us’ page, call or email us for directions. 

 

Reporting accessibility problems with this website 

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: 

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). 

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  

Technical information about this website’s accessibility 

UKHSA 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 

This website is developed in compliance with the Web Content Accessibility Guidelines version 2.1 AA standard. The ‘non-compliances’ are listed below. 

Non-accessible content 

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

Non-compliance with the accessibility regulations 

 

Accessible names are not provided for informative images, including complex images such as graphs. This can result in content not being presented to screen reader users. This fails WCAG 2.1 success criterion 1.1.1 - Non-text Content. 

We plan to resolve this by:  January 2024 
 


Decorative images have been given alternative attributes, resulting in unnecessary information being announced to users of screen readers. This fails WCAG 2.1 success criterion 1.1.1 - Non-Text Content. 

We plan to resolve this by: January 2024 
 
 

Word documents contain non-inline graphics or objects, which means it may be difficult for screen reader users to interact with that object and where the object is relative to the text. This fails WCAG 2.1 success criterion 1.1.1 - Non-text Content.  

We plan to resolve this by: January 2024 

 
 

Within PDFs, the page content is not tagged. All content within a PDF should be included in a tag tree or marked as an artifact to assist screen reader users. This fails WCAG 2.1 success criterion 1.3.1 - Info and Relationships. 
We plan to resolve this by: January 2024 
 
 
 
A correctly formed heading structure is not present to facilitate navigation across the site, with skipped heading levels present. This fails WCAG 2.1 success criterion 2.4.1 - Bypass Blocks.  
We plan to resolve this by: January 2024 
 
 
 
All PDFs lack titles which help the user orient themselves when the PDF opens. This can also hinder users who need to move from one document to another quickly. This fails WCAG 2.1 success criterion 2.4.2 - Page Titled. 
We plan to resolve this by: January 2024 
  

 

There is not more than one way to access pages on the site. For the user to access the Cart, User Settings, Quick Shop or Register page, the user must go through specific journeys rather than search for that page or find it within the site map. This fails WCAG 2.1 success criterion 2.4.5 - Multiple Ways. 
We plan to resolve this by: January 2024 


 

The focus indicator is not visible when the user tabs on the list view and grid view elements on the search page. This can make it difficult for keyboard-only users to keep track of the elements currently in focus. This fails WCAG 2.1 success criterion 2.4.7 - Focus Visible.  
We plan to resolve this by: January 2024 

 

Within PDFs, the language has not been defined. This may mean that users of screen readers are not able to hear the correct pronunciation of certain words. This fails WCAG 2.1 success criterion 3.1.1 - Language of PDF. 

We plan to resolve this by: December 2023 
 

 
When navigating the site using Dragon Naturally Speaking (speech recognition software) users are unable to interact with the entirety of the top navigation, and the check box to accept terms and conditions. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024 

 
A PDF document does not contain XMP metadata which means users of screen readers may not be able to navigate the PDF in a logical way. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024 


 
While using JAWS desktop screen reader, upon clicking the submit button on the Register and Contact Us pages, the user is taken to the CAPTCHA element, and not the error field. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024 


 
While using NVDA desktop screen reader, when the quick view pop-up box appears, it does not receive focus. Instead, the focus will stay on the main page meaning the user is unable to close this pop-up. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024 

 

While using JAWS and NVDA desktop screen readers, TalkBack and VoiceOver mobile screen readers, various buttons across the site are not announced to the user. This can be seen on the Checkout page while trying to upload a purchase order number and where the help button appears on the site. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024 
 

While using TalkBack mobile screen readers, the focus ordering of the page is incorrect. On the Homepage, the top navigation is announced in a different order from what is shown on the screen. This fails WCAG 2.1 success criterion 4.1.2- Name, Role, Value.  
We plan to resolve this by: January 2024  

 

While using VoiceOver mobile screen readers, the main navigation menu is not accessible, so navigation throughout the site cannot be completed via this method. This fails WCAG 2.1 success criterion 4.1.2- Name, Role, Value. 
We plan to resolve this by: January 2024  
 

 

While using TalkBack and VoiceOver mobile screen readers, any arrow indicating a dropdown menu is not announced. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024  

 

 

While using TalkBack and VoiceOver mobile screen readers, on the Summary and Payment page, various fields are not announced, meaning the user is unable to complete the form. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.  
We plan to resolve this by: January 2024  

 

While using JAWS and NVDA desktop screen readers, TalkBack and VoiceOver mobile screen readers, several status messages and form submission confirmations are not announced to the user. These include when registration has been completed, when a product has been added to the cart, if a field has been left blank or if a form has been completed successfully. This fails WCAG 2.1 success criterion 4.1.3 - Status Messages.  
We plan to resolve this by: January 2024  

 

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

[Note: in this subsection list accessibility problems that fall outside the scope of the accessibility regulations.] 

PDFs and other documents 

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. By December 2023, we plan to either fix these or replace them with accessible HTML pages. 

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. For example, we do not plan to fix [example of non-essential document]. 

Any new PDFs or Word documents we publish will meet accessibility standards. 

 

Live video 

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. 

 

What we’re doing to improve accessibility 

Our accessibility roadmap shows how and when we plan to improve accessibility on this website. 

Preparation of this accessibility statement 

This statement was prepared on 21st June 2023. It was last reviewed on 21st June 2023. 

This website was last tested on 20th June 2023. The test was carried out by Zoonou. 

Zoonou used WCAG-EM to define the pages tested and test approach. 

 

 

Powered by nopCommerce