Beta

This is a new service - your feedback will help us to improve it.

Accessibility

This accessibility statement applies to https://go.walsall.gov.uk.

This website is run by Walsall 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 contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of 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)

We are working towards making 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:

  • the text will not reflow in a single column when you change the size of the browser window
  • you cannot modify the line height or spacing of text
  • many documents are in PDF format and are not fully accessible to screen reader software
  • live video streams do not have captions
  • some of our online forms are difficult to navigate using just a keyboard
  • you cannot skip to the main content when using a screen reader
  • there’s a limit to how far you can magnify the map on our ‘contact us’ page

Feedback and contact information

Tell us if you need information on this website in a different format. In your message, include:

  • the web address (URL) of the content
  • your name and email address
  • the format you need (for example, BSL, large print, accessible PDF, audio recording, easy read or braille)

We’ll consider your request and get back to you as soon as possible.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website.

We are working on our content and will continue to make this more readable. All of our pages let you provide feedback to us and we encourage you to tell us what you think. 

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, let us know via:

  • feedback buttons on pages
  • feedback button on a BETA banner at the top of the page to report how you find the look and feel and navigation of our pages
  • email: webproject@walsall.gov.uk
  • phone: +44 1922 650000
  • visitor address: Walsall Council, The Civic Centre, Walsall, WS1 1TP

We will respond to feedback within 5 working days.

Enforcement procedure

If you contact us with a complaint and you’re not happy with how we respond, contact the Equality Advisory and Support Service (EASS).

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’).

Technical information about this website’s accessibility

Walsall 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

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. 

Walsall Council 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 reasons.

Non-compliance with the accessibility regulations

PDFs and non-HTML documents

Some of our PDFs and other documents are not formatted so they’re accessible to a screen reader. Some errors may include, missing:

  1. Page titles. PDF documents should have titles that describe the topic or purpose of the page. If these are missing this doesn't meet WCAG success criteria 2.4.2.
  2. Non-text content. All non-text content presented to the user should have a text alternative that serves the equivalent purpose. If these are missing this doesn’t meet WCAG 2.1 success criterion 1.1.1
  3. Headings and labels. Headings and labels describe topic or purpose. If these are missing this doesn't meet WCAG 2.1 success criteria 2.4.6
  4. Name, role, value. For all user interface components, some of which are essential to providing our services (for example, forms published as Word documents). If these are missing this doesn’t meet WCAG 2.1 success criterion 4.1.2

Images

Some images don’t have a text alternative (alt text), so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content). When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This doesn't meet WCAG success criterion 1.4.5 (images of text). When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Broken links

On some pages the same link text is used for different link destinations. This doesn’t meet WCAG 2.1 success criterion 2.4.4 link purpose (in context). We are working on a new website that will fix these issues. When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

On some pages the purpose of each link can't be determined from the link text alone. This doesn't meet WCAG 2.1 success criterion 2.4.4 link purpose (in context). When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Tables

On some pages tables do not have a description set using the caption element. This doesn't meet WCAG 2.1 success criterion 1.3.1 info and relationships. When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Contrast

On some pages on our microsites there isn't sufficient contrast between the colour of the text and the background, making it hard to read the information. This doesn’t meet WCAG 2.1 success criterion 1.4.3 contrast (minimum). When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards. All the pages on our main website now conform to accessibility guidelines.

Language

On some pages the language has not been set in a way that can be understood by a screen reader. This doesn’t meet WCAG 2.1 success criterion 3.1.1 (language of page). When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Navigation

On some pages the tabbing order is not logical when navigating using a keyboard. This doesn’t meet WCAG 2.1 success criterion 2.4.3 focus order. When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

You cannot skip to main content when using a screen reader. This doesn’t meet WCAG 2.1 success criterion 2.4.3 focus order. When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

HTML

On some pages HTML is used to format content rather than CSS. This doesn’t meet WCAG 2.1 success criterion 1.3.1 information and relationships. When we review existing content and publish new content we’ll make sure our use of images meets accessibility standards.

Online forms

On some online forms, the questions with radiobox/checkbox answers might have missing fieldset or an orphaned form label which makes the questions and answers unavailable to people using a screen reader. This doesn't meet WCAG 2.1 AA success criterion 3.3.2 (labels or instructions) and 1.1.1 (non-text content). We are currently moving all the online forms into a different platform. When we are developing the revamped forms we will make sure all fields meet WCAG 2.1 AA accessibility standards.

Compatibility with browsers and assistive technology

For optimal performance and experience, we recommend you use the latest version of a modern browser. Microsoft Internet Explorer 11 support is deprecated. We recommend that you use Microsoft Edge.

Walsall Council website is not compatible with:

  • browsers older than Internet Explorer 8

Technical specifications

Accessibility of Walsall Council Website relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

We rely upon these technologies for conformance to accessibility standards.

My account online applications

Online applications within my Walsall account are only accessible on the most recent versions of the following browsers:

  • Microsoft Edge
  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Internet Explorer (not recommended)

If you are using an android phone, please download Google Chrome which is widely available for free on app stores.

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

PDFs and other documents

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. For example, we do not plan to fix the 2008 parking strategy (pdf).

Any new documents we publish from 1 January 2022 will be accessible.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations

What we are doing to improve accessibility

Our service areas are urgently fixing content which fails to meet the Web Content Accessibility Guidelines version 2.1AA.

We are currently undergoing a complete rewrite of our website to deliver a more inclusive online experience. The following is a list of planned activity and estimated delivery:

  • replacing our web platform: 30 September 2022
  • all web content updated: 30 September 2022
  • fix inaccessible PDFs: 30 April 2022

Testing approach

We run annual and weekly tests. We fix any issues as they are found.

Annual testing

This website is tested annually for accessibility. This is done manually and our web team test the most used customer journeys through the website and a sample of the different types of page. We test using tools such as Lighthouse and AXE.

Weekly testing

Each week we test:

  • a random sample of all new webpages published that week
  • all new documents published each week

Our tests include:

  • general accessibility testing and colour contrast checking using WAVE
  • human testing for usability
  • mobile browser retesting
  • Nitro Pro and PDF-Xchange editor to test and fix PDF documents

Preparation of this accessibility statement

This statement was prepared on 18 September 2020. It was last reviewed on 2nd February 2022.

Last updated on 2 February 2022.