Accessibility statement

Introduction

This accessibility statement applies to the Norfolk Museums website, which is made up of:

This website is run by Norfolk County Council.

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 the website using just a keyboard
Navigate 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)

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We aim to meet the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.2 at AA level.

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

Some search forms have unlabelled or incorrectly labelled fields
Some email newsletter sign up forms:
- Have an email form field that does not support autocomplete
- Do not show error messages when the form hasn't been correctly completed and the user attempts to submit the form using a keyboard. This makes it hard for users to identify errors they have made and correct them
- Tell screen reader users that all fields have invalid input until they have been completed correctly. This may confuse users as this is not typical form behaviour
- Are embedded on the page in an iframe that does not have a descriptive accessible name. This may make it difficult for users to identify the form or find it on the page
- Have text that does not resize
The cookie control has several accessibility issues that may make it difficult to use for visually impaired people
Some Word documents may be difficult to access or use
Some PDF documents may be difficult to access or use
Some videos do not have audio description, which may make them difficult for visually impaired users to understand

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, email museums@norfolk.gov.uk.

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 webaccessibility@norfolk.gov.uk.

We'll consider your request and get back to you in 3 working days.

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

Contact us by phone or visiting us in person

Our museums have audio induction loops at all ticket/reception desks.

Find out how to contact us.

Technical information about this website's accessibility

Norfolk County Council 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 partially compliant with the Web Content Accessibility Guidelines (WCAG) 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

Search forms

Some search forms have unlabelled or incorrectly labelled controls. This fails WCAG 3.3.2 Labels or Instructions and WCAG 4.1.2 Name, Role, Value.

Email newsletter sign up forms

Some email newsletter sign up forms do not provide error messages when one or more fields do not have valid input and the user attempts to submit the form using a keyboard. This fails WCAG 3.3.1 Error identification
Some email newsletter sign up forms include 'aria-invalid="true"' on all form inputs until they have valid input, which triggers the value to change to "false". This is incorrect use of the attribute - on form load it should be set to "false" and it should only be set to "true" if invalid input is detected when validation is performed. This fails WCAG 3.3.1 Error identification
Some email newsletter sign up forms are embedded on the page using a script. This creates an iframe element within the html. The iframe does not have a descriptive accessible name. This fails WCAG 4.1.2 Name, role, value
The email form field in some email newsletter sign up forms does not include the attribute and value 'autocomplete="email"'. This fails WCAG 1.3.5 Identify input purpose
Some email newsletter sign up forms have text that does not resize. This fails WCAG 1.4.4 Resize Text

Videos

Some videos have visual content that is not conveyed in the audio track and audio described versions of the videos have not been provided. This fails WCAG 1.2.3 Audio Description or Media Alternative (Pre-recorded).

Cookie control

The cookie control has several accessibility issues:

The modal dialog that appears when a user selects the 'Customize' button does not have an appropriate role, accessible name or aria-modal attribute. This fails WCAG 4.1.2 Name, Role, Value and WCAG 3.3.2 Labels or Instructions
Some buttons in the dialog do not have sufficiently descriptive accessible names. This fails WCAG 1.3.1 Info and Relationships
Some colour combinations used do not have sufficient colour contrast and rely on colour to communicate a state change. This fails WCAG 1.4.3 Contrast (Minimum) and WCAG 1.4.1 Use of Color

Word documents

There are four Word documents that do not meet accessibility standards. This is because they require user input (act as editable forms or templates) but have visible labels or instructions that aren't programmatically associated with the form field, or do not have programmatically determinable form fields.

This fails:

WCAG 1.3.1 Info and Relationships
WCAG 4.1.2 Name, Role, Value

Norfolk Museums Pass application form

There is a Norfolk Museums Pass application form PDF on the Norfolk Museums Pass page. The PDF does not meet accessibility standards because:

It is an untagged PDF. This means it doesn't contain tags to tell assistive technologies what content is in the document. It can be difficult for people using assistive technologies to navigate, find content, and determine where they are in this document. Screen readers might not read the content in the correct order.
Some of the text in the document does not have sufficient colour contrast against the background colours used. This means it can be difficult for users with visual disabilities to read this text.

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

PDFs and other documents

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.

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

Older videos

Some of our older videos may not have captions and/or audio description. This fails:

WCAG 1.2.2 Captions (Prerecorded)
WCAG 1.2.5 Audio Description (Prerecorded)

We do not plan to make these older videos accessible because videos published before 23 September 2020 are exempt from the meeting the accessibility regulations.

YouTube video buttons

YouTube videos on the website include buttons with the accessible names 'play', 'copy' and 'more'. These button names don't make it sufficiently clear to users that the buttons relate to the YouTube video. We are unable to make the button names more specific because they are under YouTube's control and we did not pay for them or develop them ourselves.

Maps

Our maps are not accessible to screen reader users. We have ensured that essential navigational information included in maps, such as addresses or directions, are available in an accessible format.

Preparation of this accessibility statement

This statement was prepared on 22 September 2020. It was last updated on 3 January 2025.

We migrated this website to a different content management system (CMS) in April 2024. We have updated this statement to reflect how this has improved the accessibility of the website. We have development work planned to address many of the remaining system-related issues. We aim to have addressed these by the time we reaudit the website. We aim to have reaudited the website and updated this statement to reflect that by January 2025.

The website was last audited in February 2023. Norfolk County Council's Digital Customer Experience Team carried out the test.

We tested the website using automated and manual tests. We used:

Accessibility Insights for Web browser extension
Web Developer browser extension
Nu HTML Checker
WebAim.org contrast checker

We used a sample-based approach to auditing, based on the Website Accessibility Conformance Evaluation Methodology (WCAG-EM).