MCard Mobile App Accessibility Statement

This accessibility statement applies to the MCard Mobile App.

This app is run by the West Yorkshire Combined Authority. We want as many people as possible to be able to use our app.

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

 

How accessible this app is

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

  • The app cannot be used in landscape orientation
  • Most of the app cannot be used with an external Bluetooth keyboard
  • Some key components are not operable when swiping through the contents on iOS while using VoiceOver screen reader
  • Most interactive form components are not associated with their visible labels

 

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.2 AA standard, due to ‘the non-compliances and exemptions’ listed below. 

 

Non-compliance with the accessibility regulations

 

Navigation, links and other elements

  1. Most of the app is not operable using an external Bluetooth keyboard, including selecting tickets This fails WCAG success criterion 2.1.1. We plan ensure all interactive elements within the app are accessible by keyboard by [August 2025].
  2. Focus order is not always correct when navigating through the app including on the payment screen, help screen and content within the FAQ accordions. This fails WCAG success criterion 2.4.3. We will ensure that the focus order is logical and consistent throughout the app by [August 2025].
  3. On the parts of the app that are keyboard operable, there is either no visible focus indicator or it is very unclear (a slight change in colour). This makes it difficult for sighted keyboard users to navigate the app and fails WCAG success criterion 2.4.7. We plan make all interactive controls, including buttons have a high-vis indicator on focus by [August 2025].
  4. Link context is not always clear on the app which fails WCAG success criterion 2.4.4. We plan to add additional programmatic context to links by [August 2025].
  5. Tabs on the ‘select ticket’ screen have no programmatic indication, making them inaccessible to non-sighted users. This fails WCAG success criterion 1.3.1. We plan to review our use of tabs in this area of the app and ensure their role is clearly conveyed by [August 2025].
  6. During the ticket selection process, there is no programmatic indication that secondary messaging has appeared when an option is selected. This means that screen reader users may miss this new information and fails WCAG success criterion 3.2.2. We plan to fix this by [August 2025].
  7. Some interactive elements do not have programmatic labels and are therefore announced in an unclear way. This fails WCAG success criterion 4.1.2. We plan to fix this by ensuring all interactive elements have appropriate, descriptive programmatic labels by [August 2025].

 

Forms and payments

  1. Some form elements such as radio buttons, text fields and dropdowns are not grouped with their labels so are not announced descriptively. This fails WCAG success criterion 1.3.1. We plan to review all form elements and ensure they all have a properly associated form label by [August 2025].
  2. Error messaging on the payment screen is not sufficiently clear which fails WCAG success criterion 3.3.3. We plan to fix this by [August 2025].
  3. Error prevention techniques on the payment screen are not sufficient which fails WCAG success criterion 3.3.4. We plan to fix this by providing clear and informative error messaging by [August 2025].
  4. Error messaging in the registration process is not announced by a screen reader. This fails WCAG success criterion 4.1.3. We plan to fix this by ensuring notifications are announced by [August 2025].

 

Structure 

  1. It is not possible to view any part of the app in landscape orientation, it is only available in portrait. This fails WCAG success criterion 1.3.4. We plan to resolve this issue by [August 2025]. 
  2. The text in the app cannot be resized when using the phone’s text resizing tool. This may make the app difficult for visually impaired individuals to use and fails WCAG success criterion 1.4.4. We plan to fix this by [August 2025].

 

Colour contrast

  1. There are some areas where the contrast of text against the background colour is insufficient. This fails WCAG success criterion 1.4.3. We plan to adjust text colour and/or background colour to give them a higher contrast value by [August 2025].
  2. There are some areas where the graphic colour contrast is insufficient. This fails WCAG success criterion 1.4.11. We plan to adjust these graphical elements to give them a higher contrast value by [August 2025].

 

Preparation of this accessibility statement 

This statement was prepared on 19 August 2024. It was last reviewed on 19 August 2024.

This website was last tested on 8 August 2024. This website was tested for compliance with the Web Content Accessibility Guidelines V2.2 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.