Toggle mobile menu visibility

Accessibility statement for buslanepayments.norfolk.gov.uk

This accessibility statement applies to the Penalty Charge Notice 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:

  • Keyboard users are not able to navigate to some buttons or parts of forms
  • Some pages have poor colour contrast
  • The payment form does not enable users to enter their personal details using autocomplete
  • Some page titles do not clearly and accurately describe the page
  • The 'Skip to content' link on all pages does not direct users to the main content on the page
  • Some tables and bold text are not formatted correctly, meaning that assistive technology users may find it difficult to understand them
  • It may not be clear to assistive technology users which form fields must be completed (are required)
  • Some text headings do not have the correct programmatic heading levels

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 via email at MTE@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 us at MTE@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

The content listed below is non-accessible for the following reason(s):

Non compliance with the accessibility regulations

Bypass blocks on all pages (excludes ChallengeSmarti appeals pages and ConnectPay payment pages)

If you use the tab key to activate the 'Skip to content' section it uses #main but this location is not set on the page for it to skip to. This fails WCAG 2.4.1 Bypass blocks: A page must provide a keyboard-accessible method to bypass repetitive content.

Semantics emphasis on all pages (excludes ChallengeSmarti appeals pages and ConnectPay payment pages)

Table 'titles' are bold (set by CSS) but are not contained within an <em> or <strong> element and are not set as table headers. This fails WCAG 1.3.1 Emphasis: Words and phrases that are visually emphasized must be contained within semantically correct containers.

Instructions on the Login page

The inputs to 'Vehicle registration number' and 'Penalty Charge Notice' are required but it does not state that programmatically in the accessible description. This fails WCAG 1.3.1 and WCAG 2.5.3 Instructions: If a native widget has a visible label or instructions, they must be programmatically determinable.

Cues on the Login page

The input fields for 'Vehicle registration number' and 'Penalty Charge Notice' are required but they do not say they are in the HTML. This fails WCAG 1.3.1 and WCAG 4.1.2 Cues: If a native widget adopts certain interactive states, it must provide appropriate cues.

Page title on the Login page

The page title is 'ICES 3sixty Citizen - Penalty Charge Notice search', which makes it hard to understand if you're on the right page. This fails WCAG 2.4.2 Page title: A web page must have a title that describes its topic or purpose.

Page title on the Ticket details page

The page title of 'ICES 3sixty Citizen - Penalty Charge Notice details' contains references to 'ICES 3sixty Citizen', which a user would not understand. This fails WCAG 2.4.2 Page title: A web page must have a title that describes its topic or purpose.

Semantics emphasis on the Payment outstanding page

Table 'titles' are bold (set by CSS) but are not contained within an <em> or <strong> element and are not set as table headers. This fails WCAG 1.3.1 Emphasis: Words and phrases that are visually emphasized must be contained within semantically correct containers.

Semantics emphasis on the Important notice page

The text 'do not' uses a <b> instead of <em> or <strong> which fails the emphasis criteria. This fails WCAG 1.3.1 Emphasis: Words and phrases that are visually emphasized must be contained within semantically correct containers.

Heading function on the Connect Pay details (billing, card) page

The ticket ID number in the 'Your Order' section uses an H6 tag but it shouldn't be a heading. This fails WCAG 1.3.1, WCAG 2.4.6 Heading function: An element coded as a heading must function as a heading.

Heading level on the Connect Pay details (billing, card) page

In the 'Your Order' and 'Billing Address' sections, the main titles are <h4> and not an <h1>. This fails WCAG 1.3.1 Heading level: A heading's programmatic level must match the level that's presented visually.

Link function on the Connect Pay details (billing, card) page

The 'ConnectPay' logo is wrapped in Anchor <a> tags but it does not link anywhere. This fails WCAG 4.1.2 Link function: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role.

Link purpose on the Connect Pay details (billing, card) page

The 'ConnectPay' logo is wrapped in Anchor <a> tags but it does not link anywhere. This fails WCAG 2.4.4 Link purpose: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context.

Cues on the Connect Pay details (billing, card) page

