Cookie Consent by PrivacyPolicies.com

Accessibility statement for Museums Norfolk

This accessibility statement applies to www.museums.norfolk.gov.uk

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.

We have run a simple accessibility audit on this site. We plan to run a more in-depth audit in 2023.

How accessible this website is

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

However, we know some parts of this website are not fully accessible:

  • Some Word documents and older PDF documents are not fully accessible to screen reader software
  • Some images do not have good alternative text, which means the information they show is not available to all users
  • The text in some elements may overlap and be harder to read when resized or when text spacing is increased
  • Some text links may be hard to see because they don’t contrast sufficiently with the background colour
  • The search filter and carousels have missing or incorrect metadata, which may make them difficult to use for screen reader users

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email webaccessibility@norfolk.gov.uk

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

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

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

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 version 2.1 AA standard, due to the non-compliances listed below.

We have run a simple accessibility audit on this site. We plan to run a more in-depth audit in 2023.

Non-accessible content

The content listed below is non-accessible for the following reasons. Each item is listed with the relevant WCAG criterion that it fails on.

Non compliance with the accessibility regulations

Images

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We are working through the site adding alternative text when we spot it is missing. When we publish new content we’ll make sure our use of images meets accessibility standards.

Overlapping text

On a few pages text can overlap when resized or when text spacing is increased. This fails WCAG 2.1 success criterion 1.4.12 (text spacing) and 1.4.10 (reflow).
We are currently fixing this issue.

Visual elements

Some of our breadcrumb links on certain pages do not have sufficient contrast, for example on this page: Join one of our friend's groups. This fails WCAG 2.1 success criterion 1.4.3 (contrast minimum).
We are currently fixing this issue.

Meta data

The filter field on the search page lacks an explicit label. This fails WCAG 2.1 success criterion 1.3.1 (meaningful relationships)

The carousel element used across the site has misapplied aria roles, which will break interactivity for screen reader users. For example the main carousel element on this page: Time and Tide Museum. This fails WCCAG 2.1 success criterion 1.3.1 (info and relationships) and 4.1.2 (name, role, value).

We are currently fixing these issues.

Word documents

There are approximately 9 Word documents that do not meet accessibility standards. For example, several 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 2.1 success criterion 1.3.1 (info and relationships) and 4.1.2 (name, role, value)

We are reviewing these documents, removing them and replacing them with accessible PDFs or web content where needed.

Date of expected fix September 2023.

Disproportionate burden

We are not claiming disproportionate burden on any part of our site.

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.

Preparation of this accessibility statement

This statement was prepared on 22 September 2020.

This website was last tested on 21 August 2020. The test was carried out by NCC staff.

The statement was last updated on 2 December 2022.

We ran a simple set of tests based on the preliminary checks suggested by the W3C. We tested against all the main templates used throughout the site. This should be enough to catch common, site-wide issues that will affect the most users. We recognise that this cannot address content related issues, for which will be running a more in-depth set of tests in 2023.