norfolkcc.cmis.uk.com/norfolkcc accessibility statement

Introduction

This accessibility statement applies to www.norfolkcc.cmis.uk.com/norfolkcc/.

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
Zoom in up to 400% without the text spilling off the screen and without content being truncated or overlapping
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)

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.

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

Some non-interactive components can be navigated to using a keyboard
The main landmark role has been used incorrectly
Some landmark roles have unclear labels
Some text that visually acts a heading, is not programmatically coded as a heading
Some headings are visually presented the same, despite being different heading levels
Some headings do not follow the correct heading structure
There are links that do not operate as links
Some links do not have clear link text to describe their purpose or where they go
Some links have visible text labels that do not exactly match their accessible name
There are some grid tables that have unclear accessible names
Some error messages do not clearly describe the error or the form field with the error using text
Some error messages do not sit within the correct container to tell assistive technology, such as screen readers, that the message is an alert
Some page titles do not clearly describe the page's content
Some images of text have alternative text that does not exactly match the text in the images
Some images have alternative text that does not clearly describe the image
Colour is used as the only way to convey state changes for some components
Some content is hidden when the webpage is zoomed in
Some text does not respond to text spacing adjustments
Some content overlaps when text spacing is adjusted
Some components do not have accessible colour contrast when in different states
Some PDFs are not fully accessible to assistive technologies

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 [email protected].

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, email [email protected].

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

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

Primary content

On all webpages, there are 2 'main' landmarks. There should only be one. One of the main landmarks covers the entire webpage. This is the incorrect use of the main landmark role. It also includes content that is repeated across multiple pages, which it should not.

This fails WCAG 1.3.1 and WCAG 2.4.1.

Link purpose

On all webpages, the link text/accessible name for the link behind the Norfolk County Council logo does not clearly describe the purpose of the link and where it takes the user. The accessible name is 'NCC logo'. The acronym is not explained in full words and therefore may be unclear to users who do not know what it stands for. The accessible name does not make it clear where the link goes - Norfolk County Council website.

This fails WCAG 2.4.4.

Label in name

On all webpages, the accessible name (skip to content navigation link) for the bypass mechanism link does not contain an exact match to visible text (skip to main content).

This fails WCAG 2.5.3.

Text alternative

On all webpages:

The 'NCC logo' contains text. The alt text should exactly match the text in the image (Norfolk County Council).
The Intran logo contains text. The alt text should exactly match the text in the image. (Intran communication for all).
The alt text for the govmetric faces could be clearer. For example, they should include what it is the user is rating i.e. 'Rate this page as Good'.

This fails WCAG 1.1.1.

Colour as meaning

On all webpages:

The Norfolk County Council logo goes from having a white background to an orange background from normal to hover state, normal to tabbed state and hover to selected state. The orange and white do not have accessible colour contrast.
The 'Search' link goes from black underlined text on a white background to black underlined text on an orange background when going from a hover to selected state. The orange and white do not have accessible colour contrast.
The links in the grey menu bar go from black underlined text on a grey background to black underlined text on an orange background when going from a hover to selected state. The orange and grey do not have accessible colour contrast.
The GovMetric links go from black text with blue underline on a white background to black text with a black underline on an orange background when going from hover to selected state. The blue to black and white to orange do not have accessible colour contrasts.
The footer links go from dark grey text on a light grey background to black text on an orange background when going from a hover to selected state. The dark grey to black and light grey to orange do not have accessible colour contrasts.
The Intran logo goes from black on a grey background to black on an orange background when going from normal to tabbed and hover to selected states. The grey to orange does not have accessible colour contrast.
The Facebook and Twitter links and logos go from being on a grey background to being on an orange background hen going from a hover to selected state. The grey to orange does not have accessible colour contrast.

On the CMIS homepage:

The link text in the cards goes from teal to blue on a white background when going from a normal to hover state. The teal and blue do not have accessible colour contrast.
The link text in the cards goes from teal underlined text on a white background to black text with a blue underline on an orange background. The teal to blue and the white to orange do not have accessible colour contrasts.

On the Cabinet webpage:

