Accessibility statement for Committee Management Information System (CMIS)

Minimize

This accessibility statement applies to the website  CMIS - https://cmispublic.walsall.gov.uk/cmis/Home.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:

  • 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.

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:

  • Low colour contrast against the background will cause issues for the visually impaired
  • Images without alternative text, will not be read by a screen reader
  • Lists without labels will be difficult to read for all users and will confuse a screen reader
  • Forms without labels will cause issues for screen readers
  • 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
  • PDF’s without Bookmarks and Page language may cause problems for all users, especially for those with visual or cognitive impairments

 

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:

  • Democraticservices@walsall.gov.uk
  • 01922 650000

We’ll consider your request and get back to you in 5 days.

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

 

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: democraticservices@walsall.gov.uk & 01922 650000.

 

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

 

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Find out how to contact us at Walsall Council

 

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

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 heading levels have been skipped and marked up incorrectly. This may impact Blind or low vision users. This fails WCAG 2.1 success criteria 1.3.1 Info and Relationships & 2.4.1 Bypass Blocks. We plan to amend the headings by January 2024. When we publish new content we’ll make sure our use of headings 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).

Some of the keyboard focus may not be clearly visible. 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).

Some text cannot be resized without loss of content or functionality. Which means people with visual impairments may be unable to access some content This doesn’t meet WCAG success criteria 1.4.4 (Resize Text). We plan to amend the text resizing by  January  2024. When we publish new content we’ll make sure our use of text resizing 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 text resizing by  January  2024. When we publish new content we’ll make sure our use of text resizing meets accessibility standards.

Some PDF’s the Language of the Page cannot be identified. This would effect screen reader users. This fails WCAG  2.1 success criteria 3.1.1 (Language of the page). We plan to amend the language of the page by  January  2024. When we publish new content we’ll make sure our use of language meets accessibility standards.

Some PDF’s do not have Bookmarks. . This fails WCAG  2.1 success criteria 2.4.1 Bypass Blocks. We plan to amend the bookmarks in PDF’s by  January  2024. When we publish new PDF’s we’ll make sure our use of Bookmarks meets accessibility standards.

Some of the purpose or destination of a link cannot be determined from the link text. This doesn’t meet WCAG 2.1 success criteria 2.4.5 (Multiple ways). 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 pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways). We plan to amend the navigation by  January  2024. When we publish new content we’ll make sure our navigation meets accessibility standards.

There is no “Skip to Content” present. This may effect users who are blind or have low vision. This fails WCAG 2.1 success criteria 2.4.1 (Bypass Blocks). We plan to amend the navigation by January 2024. When we publish new content we’ll make sure our use of navigation meets accessibility standards.

Some frames have not been labelled correctly. 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 headings by January 2024. When we publish new content we’ll make sure our use of headings meets 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 forms are not labelled correctly. This fails WCAG 2.1 success criteria 4.1.2 Name Role and Value. ). We plan to amend the form labels by January 2024. When we publish new content we’ll make sure our use of form labels meets accessibility standards.

Some images are missing alt text. This fails WCAG 2.1 success criterion 1.1.1 (non text content)  We plan to amend the images by January 2024. When we publish new content we’ll make sure our use of images meets accessibility standards.

Some forms do not have labels This fails WCAG 2.1 success criterion 1.1.1 (non text content). We plan to amend the forms by January 2024. When we publish new content we’ll make sure our forms meet 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 by January 2024. When we publish new pages we will make sure our page titles meet accessibility standards

 

Content that’s not within the 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.

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

We are planning to launch a new website by September 2023. Staff will be trained on accessibility skills going forward.

 

Preparation of this accessibility statement

This statement was prepared on 27 April 2023. It was last reviewed on 17 May 2023.

This website was last tested on 01 March 2023. The test was carried out by Walsall Council DaTS Team.