Accessibility statement for Lets Go! South Norfolk and Broadland

This accessibility statement applies to https://yes-lets-go.org.uk/. This website is run by South Norfolk and Broadland Councils.

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 using browser or device settings
  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using a keyboard or speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • Some map filters and map areas are difficult or not possible to use with a keyboard only.
  • Keyboard focus is not always easy to see, especially within maps.
  • Some links and buttons do not have clear or meaningful names, including repeated “read more” links.
  • Some images are missing alternative text.
  • Some pages have heading structure issues, including skipped heading levels or pages that do not start with a level 1 heading.
  • Some text and controls do not reflow or resize correctly when users increase text size or zoom.
  • Some blue text on a white background does not meet minimum colour contrast requirements.
  • The skip to main content link is present in code but does not appear or work when users tab through content.
  • Search is not visible and there is no sitemap in the footer, so there is not always more than one way to find content.
  • Some technical names, roles, values and ARIA landmarks need review so assistive technologies can understand the page structure.

Feedback and contact information

If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact us by: 

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

 

We’ll consider your request and get back to you in 10 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

South Norfolk and Broadland Councils are committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance status

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

  • Images and text alternatives: Some non-decorative images are missing alternative text. This may make content unavailable to screen reader users or people who need text to adapt to their settings.
    Fails: WCAG 1.1.1 Non-text Content; WCAG 1.4.5 Images of Text.
  • Links, buttons and labels: Some links, buttons and controls do not have clear names. This includes links without a text alternative, repeated “read more” buttons, and controls where the visible label and accessible name do not match.
    Fails: WCAG 2.4.4 Link Purpose; WCAG 2.5.3 Label in Name; WCAG 4.1.2 Name, Role, Value.
  • Keyboard access and focus: Some map filters cannot be used with a keyboard only. Keyboard focus is not always visible within maps and users may find it difficult to move away from map components.
    Fails: WCAG 2.1.1 Keyboard; WCAG 2.1.2 No Keyboard Trap; WCAG 2.4.7 Focus Visible.
  • Page structure and headings: Some headings skip levels, some pages may not start with a level 1 heading, and some containers or headings are empty. This can make it harder for assistive technology users to understand page structure.
    Fails: WCAG 1.3.1 Info and Relationships; WCAG 2.4.2 Page Titled.
  • Colour contrast: Blue text and buttons on a white background do not meet the minimum contrast ratio. Our recent audit recorded a contrast ratio of 3.59:1 where 4.5:1 is required.
    Fails: WCAG 1.4.3 Contrast Minimum.
  • Text resize and reflow: Some map filters and page areas are difficult to use when text is resized or displayed at narrow widths. Content can detach from maps, overlap other content, or fail to adapt when text size is increased.
    Fails: WCAG 1.4.4 Resize Text; WCAG 1.4.10 Reflow.
  • Bypass blocks: The skip to main content link is in the code but does not appear or work when users tab through the page.
    Fails: WCAG 2.4.1 Bypass Blocks.
  • Instructions and input methods: Some content refers to “simply click”, which relies on a specific input method and may not be suitable for keyboard, voice control or screen reader users.
    Fails: WCAG 1.3.3 Sensory Characteristics.
  • ARIA, landmarks and technical semantics: Some content is not contained within appropriate landmarks, some container elements are empty, and some inline frames are missing a text alternative. This may make navigation harder for assistive technology users.
    Fails: WCAG 1.3.1 Info and Relationships; WCAG 4.1.2 Name, Role, Value; WAI-ARIA authoring practices.

Disproportionate burden

We are not currently claiming that any of the issues listed above are a disproportionate burden to fix. We will update this statement if that changes after further assessment.

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

Third‑party content that we do not control is out of scope. This includes widgets within the site that cannot be changed by our developer.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services. Any new PDFs or Word documents we publish will meet accessibility standards.

We are also not required to fix third-party content that is not funded, developed by or under the control of South Norfolk and Broadland Councils.

The audit recorded that there were no videos on the site, so captions and audio descriptions were not applicable at the time of testing.

What we’re doing to improve accessibility

We are working through the issues identified in the most recent accessibility audit and aim to have fixes implemented by the time we complete our next annual audit.

We will continue to monitor our progress with Siteimprove and manual accessibility checks to help update this statement following the annual audit cycle.

Preparation of this accessibility statement

This statement was prepared on 9 July 2026. It was last reviewed on 21 July 2026.

This website was last tested on 9 June 2026 to assess it against WCAG 2.2 Level A and Level AA, WAI-ARIA authoring practices and accessibility best practices. The test was carried out by the Digital Customer Experience and Accessibility Officer at South Norfolk and Broadland Councils.

The assessment included:

  • a semi-automated Siteimprove review to identify site-wide issues
  • manual accessibility checks to monitor compliance and inform this statement
  • keyboard navigation checks
  • screen reader sampling using NVDA