The 'open the calendar pop up' button icon goes from light blue on a grey background to darker blue on a grey background when going from normal to hover state. The light and dark blue do not have accessible colour contrast.
The 'open the calendar pop up' button icon goes from blue on a grey background to black on a yellow background when going from normal to tab state. The blue to black does not have accessible colour contrast and the grey to yellow do not have accessible colour contrast.
The calendar icon in the grid table goes from being on a white background to being on a yellow background with blue underline when going from normal to tab state. The white and yellow backgrounds do not have an accessible colour contrast and blue underline and yellow background do not have accessible colour contrast.
The calendar icon in the grid table goes from being on a white background with a blue underline to being on a yellow background with blue underline when going from hover to select state. The white and yellow backgrounds do not have an accessible colour contrast.
The linked text (numbers 1 to 9) below the grid table go from blue text on a grey background to black text on a yellow background when going from normal to tab state. The blue and black text does not have accessible colour contrast and the grey and yellow backgrounds do not have accessible colour contrast.
The linked text below the grid table go from white text on a dark green background to white text on a dark green background with a yellow outline. The yellow outline against the grey background does not have accessible colour contrast.
The check box goes from being a light grey box on a white background to a darker grey box on a white background when going from normal to hover state. It also goes from being a dark grey box on a white background to a lighter grey box on a white background when going from hover to select state. The light and dark grey do not have accessible colour contrast.

On the Councilors webpage:

The letter links (A, B, C etc) go from blue text on a grey background to black text with a blue underline on a yellow background when going from a normal to tabbed state and a hover to a selected state. The blue to black and the grey to yellow do not have accessible colour contrast. The blue underline also does not have accessible colour contrast against the yellow background.
The images gain a yellow outline when going from normal to tabbed state and hover to selected state. The yellow outline does not have accessible colour contrast against the white background.
The 'Back to the Top' links go from black text on a white background to black text with a blue underline on a yellow background when going from a normal to tabbed state. The white and yellow do not have accessible colour contrast. The blue underline also does not have accessible colour contrast against the yellow background.
The 'Back to the Top' links go from black text with a blue underline on a white background to black text with a blue underline on a yellow background. The white and yellow do not have accessible colour contrast.

On the Cabinet and Councilors webpages:

The buttons ('Submit', 'View Committees List' and '9') go from white text on a teal background to black text on a yellow background when going from normal to tab state. The teal and yellow do not have accessible colour contrast.
The 'Enter a Date' text box goes from being a grey box on a white background to a teal box on a white background when going from normal to hover state. The grey and teal do not have accessible colour contrast.

On the Committees, Cabinet and Councilors webpages:

The text links go from blue text on a white background to black text with a blue underline on an orange background from a normal to tabbed state. The blue to black and the white to orange do not have accessible colour contrast.
The text links go from light blue underlined text on a white background to black text with a blue underline on an orange background from a hover to selected state. The light blue to black and the white to orange do not have accessible colour contrast.

This fails WCAG 1.4.1.

Keyboard navigation

On the Cabinet webpage, you can tab to the date picker forms (for Meetings and Members), even though they are not interactive. Users should only be able to tab to interactive interfaces.

This fails WCAG 2.1.1.

Landmark roles

On the Cabinet webpage, there are two navigation landmarks. One is for the date picker forms (on 'Meetings' and 'Members'). It has the label: "press tab once more to focus the meeting from date". The label text does not clearly describe the content in the landmark.

This fails WCAG 1.3.1.

No missing headings

On the Committees webpage:

There is text that acts as a heading but has not been programmatically coded as a heading.
There is text that acts as a heading and has been visually styled as a heading (emboldened). This text has not been programmatically styled as a heading.

This fails WCAG 1.3.1 and WCAG 2.4.6.

Heading level

On the Cabinet webpage, the heading 2s ('Meetings', 'Members' and 'Other Information') are the same font size (32) as the heading 1 ('Cabinet').

On the Committees webpage, the headings that have been programmatically styled as headings do not follow the correct heading structure. For example, there are three heading 1s - there should only ever be one heading 1. For example, 'Committees' should be the only heading 1. 'Current Committees' should be a heading 2. 'Norfolk County Council' should be a heading 3. 'Internal Committees and Outside Bodies' should be a heading 2.

