Alerts 28 Bus

Website accessibility

We strive to make our websites accessible to everyone. Below are options and instructions for the various ways you can navigate this site.

This accessibility statement applies to the WY Metro website, which includes the following URLs:

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:

  • change colours, contrast levels and fonts
  • zoom in up to 300% 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)

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

How accessible this website is

Overall, most customers should be able to use the site without too much difficulty. We are aware, however, of some issues that may affect the accessibility of some parts of the website:   

  • people who navigate using only a keyboard may become disorientated on our site as there is no visible focus 
  • some of our forms may be difficult to complete for people that use a screen reader 
  • forms may also be difficult for keyboard-only customers to complete
  • some content is overlapped or truncated when using FireFox at 200% text zoom

 

Information in different formats 

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:  

Email -customerfeedback@westyorks-ca.gov.uk   

Call – 0113 251 7272  

Write - West Yorkshire Combined Authority, Wellington House, 40-50 Wellington Street, Leeds, LS1 2DE  

We will acknowledge your request within 3 working days.  

 

Reporting accessibility problems with this website  

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 customerfeedback@westyorks-ca.gov.uk 

 

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.   

If you need directions to our offices, please call or email us.  

Email - customerfeedback@westyorks-ca.gov.uk  

Call – 0113 251 7272  

Write - West Yorkshire Combined Authority, Wellington House, 40-50 Wellington Street, Leeds, LS1 2DE  

 

Technical information about this website’s accessibility 

WY Metro 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 

The website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to ‘the non-compliances and exemptions’ listed below. 

 

Non-accessible content 

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

 

Non-compliance with the accessibility regulations 

Page design 

  1. Some of the text links on our website are only distinguished by colour. This may be imperceivable to some users and fails WCAG success criterion 1.4.1 (Use of Colour). We plan to review our link styling and add additional formatting to ensure links do not rely on colour alone by [June 2023]. 
  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 [June 2023]. Any new colours will be tested for compliance before being used on the website.
  3. Text gets cut off when enlarged on main pages when viewed with text resized to 200% using custom browser settings in Firefox. This fails WCAG success criterion 1.4.4 (Resize text). We plan to resolve this issue by [June 2023].
  4. On the homepage, the carousel pause button cannot be accessed using just a keyboard so some users will be unable to pause or stop it. 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 [June 2023] by making the pause button keyboard operable. 

Page structure 

  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 [June 2023]. Any new pages will use heading elements correctly from creation. 
  2. Our website is missing a key ARIA page landmark, 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 [June 2023].

Navigation, links and buttons 

  1. Some parts of the website cannot be operated using just a keyboard, which will make these parts inaccessible to some users. This fails WCAG success criterion 2.1.1 (Keyboard). We plan to make everything on our website keyboard operable by [June 2023]. All future website developments will be tester for keyboard operability before launch. 
  2. Most pages on the site are missing a ‘skip to content’ bypass link. This can make navigation very time consuming for some users and fails WCAG success criterion 2.4.1 (Bypass Blocks). We plan to add a ‘skip to content’ bypass link by [June 2023].
  3. In places, the focus order across the site is not logical. This may cause some of our users confusion when they are navigating through the site and fails WCAG success criterion 2.4.3 (Focus Order). Where these issues exist, we plan to review and correct the focus order by [June 2023] to ensure it is logical.  
  4. 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 [June 2023]. Any new links added will also have clear purpose.  
  5. Across most of our website the keyboard focus is not visible. 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 [June 2023].
  6. The presentation of links across the website is not consistent which may make is harder for some users to distinguish what is and isn’t a link. This fails WCAG success criterion 3.2.4 (Consistent Identification). We plan to standardise our approach to link presentation, so it is consistent across the site by [June 2023]. Any new links will adopt this style.  

Interactive forms 

  1. Form fields, including search boxes, are missing programmatic labels which means it may not be clear to screen reader users what information they need to enter. This fails WCAG success criterion 4.1.2 (Name, Role, Value).We plan to resolve all programmatic labelling issues by [June 2023]. Any new forms will be developed with the correct 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 [June 2023]. 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 [June 2023]. 

PDFs 

  1. PDFs are missing document titles that can make it difficult for screen reader users to quickly establish the contents of the document. This fails WCAG success criterion 2.4.2 (Page Titled). We plan to add document titles to all PDFs on our site by [June 2023]. Any new PDFs will be published with titles as standard. 
  2. PDFs are missing document bookmarks which are a key method of navigation for some users. This fails WCAG success criterion 2.4.5 (Multiple Ways). We plan to add bookmarks to our PDFs by [June 2023]. Any new PDFs will be developed with bookmarks as standard. 
  3. PDFs do not have a language set so screen readers may not know which language they should be accessing the content in. This fails WCAG success criterion 3.1.1 (Language of Page). We plan to add the correct language options to our PDFs by [June 2023]. Any new PDFs will have a language set as standard.  

 

Content that’s not within the scope of the accessibility regulations 

Maps on our site are missing alt text. The accessibility regulations do not require us to add alt text as long as an address is provided alongside the map. 

Some of our pre-recorded audio and video published before 23 September 2020 do not have audio descriptions. The accessibility regulations do not require us to add audio descriptions to audio and video published before this date.

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. 

Preparation of this accessibility statement 

This statement was prepared on 18 August 2021. It was last reviewed on 2 December 2022.

This website was last tested on 18th August 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. 

Alerts 28 Bus

Get our email newsletter

For the latest news and offers direct to your inbox.