norfolkcc.cmis.uk.com/norfolkcc accessibility statement

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

This website is run by Norfolk County Council. It is built and maintained by a third party supplier on our behalf.

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 2.1 at AA level.

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

• Some interactive components, including tables, tabs, date pickers, forms and the calendar of meetings, cannot be accurately identified or fully navigated using a screen reader and/or just a keyboard. Reading order and focus is sometimes not in a meaningful order
• Some components including date pickers, tabs, forms, profile photo links and parts of the website footer use colour as the only way to convey meaning and/or do not use colour combinations that have sufficient contrast
• Some error messages associated with forms and/or text inputs are not sufficiently described by text and/or accessible using assistive technologies
• Some content on some pages is not responsive and/or visible when browser zoom or text spacing adjustments have been made.
• Some pages have link text that does not sufficiently describe the link
• Landmark roles are misapplied on website pages and headings are used incorrectly in some places, which can make pages hard to navigate when using a screen reader
• Several pages do not provide multiple ways to navigate to other internal pages - only direct links
• Inconsistent breadcrumb links and inaccurate page titles could confuse users who use them to navigate or identify the page they are on
• Some pages have images that are decorative but are coded as meaningful, making the pages harder to navigate using a screen reader
• Users are logged out if they are logged in to their user account and leave a page inactive for a period. They are not given the option to turn off, adjust or extend the time limit
• Many PDF documents are not fully accessible to screen reader software

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, contact us at committees@norfolk.gov.uk

We aim to respond to email enquiries within three 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 committees@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

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.

Contact us to ask about your visit.

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 and exemptions listed below.

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. We are working with our supplier to address and fix these issues.

Non compliance with the accessibility regulations

Landmark roles are misapplied on the site template

The site template incorrectly uses the landmark role 'main'. There are two 'main' landmarks - there should only be one. The 'main' landmark should be reserved for indicating the primary content of the page. One is correct as it wraps all of the page's primary content, the other is incorrect as it wraps the entire page and contains blocks of content that repeat across pages.

This fails WCAG 1.3.1 Info and Relationships.

We expect to fix this by May 2024.

Colour

1. The Facebook and Twitter links in footer (text and logos) in hover state do not meet colour contrast requirements
2. Profile photo links do not meet colour contrast requirements 

These fail WCAG 1.4.11 Non-text Contrast.

We expect to fix this by May 2024.

Headings

Multiple pages have text that looks like and functions as a heading, but is not coded as a heading. Some pages have headings with a programmatic level that does not match the level that's presented visually. Heading use is sometimes inconsistent and should be improved to benefit users who use headings to identify key content relevant to them.

This fails WCAG 1.3.1 Info and Relationships and WCAG 2.4.6 Headings and Labels.

We expect to fix this by May 2024.

Only one way to navigate to content

Most pages only provide direct links for users to user to navigate to other pages. The services link list, sitemap and search function all refer to www.norfolk.gov.uk not www.norfolkcc.cmis.uk.com/norfolkcc/ so users can't use them to access CMIS pages.

This fails WCAG 2.4.5 Multiple Ways.

We expect to fix this by May 2024.

Images are not marked up properly

Profile pictures of councillors are marked as meaningful. Where they are not part of a link they should be decorative as they don't add any relevant information to the page.

This fails WCAG 1.1.1 Text Alternatives.

We expect to fix this by May 2024.

Page titles

Some pages have the same page title, meaning that they do not describe the page's unique topic or purpose.

This fails WCAG 2.4.2 Page Titled.

We expect to fix this by May 2024.

Some content is not adaptable

1. At display resolution 1280 x 1024 and 400% browser page zoom, the presence of at least one horizonal scroll bar prompts users to scroll horizontally as well as vertically. In some cases, users must do this to see all content. In some cases, text isn't sufficiently visible because it is clipped or overlapping.
   This fails WCAG 1.4.10 Reflow.
2. At display resolution 1280 x 1024 and 200% browser page zoom, some of the meeting information text on the Calendar of Meetings page is clipped and therefore not fully visible.
   This fails WCAG 1.4.4 Resize text.
3. Certain text doesn't respond to text spacing adjustments adequately:
   1. H1s - letter spacing (tracking)
   2. H2s in the footer on all pages, and in the main page content on some pages - letter spacing (tracking)
   3. 'k' in 'Facebook' text in footer is clipped
   4. Main page content - line height (line spacing)
   5. Teal buttons on most pages - letter spacing (tracking) and word spacing
   6. Text in columns on councillor details pages
   7. Meeting information text is clipped on Calendar of Meetings page

This fails WCAG 1.4.12 Text Spacing.

We expect to fix this by May 2024.

Repetitive content

Breadcrumb links are inconsistently featured. Some pages include a link for the page the user is on, and some do not.

This fails WCAG 3.2.4 Consistent Identification.

We expect to fix this by May 2024.

Timed events

Timeout occurs if the user is logged in and leaves a page inactive for a period. This logs the user out and displays an error message. The user is not given the option to turn off, adjust or extend the time limit.