The form inputs do not contain cues that state they are 'required'. This fails WCAG 1.3.1, WCAG 4.1.2 Cues: If a native widget adopts certain interactive states, it must provide appropriate cues.

Autocomplete on the Connect Pay details (billing, card) page

None of the input fields have an autocomplete attribute, for example 'Postcode' could use 'postal-code'. This fails WCAG 1.3.5 Autocomplete: Text fields that serve certain purposes must have the correct HTML5 autocomplete attribute.

Instructions on the Connect Pay details (billing, card) page

The help badge contains instructions that are not programmatically determinable This fails WCAG 1.3.1, WCAG 2.5.3 Instructions: If a custom widget has a visible label or instructions, they must be programmatically determinable.

Status messages on the Connect Pay details (billing, card) page

The error messages do not set a role="alert". This fails WCAG 4.1.3 Status messages: Status messages must be programmatically determinable without receiving focus.

Image function on the Connect Pay details (billing, card) page

The 'ConnectPay' image is coded as meaningful but it has alt text of 'Home' and the link does not work, so so the alt text doesn't describe purpose of link. This fails WCAG 1.1.1 Image function: Every image must be coded as either meaningful or decorative.

Text alternative on the Connect Pay details (billing, card) page

The text alternative is 'Home' but it doesn't work as a home button and the alt text doesn't match the visible text. This fails WCAG 1.1.1 Text alternative: A meaningful image must have a text alternative that serves the equivalent purpose.

Contrast on the Connect Pay details (billing, card) page

The light blue on white contrast is 1.41:1 which is a fail for graphical objects and user interface components. The 1px darker boarder is 2.05:1 which is also a fail. The light grey border is also a fail with a contrast ratio of 1.49:1 (all contrast compared to a white background). This fails WCAG 1.4.11 UI components: Visual information used to identify active user interface components and their states must have sufficient contrast.

State changes on the Connect Pay details (billing, card) page

The light blue on white contrast is 1.41:1 which is a fail for Graphical objects and User Interface Components. The 1px darker boarder is 2.05:1 which is also a fail. The light grey boarder is also a fail with a contrast ratio of 1.49:1 (all contrast compared to a white background). This fails WCAG 1.4.11 State changes: Any visual information that indicates a component's state must have sufficient contrast.

Keyboard navigation on the Appeals criteria page

On the drop down menu you can't focus on 'View case summary'. This fails WCAG 2.1.1 Keyboard navigation: Users must be able to navigate to all interactive interface components using a keyboard.

Contrast minimum on the Appeals criteria page

On mobile the hover/focus on the appeals page 'menu' dropdown makes the text white so it can't be seen. This fails WCAG 1.4.3 Color-contrast: Elements must meet minimum color contrast ratio thresholds.

Aria use on the Appeals criteria page

The snippet: '.navbar-collapse <div class="navbar-collapse collapse in" aria-expanded="true" style="">' fails WCAG 4.1.2 Elements must only use allowed ARIA attributes.

Heading function on the Appeals criteria page

All titles on the page are H3 but there are no H1 or H2. This fails WCAG 1.3.1 and WCAG 2.4.6 Heading function: An element coded as a heading must function as a heading.

Page title on the Appeals criteria page

The page title is 'ChallengeSmarti', which does not relate to the fact that you are appealing a Penalty Charge Notice (PCN). This fails WCAG 2.4.2 Page title: A web page must have a title that describes its topic or purpose.

Keyboard navigation on the Appeals criteria - document upload page

The user can't tab or key to browse in the modal. This fails WCAG 2.1.1 Keyboard navigation: Users must be able to navigate to all interactive interface components using a keyboard.

Keyboard navigation on the Appeals criteria - privacy policy page

It's not possible to use a keyboard to tick the 'Please check the box to continue' check box. This fails WCAG 2.1.1 Keyboard navigation: Users must be able to navigate to all interactive interface components using a keyboard.

Preparation of this accessibility statement

This statement was prepared on 20 October 2023. This website was last tested in October 2023.

This statement was last updated on 1 November 2023.

We used a mix of automated and manual tests to check conformance to all WCAG 2.1 A and AA criteria. 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 Website Accessibility Conformance Evaluation Methodology (WCAG-EM).