Have Your Say Today - Commonplace Accessibility Statement - Walsall Engagement Hub

Home

Commonplace Accessibility Statement

1/2

Accessibility statement for Walsall Council Commonplace sites

This accessibility statement applies to:

WAW 2040, Walsall says, Walsall Walking and Cycling, Parks and Green Spaces, Walsall Borough Local Plan.

These websites are run by Commonplace, but managed by Walsall Council. We want as many visitors (or respondents) as possible to be able to use this website and leave feedback on consultations, including those with accessibility needs . For example, that means you should be able to: 

  • change colours, contrast levels and fonts
  • zoom in up to 200% 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’ve also made the website text as simple as possible to understand, and we add alternative text to every image where possible.

We have a accessibility feature, provided by Userway, designed to help with the following accessibility needs: 

  • Motor impairment
  • Blindness/color blindness
  • Dyslexia
  • Visual impairments
  • Cognitive and learning impairments
  • Epilepsy
  • ADHD 

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

How accessible this website is:

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

  • Low colour contrast against the background will cause issues for the visually impaired
  • Lists without labels will be difficult to read for all users and will confuse a screen reader
  • Page functionality being available to keyboard only users, who may have cognitive impairments.
  • Keyboard focus elements not being clear for users with vision and cognitive impairments
  • Links incorrectly labelled will cause issues for all users, but especially the visually impaired
  • Page titles not reflecting content will cause issues for all users and reduce the likelihood that a user can find the content through a search engine
  • Hidden content with different screen settings may confuse all users 

The above points are being actively worked on, and we advise to use the Userway accessibility function as much as possible.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille please contact us via email at support@commonplace.is We’ll consider your request and get back to you within 48 hours. If you cannot view the map on our ‘contact us’ page, email us at support@commonplace.is 

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 our support team at support@commonplace.is and they will be able to escalate any issues to our development team.

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)Empty heading

Technical information about this website's accessibility

Commonplace 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 (WCAG) 2.1 AA standard, due to the non-compliances listed below. Empty heading

Non-accessible content

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

Non-compliance with the accessibility regulations

Some parts of the website do not have sufficient contrast. Between the text and background colours. This fails WCAG 2.1 success criterion 1.4.3 (contrast minimum). We plan to amend the colour contrast by January 2024. When we publish new content, we’ll make sure our use of colour meets accessibility standards.

Some pages do not have a unique page title. The page title should describe the topic of the page, purpose of the page or the subject of the page. This doesn’t meet WCAG success criteria 2.4.2 (Page Titled). We plan to amend the page titles January 2024. When we publish new content, we’ll make sure our use of Page Titles meets accessibility standards.

Some links are not labelled correctly and may not take the user to the correct destination. This fails WCAG 2.1 success criteria 2.4.4 Link Purpose (In Context) and 1.1.1: Non-text Content. We plan to amend the links by January 2024. When we publish new content, we’ll make sure our use of links meets accessibility standards.

Some elements have not been marked up correctly with unique ID’s. This fails WCAG success criteria 4.1.1(Parsing) We plan to amend the markup by January 2024. When we publish new content, we’ll make sure our use of markup meets accessibility standards.

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.1 success criterion 1.4.10 (Reflow). We plan to amend the reflow by January 2024. When we publish new content, we’ll make sure our use of reflow meets accessibility standards.

Some elements on the page keyboard focus was unclear. This would effect users with low vision and cognitive impairments. This doesn’t meet WCAG success criteria 2.4.7 (Focus Visible). We plan to amend the keyboard focus by January 2024. When we publish new content, we’ll make sure our use of keyboard focus to meet accessibility standards)

On some pages the tabbing order is not clear and logical, when navigating with a keyboard. This fails WCAG success criteria 2.4.3 ( Focus Order) We plan to amend the tabbing order by January 2024. When we publish new content we’ll make sure our use of navigation meets accessibility standards.

Some of the keyboard focus may not be clearly visible, against the background. . This fails WCAG 2.1 success criteria 2.4.11 Focus Appearance. We plan to amend the keyboard appearance by January 2024. When we publish new content we’ll make sure our use of focus appearance meet accessibility standards)

Not all page functionality is available to Keyboard only users, This may effect users who are blind or have low vision. This fails WCAG success criterion 2.1.1 (Keyboard). We plan to amend the keyboard functionality by January 2024. When we publish new content, we’ll make sure our use of keyboard functionality meets accessibility standards.

Some lists have been marked up incorrectly. This may impact Blind or low vision users. This fails WCAG 2.1 success criteria 1.3.1 Info and Relationships. We plan to amend the lists by January 2024. When we publish new content we’ll make sure our use of lists meets accessibility standards.ding

Empty headi

Content that is not in scope of the accessibility regulations

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

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 [example of non-essential document].

 Any new PDFs or Word documents we publish will meet accessibility standards. 

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’re doing to improve accessibility

Timeline for improving accessibility: 

  • Training and material resources for Userway accessibility by June 2023
  • Contrast testing by July 2023 - this may also be resolved by Userway or via branding settings.
  • Alternative text for all images reviewed and updated by August 2023
  • HTML markups, hidden content and labels revised, reviewed and updated by September 2023
  • Reflow testing and updating by October 2023
  • Keyboard focus testing and updates by November 2023.
  • Screen reader testing by November 2023

Empty headi

Preparation of this accessibility statement

This statement was prepared on 07 June 2023. It was last reviewed on 07 June 2023.

  • WAW 2040 was last tested on 31 March 2023
  • Walsall says was last tested on 03 April 2023
  • Walsall Walking and Cycling was last tested on 04 April 2023
  • Parks and Green Spaces was last tested on 17 May 2023
  • The tests were carried out by Walsall Council DaTS Team.