This fails WCAG 2.2.1 Timing Adjustable.

We expect to fix this by May 2024.

Sequence

When pages are linearized, 'Petitions Login' and 'Petitions Registration' links are hard to read and use.

This fails WCAG 1.3.2 Meaningful Sequence.

We expect to fix this by May 2024.

Links

1. Some links in the header and footer may confuse the user as it's not clear whether they take them to content on www.norfolk.gov.uk or content on CMIS.
2. Several pages have empty links just before text headings in main page content
3. Letter links on the Councillors page aren't descriptive enough
4. Profile photo links (alt text) aren't descriptive enough or helpful to users
5. The 'View' button on councillors details pages isn't descriptive enough

This fails WCAG 2.4.4 Link Purpose (In Context).

We expect to fix this by May 2024.

Data tables

We expect to fix these issues by May 2024.

Sort function

In tables with a sort function:

1. It is not visually clear that clicking on the column header text will sort the table data by that specific information, nor whether it is ascending or descending. When the sort function has been activated, it's not visually clear that this is what the arrow icon indicates.
   This fails WCAG 3.3.2 Labels or Instructions.
2. The arrow icon is intended to communicate visually when table data is being ordered by date in that column in ascending or descending order. This information is not available to users who can't see the arrow icon.
   This fails WCAG 1.3.1 Info and Relationships.

Structure and layout of table pagination

Data tables have a series of pagination links if the table shows more than 10 items. Following the links allows users to see the other items in the list.

1. There is nothing in the page's code to identify these links as navigation for the table.
2. The links used do not provide enough information to let users know what will happen when clicking the links.

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

ARIA use

1. Several pages have data tables that have a <tr> element that has the ARIA role 'presentation'. This role should only be used for layout tables.
   This fails WCAG 1.3.1 Info and Relationships.
2. Tables are part of grids that are coded 'aria-readonly'. Grids that do not provide editing functions should not include the aria-readonly attribute on any of their elements. The presence of the attribute could be confusing because it implies that editing functionality is present but disabled. Grids also do not have the appropriate aria-sort and aria-selected roles.
   This fails WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value.
3. The meetings table on the Audit Committee page does not contain the right parent or child ARIA roles. There is also a grammar mistake in the aria label.
   This fails WCAG 1.3.1 Info and Relationships.

Keyboard

Tables are part of grids that do not support the keyboard interaction specified by their design pattern.

This fails WCAG 2.1.1 Keyboard and WCAF 2.1.2 No Keyboard Trap.

Focus

Activating a table pagination link moves focus back to the beginning of the page instead of to the revealed content.

This fails WCAG 2.4.3 Focus Order.

Sequence

When the Councillors page is linearized, table content is not in the correct reading order.

This fails WCAG 1.3.2 Meaningful Sequence.

Tabs

We expect to fix these issues by May 2024.

ARIA use

Tab list and panels to do not have an ARIA widget role. Tab list and panels resemble tabs, but do not support the ARIA roles, states, and properties specified by the tabs design pattern.

This fails WCAG 1.3.1 and WCAG 4.1.2 Name, Role, Value.

Keyboard

Tab lists and panels resemble tabs but do not support the keyboard interaction specified by their design pattern. Users can't navigate away from the tab if the panel contains interactive interface components.

This fails WCAG 2.1.1 Keyboard and WCAF 2.1.2 No Keyboard Trap.

Labels and instructions

The visible labels in tab lists aren't sufficiently programmatically determinable. They also don't have a label and/or instructions that identify the expected input sufficiently.

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

Colour

Where tab panels are used, visual information that indicates a tab is in focus and selected states respectively does not meet contrast requirements.

This fails WCAG 1.4.11 Non-text contrast.

Date picker

We expect to fix these issues by May 2024.

ARIA use

Date pickers have the role 'grid' - 'dialogue' would be a more appropriate role and design pattern. It does not support the ARIA roles, states and properties specified by the dialogue design pattern.
This fails WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value.

Keyboard

Date pickers resemble dialogues but do not support the keyboard interaction specified by their design pattern. Users can't navigate to and away from all parts of the date picker.
This fails WCAG 2.1.1 Keyboard and WCAF 2.1.2 No Keyboard Trap.

Focus

Date pickers do not receive focus in an order that preserves meaning and operability.

This fails WCAG 2.4.3 focus order

Labels and instructions

There needs to be more information associated with the button that opens the date picker to make it clear:

• What the tool relates to eg. picking a start/end date for the meetings filter
• Once the date picker is open, the user needs to select a date
• What they need to do after picking the date

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

Colour

In some cases, when the calendar icon is selected and when the date picker is open, visual information showing this does not contrast sufficiently with adjacent colours, and the light blue focus indicator on date numbers does not contrast sufficiently with white background colour.

This fails WCAG 1.4.11 Non-text contrast.

Semantics

