Toggle mobile menu visibility

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

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

  • There are keyboard function issues on all pages. For example:
    • The operability of the cookie control alert pop-up when you first enter the website
    • The colour contrast of the focus indicator on text and image links when navigating using a keyboard (tabbing)
  • There are keyboard function issues on specific pages. For example:
    • No visible focus indicator on some image links
    • Incorrect focus order when tabbing
  • Some pages have missing headings
  • The visual styling of some headings does not match their programmatic styling
  • For users using the website with assistive technology, such as a screen reader, there are issues with the description of the search button
  • From 175% zoom and upwards on a 1280 x 1024 display resolution, users cannot access the 'Refine your results' section on search pages by tabbing with a keyboard. Also in this view, the 'Refine your results' section overlaps some text which makes it difficult to read the text
  • The text in some elements overlaps on some pages when CSS styling is turned off
  • Mary Word documents, PDF documents and Excel spreadsheets 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 by email: ict@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 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 version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

We are aware of the following areas where our site is not currently meeting the WCAG standards. We have listed the issues according to the specific WCAG standard they are missing. We are currently working on fixes for all of these issues and, where possible, have listed an estimated date for fixing them.

Non-compliance with the accessibility regulations

The content listed below is non-accessible for the following reasons:

Search button labels on all pages

The visible label of the 'Search' button does not match its accessible name. This means that screen reader software will read out two different labels. Instructions are not consistent.

This fails:

  • WCAG 1.3.1 Information and relationships
  • WCAG 2.5.3 Label in name

Date of expected fix: 2 May 2024.

Keyboard interaction with cookie control pop-up on all pages

When the cookie control pop-up appears, keyboard users can tab to components on the page and activate them. Keyboard users should only be able to tab to the 'Cookie Controller' link, and the 'Accept all' and 'Set cookie preferences' buttons.

This fails WCAG 2.1.1 Keyboard.

Date of expected fix: 2 May 2024.

Orientation of all pages

We are unable to access the website on a mobile device, so cannot test to ensure that the website content changes orientation appropriately.

This fails WCAG 1.3.4 Orientation.

Date of expected fix: 2 January 2024.

Colour contrast of keyboard focus on all pages

When keyboard tabbing through text links and some image links, the yellow focus indicator against a white background has an inaccessible colour contrast ratio.

This fails WCAG 1.4.11 Non-text contrast.

Date of expected fix: 2 January 2024.

Order of keyboard focus on search pages

When keyboard tabbing through search pages, the 'Search' form field automatically receives focus first. The 'Skip to main content' bypass mechanism should be the first element to receive focus when keyboard tabbing.

This fails WCAG 2.4.3 Focus order.

Date of expected fix: 2 April 2024

Resize and reflow on search pages

From 175% zoom and upwards on a 1280 x 1024 display resolution, users cannot access the 'Refine your results' section on search pages by tabbing with a keyboard. Also in this view, the 'Refine your results' section sticks to the top of the browser window, meaning that it covers and obscures the page content and focus.

This fails:

  • WCAG 1.4.4 Resize text
  • WCAG 1.4.10 Reflow

Date of expected fix: 2 April 2024

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

Date of expected fix: 2 December 2024

Missing headings

Some pages have text that visually looks and operates as headings, but is not coded as headings. This means screen reader software will not detect them as headings.

This fails:

  • WCAG 1.3.1 Information and relationships
  • WCAG 2.4.5 Headings and labels

Date of expected fix: 2 April 2024

Inconsistent heading styles

The visual styling of some headings does not match their programmatic styling.

This fails WCAG 1.3.1 Information and relationships.

Positioning of content

On some pages, content such as the search button and the breadcrumb navigation list overlaps when CSS styles are turned off. This makes the content difficult to read and interact with.

This fails WCAG 1.3.2 Meaningful sequence.

Date of expected fix: 2 February 2024.

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: 2 March 2024

Excel spreadsheets

There are Excel spreadsheets 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
  • 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

Date of expected fix: 2 March 2024

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 17 January 2024.

We tested the ICT Solutions website, available at ict.ncc1-prd.gosshosted.com, 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).