This accessibility statement applies to content hosted on the wmca.org.uk domain (and its subdomains beta.wmca.org.uk and governance.wmca.org.uk).
This website is run by West Midlands Combined Authority. We want as many people as possible to be able to use this website. For example, that means you should be able to:
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We’ll consider your request and get back to you in 10 days.
There is more information about what we can provide and our process in our reasonable adjustments policy.
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 the Equalities Team:
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).
We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.
Our offices and travel shops have audio induction loops.
You can read more about reasonable adjustments we are able to provide.
West Midlands Combined Authority is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.
The content listed below is non-accessible for the following reasons.
Some interface elements can’t receive keyboard focus, and non-interactive elements appear in the tab index. This fails WCAG success criterions 2.4.3 Focus Order and 2.4.7 Focus Visible. We will fix this by November 2020.
The search button is only interactable with a keyboard. This fails WCAG success criterion 2.4.4 Link Purpose. We will fix this by November 2020.
The search box close link text is displayed vertically. This fails WCAG success criterion 1.4.8 Visual Presentation. We will fix this by November 2020.
Links do not have a hover state, and may not be noticed by some users. This fails WCAG success criterion 1.4.1 Use of Colour. We will fix link hover styling by November 2020.
Some interface elements such as text and buttons do not have sufficient colour contrast. This fails 1.4.3 Contrast (minimum). We will fix this by November 2020.
Some page titles aren’t meaningful, and may not make sense to screen reader users. This fails WCAG success criterion 2.4.2 Page Titled. We will fix this by November 2020.
Some headings do not have correct hierarchy, or are skipped by screen readers. This fails WCAG success criterion 2.4.6 Headings and Labels. We will fix these issues by November 2020.
Some graphic interface elements do not have labels, so they are skipped by screen readers. This fails WCAG success criterion 1.1.1 (Non-text content). We will fix this by November 2020.
Some images and icons do not have appropriate alt-text, or have alt-text where they don’t need it. This fails WCAG success criterion 1.1.1 Non-text content. We will fix these by November 2020.
Some form elements do not have appropriate labels, or are not associated with their text labels. This fails WCAG success criterions 1.1.1. Non-text content, 1.3.1 Info and relationships, 2.4.6
Headings and labels and 3.3.2 Labels or instructions. We will fix these by November 2020.
Disabled buttons are not correctly marked as disabled to screen reader users. This fails WCAG success criterion 4.1.3 Status messages. We will fix this by November 2020.
Some links do not make sense out of context, or links without text are used. This fails WCAG success criterion 2.4.4 Link purpose (In context). We will fix this by November 2020.
Selecting an area on the In My Area page redirects users to a new page without warning. This fails WCAG success criterions 3.2.2 On Input and 2.1.1 Keyboard. We will fix this by November 2020.
In some places you cannot scale the page up to 300% without loss of content. This fails WCAG success criterion 1.4.10 Reflow. We will fix this by November 2020.
Navigation links do not describe their context to screen readers and are hard to understand for screen reader users. This fails WCAG success criterion 1.3.1 Info and relationships. We will fix this by March 2021.
The document language isn’t identified in the markup. This fails WCAG success criterion 3.1.1 Language of page. We will fix this by March 2021.
Some text, such as headings, are too small. This fails WCAG success criterion 3 Understandable. We will fix this by March 2021.
We class services which are planned to be replaced by the end of 2021 as legacy services.
These services are:
The current WMCA website will be replaced by a new website in phases, with the last services to move over by the end of 2021.
We’ve assessed the cost of fixing the issues with our legacy services. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.
We will make another assessment in February 2021.
Some interface elements do not have sufficient colour contrast. For example, buttons, text and hovering on buttons.
Some elements change too fast, and are hard to understand. For example, the what we do slider on the homepage.
Page elements are not contained within landmarks, so they cannot be skipped.
Some images do not have alt-text.
Some decorative elements have alt-text, when they don’t need them.
Some buttons are too small for some users to click.
Some links do not have hover states.
Some form elements do not scale appropriately on mobile, and require horizontal scrolling.
Some links do not have appropriate link text.
Some text does not use a sufficient weight, or is presented in a way that is hard to read.
The service is difficult to navigate using a keyboard or screen reader software. For example, some blocks of content do not have a defined role or tab order does not follow logical order.
Forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ or ‘select’ tag and some form inputs are not grouped.
Some buttons and accordions cannot be selected using a keyboard.
Some buttons do not have descriptive labels.
The service might not display correctly in system high contrast mode due to the way pages are styled.
Some automatically generated links do not make sense out of context. For example, links to read more details about, or buying a specific ticket.
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 WMCA 2018-2019 Annual Plan.
Any new PDFs or Word documents we publish will meet accessibility standards.
Text content is not written in plain English. When we publish new content, we’ll make sure it meets the accessibility standards.
This statement was prepared on 16 September 2020. It was last reviewed on 16 September 2020.
This website was last tested on 14 September 2020. The test was carried out by Zimo Accessibility.
We used this approach to decide on a sample of pages to test: