Accessibility statement

This accessibility statement applies to the ICT Solutions website.

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.

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

The visual positioning of error messages on the contact us form may make it unclear to some users which field the error message applies to
The captcha challenge on the contact us form has several accessibility issues which may make the form difficult to use for some users
Some search forms have unlabelled or incorrectly labelled fields
The cookie control has several accesibility issues that may make it difficult to use for visually impaired people
Many Word documents are not fully accessible to screen reader software

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: ict@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, email webaccessibility@norfolk.gov.uk.

We'll consider your request and get back to you within 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).

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.

Technical information about this website's accessibility

Norfolk County Council is committed to making its websites 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-compliance 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.

Error identification on the Contact us page

When error messages appear to indicate that the user has not completed the contact form correctly, they are positioned above the field label. This may make it unclear to some users which field the error message applies to..

This fails WCAG 3.3.1 Error identification

Captcha challenge on the Contact us page

The captcha challenge ('I'm not a robot' checkbox) on the contact form has several accessibility issues. For example:

Sometimes users can't navigate to all buttons using a keyboard
Checking the checkbox sometimes triggers a change of context (a dialog opens). The user is not warned this is going to happen
It's not visually obvious when some components have focus
The 'Privacy', 'Terms' and 'Learn more' links are not descriptive enough
The challenge expires and errors after two minutes. The user must then tick the checkbox and complete a new challenge. They are not given the option to turn off, adjust or extend the time limit
Error messages aren't presented in an accessible way
Some text and state indicators don't contrast enough with adjacent colours
Users may have to scroll both horizontally and vertically when zoomed in
When the page is linearized, the captcha dialog is positioned after all the other page content (after the website page footer). This affects its meaning - it's no longer visually associated with the captcha checkbox

This fails:

WCAG 2.1.1 Keyboard
WCAG 3.2.2 On input
WCAG 2.4.7 Focus visible
WCAG 2.4.4 Link purpose (in context)
WCAG 2.2.1 Timing adjustable
WCAG 3.3.1 Error identification
WCAG 4.1.3 Status messages
WCAG 1.4.1 Use of colour
WCAG 1.4.3 Contrast (minimum)
WCAG 1.4.10 Reflow
WCAG 1.3.2 Meaningful sequence

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

Word documents

There are Word documents on the website that do not meet accessibility standards because they:

Do not have descriptive document titles and file names. This fails WCAG 2.4.5 Page titled
Have incorrect heading structures. This fails:
- WCAG 1.3.1 Information and relationships
- WCAG 2.4.6 Headings and labels
Include images that are not marked as decorative or given descriptive alternative text. This fails WCAG 1.1.1 Alternative text
Include tables that are not accessibly formatted. This means screen reader software will not be able to read and understand them accurately. This fails WCAG 1.3.1 Information and relationships
Have content that is only present in the document header. This means the content may not be detected or read out by screen reader software. This fails WCAG 2.4.5 Multiple ways

Date of expected fix: March 2025

Preparation of this accessibility statement

This statement was prepared on 26 October 2023.

This website was last tested in October 2023.

This statement was last updated on 03 January 2025.

We tested the ICT Solutions website using manual and automated checks on key pages and documents. We used:

Accessibility Insights for Web browser extension
Web Developer browser extension
Nu HTML Checker
contrast-ratio.com
NVDA

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