Your feedback helps us to improve our website.

Accessibility statement for the MyMaps website

 This accessibility statement applies to https://mymaps.walsall.gov.uk/mywalsall.aspx  

This website is run by IShare on behalf of 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: 

  • not all page functionality is available for keyboard users
  • the tabbing order is not always logical
  • colour is used solely to visual display content
  • some form error messages are not properly associated with their corresponding field inputs
  • some custom controls do not have their roles or names properly defined
  • drag-and-drop functionality relies solely on mouse interaction
  • some content does not have sufficient colour contrast
  • interactive elements lack sufficient contrast against backgrounds
  • you cannot skip over repeated content on multiple pages
  • updates to content are not announced to screen reader users 

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:  

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

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

  1. Some images are missing alternative text. This fails WCAG 2.2 success criterion 1.1.1 Non text content. We plan to amend this by July 2025.
  2. Some heading levels and lists have been marked up incorrectly. Also form fields are not properly linked to their error messages. This may impact Blind or low vision users. This fails WCAG 2.2 success criterion 1.3.1 Info and relationships. We plan to amend this by July 2025.
  3. Some images use colour as the only visual means of conveying information This fails WCAG 2.2 success criterion 1.4.1 (Use of colour). We plan to amend this by July 2025.
  4. Some parts of the website do not have sufficient contrast between the text and background colours. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum). We plan to amend this by July 2025.
  5. Some content does not 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 July 2025.
  6. Visual information to identify user interface components, such as keyboard focus, does not always have a sufficient contrast ratio. This fails WCAG 2.2 success criterion 1.4.11  Non text contrast.  We plan to amend this by July 2025.
  7. 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 July 2025.
  8. There is no way to skip blocks of content. This may affect users who are blind or have low vision by making it harder to bypass repetitive blocks of content. This fails WCAG 2.2 success criterion 2.4.1 Bypass Blocks. We plan to amend this by July 2025.
  9. Some links do not match the intended destination for the user. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context). We plan to amend this by July 2025.
  10. Some elements on the page keyboard focus is unclear. This would affect users with low vision and cognitive impairments. This doesn’t meet WCAG 2.2 Success criterion 2.4.7 Focus visible. We plan to amend this by July 2025.
  11. Drag-and-drop functionality relies solely on mouse interaction. This fails WCAG 2.2 success criterion 2.5.7 Dragging movements. We plan to amend this by July 2025.
  12. Some of the targets that can be chosen are too small for the minimum target size requirements.  Some people with physical impairments cannot click small buttons that are close together. This fails WCAG 2.2 success criterion 2.5.8 Target size. We plan to amend this by July 2025
  13. Some interactive elements do not specify a name or role. Some forms controls do not have correct labels.  This fails WCAG 2.2 success criterion 4.1.2 (Name, Role and Value). We plan to amend this by July 2025.
  14. Some status 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 July 2025.  

What we’re doing to improve accessibility  

We are currently working with the provider to enhance the accessibility of this website. We have open tickets with the provider and aim to resolve some of these issues by July 2025. 

Preparation of this accessibility statement

This statement was prepared on 10 February 2025. It was last reviewed on 10 February 2025. 

This website was last tested on 16 January 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