Your feedback helps us to improve our website.

Translate

Accessibility statement for Walsall Leisure online membership

This accessibility statement applies to: https://www.snapdda.co.uk/Clients/walsallcouncil/walsallcouncilsnapddasignup.aspx

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 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:

  • error messages not announced to the screen reader
  • some informative icons lack appropriate text alternative
  • heading structure does not match the visual structure
  • heading levels are skipped or are not marked up semantically
  • form fields are not programmatically associated with the group label
  • fields collecting personal details do not employ autocomplete correctly
  • reflow and resize causes loss of content in one instance
  • non-text informative content has poor contrast
  • functionality is not fully accessible using keyboard
  • interactive elements lack a permanent label in some cases
  • interactive element has inappropriate label in one instance
  • current progression is not identified
  • interactive element is missing an appropriate accessible name

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.   

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

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 ( Website and Mobile applications) (No.2) Accessibility Regulations 2018 ( The 'accessibility regulations')

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 

Webpages 

  • Some images are missing alternative text and some form inputs are missing ARIA labels. This fails WCAG 2.2 success criterion 1.1.1 Non-text content. We plan to amend this by November 2025.
  • Error messages are not programmatically associated with the form fields, including input fields, radio buttons, and select comboboxes. This may prevent screen readers and other assistive technologies from accurately conveying the error information to users with disabilities. This fails WCAG 2.2 success criterion 1.3.1 Info and relationships. We plan to amend this by November 2025.
  • There are headings where the heading structure communicated to assistive technology does not match with the visual heading structure on the page. This can cause confusion for users relying on screen readers and other assistive technologies, as it disrupts the logical flow of information. This fails WCAG 2.2 success criterion 1.3.1 Info and relationships. We plan to amend this by November 2025.
  • Some headings have not been semantically marked up. This can confuse users relying on screen readers. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan to correct this by November 2025.
  • Some form fields, including input fields, input fields, radio buttons, and select comboboxes. This can make it difficult for screen readers to convey the correct information to users. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan to correct this by November 2025.
  • Some form field inputs do not have an auto-complete feature. This makes it harder for users to fill out the field, especially for users with cognitive impairments. This fails WCAG 2.2 success criterion 1.3.5 Identify input purpose. We plan to amend this by November 2025.
  • There is an instance where content is partially lost on zoom when viewed at high browser magnification, which means people with visual impairments may be unable to access some content. This fails WCAG 2.2 success criterion 1.4.4 Resize Text. We plan to amend this by November 2025.
  • There is an instance where content is partially lost on reflow when viewed at high browser magnification, which means people with visual impairments may be unable to access some content. This fails WCAG 2.2 success criterion 1.4.10 Reflow. We plan to amend this by November 2025.
  • There is an instance where non-text informative content has poor contrast ratio. This can make it difficult for users with visual impairments to perceive the non-text informative content. This fails WCAG 2.2 success criterion 1.4.11 Non text contrast. We plan to amend this by November 2025.
  • Not all page functionality is available to keyboard only users, this may affect blind users or have low vision. This fails WCAG 2.2 success criterion 2.1.1 Keyboard. We plan to amend this by November 2025.
  • Asterisks indicating required fields are not explained. This fails WCAG 2.2 success criterion 3.3.2 Labels or instructions. We plan to amend this by November 2025.
  • Some interactive elements are missing permanent label. This can make it difficult for users relying on screen readers to understand the purpose of these elements. This fails WCAG 2.2 success criterion 3.3.2 Labels or instructions. We plan to amend this by November 2025.
  • Current progression is not identified to assistive technologies. This can make it difficult for users relying on these technologies to track their progress. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value. We plan to address this by November 2025.
  • There is an instance of interactive element with no accessible name. This can make it difficult for users relying on screen readers to understand the purpose of the element. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value. We plan to address this by November 2025.
  • Some error messages are not announced in the correct format for screen reader users. This fails WCAG 2.2 success criterion 4.1.3 Status message. We plan to amend this by November 2025. 

PDF documents

  • Some images in our PDFs are missing alternative text. This fails WCAG 2.2 success criterion 1.1.1 Non text content. We plan to amend this by November 2025. 

What we’re doing to improve accessibility 

We are reviewing and updating older PDFs to ensure compliance, while also making sure that all current PDFs meet accessibility standards. 

Preparation of this accessibility statement

This statement was prepared on 30 October 2024. It was last reviewed on 23 February 2025. 

This website was last tested on 6 February 2025. The test was carried out by the accessibility team in Walsall Council. The tests included: 

  • a mixture of simple manual checks and automated tests to find only the most common barriers to users with accessibility needs
  • manual checks using each page without a mouse, viewing the page at different zoom settings, and simulating viewing the page on a small screen 

The automated tests were completed using the latest version of Axe and WAVE. 

Tests were completed using different settings in the Internet Explorer browser on Lenovo ThinkPad with a 13-inch screen.

Rate this page