The calendar icon identifying the date picker and the four arrow icons within the date picker are meaningful but the information they convey is not visible on the page when CSS is disabled.

This fails WCAG 1.3.1 Info and Relationships.

GovMetric widget issues

We expect to fix these issues by May 2024.

ARIA use

The GovMetric widget does not have an ARIA widget role or support the ARIA roles, states, and properties specified by its design pattern.

This fails WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value.

Keyboard

The GovMetric widget does not have an ARIA widget role or support the keyboard interaction specified by its design pattern.

This fails WCAG 2.1.1 Keyboard.

Labels and instructions

Visual text and coded information (link and image title and alt text) need to be clearer in order to convey label and instructions effectively. It needs to be programmatically clearer that the icons are a group of three options that relate to the text question.

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

Colour

In normal state, the GovMetric icons don't meet colour contrast requirements.

This fails WCAG 1.4.11 Non-text contrast.

Forms and text fields

We expect to fix these issues by May 2024.

Aria use

The form on the Petitions registration page does not have an ARIA widget role and isn't accurately programmatically identifiable as a form.

This fails WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value.

Focus

If a form is completed incorrectly, focus is moved to the beginning of the page instead of the (first) field where an error has occurred.

This fails WCAG 2.4.3 Focus Order.

Labels and instructions

The accessible names of the form fields on the Petitions registration page do not all include an exact match of visible text labels. Naming is also inconsistent. The checkbox is also incorrectly identified as a textbox. Required fields need to be identified as required in a programmatically determinable way.

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

Autocomplete

Input fields on the Petitions registration page do not have an autocomplete attribute.

This fails WCAG 1.3.5 Identify Input Purpose.

Errors

1. When invalid data is entered into some date field filters by typing, the error is identified when the user tabs or clicks away through either a change in colour and appearance of an icon; or an asterisk next to the field(s). But the error is not described in text. Text describing the error is not available until the user triggers the 'Submit' button
   This fails WCAG 3.3.1 Error Identification.
2. Input error associated with some date field filters is shown in visible text but not programmatically determinable by assistive technologies.
   This fails WCAG 4.1.3 Status Messages.
3. Error alerts on the Petitions registration page are not programmatically determinable by assistive technologies.
   This fails WCAG 4.1.3 Status Messages.

Required fields

On the Petitions registration page, colour is used as the only visual means of identifying essential fields. This information is not available to assistive technologies.

This fails WCAG 1.4.1 Use of Colour and WCAG 1.3.1 Info and Relationships.

Checkbox

1. On the Petitions registration page, the checkbox has an image marked as meaningful, but it does not convey any meaning so should be marked as decorative. The alt text is 'checkbox', but the image does not show a checkbox.
   This fails WCAG 1.1.1 Non-text Content.
2. The checkbox image does not meet contrast requirements for images coded as meaningful. The checkbox does not meet colour contrast requirements when in focus state.
   This fails WCAG 1.4.11 Non-text Contrast.

Colour

Form text fields on the Petitions registration page do not pass colour contrast requirements in normal or hover state.

This fails WCAG 1.4.11 Non-text Contrast.

Calendar on Calendar of Meetings page

We expect to fix these issues by May 2024.

ARIA use

The calendar does not have an ARIA widget role. It resembles a grid but does not support the ARIA roles, states, and properties specified by the grid design pattern.

This fails WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value.

Keyboard and focus

A user can't navigate to the calendar component or within most of it using a keyboard. The calendar resembles a grid but does not support the keyboard interaction specified by the grid design pattern.

This also means that components do not receive focus in an order that preserves meaning and operability.

This fails WCAG 2.1.1 Keyboard and WCAG 2.4.3 Focus order.

Labels and instructions

The visible labels in the navigation bar at the top of the calendar (2 arrow icons, 'today', calendar icon and date text) aren't sufficiently programmatically determinable. They also don't have a label and/or instructions that identify the expected input sufficiently.

This fails WCAG 1.3.1 Info and Relationships, and WCAG 2.5.3 Label in Name.

Links

The meaning and purpose of the calendar date number links is not visually or programmatically clear enough.

This fails WCAG 2.4.4 Link Purpose (In Context)

Semantics

The two arrow icons at the top of the calendar (on the 'previous day' and 'next day' buttons) are meaningful but the information they convey is not visible on the page when CSS is disabled

This fails WCAG 1.3.1 Info and Relationships.

Sequence

When the Calendar of meetings page is linearized, the days of the week are not displayed in the correct reading order.

This fails WCAG 1.3.2 Meaningful Sequence.

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.

This fails WCAG 4.1.2 Name, Role Value.

We are currently working to improve document creation processes to make sure that new documents we add to the website are accessible.

Disproportionate burden

We are not claiming disproportionate burden on this site.

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

Older PDFs and other documents

Many of our older PDFs do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

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.

Preparation of this accessibility statement

This statement was prepared on 9 October 2023. It was last reviewed on 9 October 2023.

This website was last tested on 23 June 2022. Norfolk County Council's Digital 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).