This accessibility statement applies to the FutureGoals website:
This website is run by the West Yorkshire Combined Authority. We want as many people as possible to be able to use our website. For example, that means you should be able to:
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.
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 will consider your request and acknowledge your request within 3 working days.
We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements. Please contact us on email@example.com
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).
If you need directions to our offices, please call or email us.
The West Yorkshire 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 listed below.
The content listed below is non-accessible for the following reasons.
1: Across the website, decorative images have unnecessary alt text that make it very time consuming for screen reader users to navigate the site. This fails WCAG success criterion 1.1.1 (non-text content).
We plan to remove unnecessary alt text from our decorative images by [January 2022]
2: Colour contrast is insufficient in places making it hard from some people to read content on our website. This fails WCAG success criterion 1.4.3 (Contrast (Minimum)).
We plan to change all colours that do not pass contrast requirements by [January 2022]. Any new colours will be tested for compliance before being used on the website.
3: Some of our images contain text. This text cannot be changed or manipulated to suit user preferences so may be difficult for some users to read. This fails WCAG success criterion 1.4.5 (Images of Text).
We plan to resolve this issue by [January 2022].
4: On the homepage, the hero video plays automatically and cannot be paused or stopped. This may be distracting for some users and fails WCAG success criterion 2.2.2 (Pause, Stop Hide).
We plan to resolve this issue by [January 2022] by adding a pause button to the video.
1: Heading elements are not always used correctly, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and relationships).
We plan to review and update all heading elements to ensure they are used correctly by [January 2022] Any new pages will use heading elements correctly from creation.
2: Our website is missing key ARIA page landmarks or have duplicate ARIA landmarks, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and relationships).
We plan to review and update page landmarks to ensure they are used correctly across the site by [January 2022].
1: The ‘skip to content’ link is currently not visible when it receives focus. This fails WCAG success criterion 2.4.1 (Bypass blocks).
We plan to make our skip to content link visible by [January 2022].
2: The focus order through the main navigation is not as logical or efficient as it could be, which can make it confusing and time consuming for some users. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order)
We plan to change the focus order through the main to ensure it is logical by [January 2022].
3: The navigation is not correctly announced by a screen reader on mobile or desktop. This can make it difficult for blind users to use the main menu or understand the structure of the content contained within. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to resolve these issues with the navigation so it is announced accurately by a screen reader by [January 2022].
4: In some places on our website the keyboard focus is not visible, especially when using Mozilla FireFox. This makes it hard for keyboard users to identify which part of the site is active and fails WCAG 2.1 success criterion 2.4.7 (focus visible).
We plan to make the focus visible across the site by [January 2022].
5: The accordions used across the site are currently not included in the keyboard tabbing order so will be inaccessible to non-mouse users. This fails WCAG success criterion 2.1.1 (Keyboard).
We plan to resolve this issue and make the content within the accordions accessible to all users by [January 2022].
6: The purpose of links is not always clear from the text alone, which will affect screen reader users when they list links. This fails WCAG success criterion 2.4.4 (Link Purpose (In Context)).
We plan to change all links so they are meaningful without the context of the surrounding text by [January 2022]. Any new links added will also have clear purpose.
7: Some of our buttons, for example our social media icons, are missing programmatic labels so will be announced in an unhelpful way by a screen reader. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to add programmatic labels to all buttons by [January 2022]. Any new buttons will be added with programmatic labels as standard.
1: Checkboxes are not programmatically associated with their labels so are announced without the context the label provides. This can make it difficult for screen reader users to understand what is required of them. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to add programmatic labels to our checkboxes by [January 2022]. Any new forms will be developed with appropriate labels.
2: The error messaging on our forms is generic in places and does not describe how to correct the error. This fails WCAG success criterion 3.3.3 (Error suggestion)
We plan to change our error messaging so it accurately describes the issue and how to fix it by [January 2022]. Any new forms will be added with descriptive error messaging.
3: The error messaging on our forms is not announced by the screen reader so blind users will be unaware an error has occurred. This fails WCAG success criterion 4.1.3 (Status Message).
We plan to make the error messaging assertive by [January 2022].
We have identified a number of areas within this statement that do not comply with WCAG 2.1 guidelines. We plan to re audit our website by the end of December 2021 to validate resolutions to any areas that failed WCAG 2.1 listed in this accessibility statement.
This statement was prepared on 19 July 2021. It was last reviewed on 21 July 2021.
This website was last tested on 16th July 2021. This website was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and the test was carried out by Web Usability Partnership Ltd.
We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.