On the Councilors webpage, the headings do not follow the correct heading structure. There are two heading 1s - there should only ever be one heading 1. For example, 'Councillors' should be the only heading 1 and 'Elected Members' should be a heading 2.

This fails WCAG 1.3.1.

Link function

On the CMIS homepage, there is a link in the code that does not function as a link.

On the Committees webpage, there are links in the code that do not function as links.

On the Councilors webpage:

There are links in the code that do not function as links
There are some letters that are coded as links but do not operate as links (I Q U X Y Z)

This fails WCAG 4.1.2.

Design pattern

On the Cabinet webpage, the tab widget acts as a tab but it is not coded as a tab. For example, the element that serves as the container for the set of tabs does not have 'role=tablist'.

This fails WCAG 4.1.2.

Expected input

On the Cabinet webpage, the accessible name for the two grid tables ("Grid table view level . Contains flat or hierarchical data") does not clearly describe the content.

This fails WCAG 3.3.2.

Error identification

On the Councilors webpage, when entering an incorrect value into the 'enter a date' text box, it triggers automatic error detection. The field with the error and the error itself is not described in text - it is only identified by the text box and the text turning red.

This fails WCAG 3.3.1.

Status messages

On the Cabinet webpage, there is no empty container with 'alert' attribute for the error message.

This fails WCAG 4.1.3.

Page title

The page title for the homepage is 'CMIS'. This does not clearly identify that this website is specific to Norfolk.

This fails WCAG 2.4.2.

Resize text

On the Cabinet webpage, when the webpage is viewed at 200% zoom, some text in the date form fields is clipped, meaning that the whole year is not fully visible. For example, when longer dates are displayed such as those in September.

This fails WCAG 1.4.4.

Reflow

On the Cabinet webpage, when the webpage is viewed at 400% zoom, some text in the date form fields is clipped, meaning that the whole year is not fully visible. For example, when longer dates are displayed such as those in September.

On the Councilors webpage, when viewed at a display resolution of 1280 x 1024 at a 400% zoom with the browser set to full-screen mode, a lot of text overlaps.

This WCAG 1.4.10.

Text spacing

On the CMIS homepage, the link text in the cards does not respond to text spacing changes.

On the Councilors webpage, there is some overlapping with text and images (the political party logos) when the text spacing is increased.

This fails WCAG 1.4.12.

State Changes

On the Councilors webpage, when the images are in a tabbed or selected state they have a yellow outline. The yellow outline does not have accessible colour contrast against the white background (1.64).

On the Councilors and Cabinet webpages:

When the buttons ('Submit', 'View Committees List' and '9') are in a selected state, they display with black underlined text on a teal background with a yellow outline. The black text against the teal background does not have accessible colour contrast.
When the 'Enter a Date' text box is in a normal state it has black text in a grey text box on a white background. The grey textbox against the white background does not have accessible colour contrast.
When the 'Enter a Date' text box is in a hover state it has black text in a teal text box on a white background. The teal textbox against the white background does not have accessible colour contrast.
When the 'Enter a Date' text box is in a tabbed or selected state it has white text in a teal text box on a blue background. The white text against the blue background does not have accessible colour contrast and the teal textbox against the white background does not have accessible colour contrast.

This fails WCAG 1.4.11.

PDFs

Many PDFs on the website do not meet accessibility standards. For example:

They may not be structured so they're accessible to a screen reader
Information is communicated by the way content is visible formatted. It is not always also communicated in a way assistive technologies can understand.

This fails WCAG 2.4.2 and WCAG 1.3.1.

The content is not within the scope of the accessibility regulations

Older documents

Many of our older documents do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This fails WCAG 4.1.2 Name, role, value.

The accessibility regulations do not require us to fix documents published before 23 September 2018 if they're not essential to providing our services.

Any new documents we publish will meet accessibility standards.

Preparation of this accessibility statement

This statement was prepared on 23 September 2025. The statement was last reviewed on 7 October 2025.

This website was last tested in September 2025. Norfolk County Council's Digital Customer Experience Team carried out the test.

We tested the website www.norfolkcc.cmis.uk.com/norfolkcc/ using automated and manual tests. We used:

Accessibility Insights for Web browser extension
Browser developer tools
Web Developer browser extension
Stylus browser extension
Colourcontrast.cc browser extension

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