Accessibility  Appendix 2: Mobile app accessibility statements

This accessibility statement applies to the IMC (International Medieval Congress) mobile application. It is available for iOS and Android devices.

This app is branded for the University of Leeds by a third-party supplier, Confex, and is intended for use by members of the public as well as students and staff of the University.

While we are working actively to resolve the accessibility issues with this app AbilityNet has advice that may make it more usable in its current state.

How accessible this mobile application is

We know some parts of this mobile application are not fully accessible:

• The forward and backward buttons on the ‘Schedule’ screen aren’t available to screen reader users. This may make it harder for them to access session information and locations. For additional support, on-campus International Medieval Congress delegates are encouraged to visit the Information Desk in The Refectory (on the Precinct in the centre of campus, just off the corner of Lifton Place and Cromer Terrace) or to email the IMC team in advance via imc@leeds.ac.uk.
• There are problems with the functionality of the search filters for screen reader users that allow them to use inactive filters, clearing their search results in a way that may be unexpected.
• Errors during the ‘Sign in’ process aren’t automatically announced for screen reader users. If they have trouble logging in, people are encouraged to email the IMC team via imc@leeds.ac.uk.
• On triggering some menus and screens, focus behaves in an unexpected way that may make it difficult for screen reader users to operate the app smoothly.

If convenient, some people may find the desktop browser version of the app, the IMC virtual event platform, works better with assistive technologies.

Feedback and contact information

If you need information in this mobile application in a different format like accessible PDF, large print, easy read, audio recording or braille, please make contact through IT Services:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

Reporting accessibility problems with this mobile application

We’re always looking to improve the accessibility of this mobile application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please make contact through IT Services and provide the mobile application you’re using and the issue you’ve identified:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

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

More information about access to our campus is available in information for disabled visitors.

If you have any specific questions, details for different sections of the University are listed on our contact page.

Technical information about this mobile application’s accessibility

University of Leeds is committed to making its mobile applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 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.

These issues have been found via simple testing of the mobile application. There may be more accessibility problems than mentioned here.

Non-compliance with the accessibility regulations

The third-party supplier is commissioning a digital accessibility audit of all its platforms and aims to address all non-compliances by mid 2025.

• Some instructions include sensory-specific information. This will make it harder for people with vision impairments to complete tasks. This fails WCAG 2.2 1.3.3 Sensory Characteristics (Level A).
• Using a screen reader, it’s not possible to reach some parts of the user interface, such as the forward and back buttons to navigate between sessions, and the share button on an individual session. This will make it harder for screen reader users to navigate the app and communicate information. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (Level A).
• When using the ‘Filter’ in the ‘Search’ page, screen reader users aren’t notified that the controls on some filters are inactive because there are no results available using that filter. However, they can select them, causing this to clear the results page with no warning. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (Level A).
• Triggering various menus and controls throughout the app causes focus to be repositioned partway through a screen, menu, or series of controls. This will make it harder for screen reader users to operate the app. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (Level A).
• Errors on the ‘Sign in’ screen aren’t automatically announced for screen reader users. This will make it harder for screen reader users to use the app. This fails WCAG 2.2 success criterion 4.1.3 Status Messages (Level AA).

Disproportionate burden

We aren’t claiming disproportionate burden against any of the mobile application’s accessibility problems at this time.

What we’re doing to improve accessibility

The University of Leeds has a Web Accessibility Project that is working towards full WCAG 2.2 AA compliance for the majority of the most-used sites within the University’s web estate.

Addressing the compliance of mobile applications falls outside the scope of this project. Nonetheless, colleagues are working to improve the compliance of all mobile applications that should be accessible as well as all websites and browser-based systems.

Preparation of this accessibility statement

This statement was prepared on 28 June 2022. It was last reviewed on 18 June 2024.

This mobile application was last tested on 18 June 2024. The test was carried out by the University of Leeds.

The testing consisted of the following:

• Selecting a sample of screens including the log-in, home, and schedule screens.
• Assessing all these screens using an iPhone with iOS VoiceOver and VoiceControl.
• Checking items on each page for colour contrast failures.
• Checking whether the mobile application responded to changes in device orientation.

This accessibility statement applies to the GFaL Rewards mobile application. It is available for iOS and Android devices.

This app is branded for the University of Leeds by a third-party supplier, Lolly, and is intended for use by members of the public as well as students and staff of the University.

While we are working actively to resolve the accessibility issues with this app AbilityNet has advice that may make it more usable in its current state.

How accessible this mobile application is

We know some parts of this mobile application are not fully accessible:

• On the main screen viewers are not told that, or where, the QR code image is displayed. This is likely to make that functionality harder to use for blind or partially sighted people. 
• There are many items that don’t have fully descriptive labels, such as the loyalty stamp area. This will make the app extremely difficult to operate for screen reader users.
• Focus order when using a screen reader is unusual and affects meaning in several areas of the app. This makes it likely the app will be confusing to operate for screen reader users.

Feedback and contact information

If you need information in this mobile application in a different format like accessible PDF, large print, easy read, audio recording or braille, please make contact through IT Services:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

Reporting accessibility problems with this mobile application

We’re always looking to improve the accessibility of this mobile application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please make contact through IT Services and provide the mobile application you’re using and the issue you’ve identified:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

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

More information about access to our campus is available in information for disabled visitors.

If you have any specific questions, details for different sections of the University are listed on our contact page.

Technical information about this mobile application’s accessibility

University of Leeds is committed to making its mobile applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 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.

These issues have been found via simple testing of the mobile application. There may be more accessibility problems than mentioned here.

Non-compliance with the accessibility regulations

The third-party supplier has been notified of all the following non-compliances and assured the University that they are prioritising fixes. The University will seek to have all issues resolved by the end of 2024.

• Notification bell badge is announced as only the number that's displayed, e.g. '1'. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
• The available fund figure is announced but it’s not clear either from the surrounding context or an associated label what this figure definitely relates to. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
• There is unusual focus order for the components that doesn't represent the visual order throughout the app. For example, on the main screen, focus starts at the 'Plus' symbol then moves through to the customer name, funds figure, then 'add' and 'funds'. This is likely to cause confusion for keyboard and assistive technology users. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (Level A).
• In the funds area, the 'Plus' symbol is ambiguous and should have a label that indicates what it does. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
• On the main screen, the avatar image cannot be accessed via VoiceOver. Screen reader users should be able to reach all interactive elements. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (Level A).
• VoiceOver struggles to move below the line 'Scan this QR code in store', and users are required to make at least five repeated forward steps to progress through to the rest of the screen. This is likely to cause confusion for keyboard and assistive technology users. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (Level A).
• It's unclear to screen reader users where the QR code is on the screen to enable them to scan it. Also not clear to users in general why they need to scan the QR code. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A).
• VoiceOver users cannot interact with the 'Scan this QR code in store' button. It's not possible to make it 'flip' to show the text code. Additionally, it's not clear from the label that this area has any interactivity. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 2.4.6 Headings and Labels (Level AA) and 2.1.1 Keyboard (Level A).
• On the 'Tap to show QR code' area, it's not clear a code is being displayed. VoiceOver attempts to read out the code as a word, and there's no other text to explain what the word/code relates to. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A).
• Each loyalty stamp placeholder is announced as a number. The labels should indicate more information (e.g., Drink stamp 1, unstamped). This also needs to adjust for a 'stamped' status. This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
• In the loyalty stamp area, it’s not possible to select the 'information' button via screen reader. Screen reader users should be able to reach all interactive elements. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (Level A).
• In the ‘More’ screen, all menu items have two buttons/elements that receive focus: the item text and the chevron that's announced as: "Single right pointing angle quotation mark". This can cause confusion for screen reader users. This fails WCAG 2.2 success criteria 2.4.6 Headings and Labels (Level AA) and 2.1.1 Keyboard (Level A).
• On the ‘Activity’ screen, the tabs 'All', 'Account' and 'Loyalty' are not announced to a screen reader user, and they cannot access 'Filter Options'. This will be an obstruction for screen reader users. This fails WCAG 2.2 success criteria 2.4.6 Headings and Labels (Level AA) and 2.1.1 Keyboard (Level A).
• On the ‘Personal Details’ screen, screen reader users cannot select the 'Contact Preferences' checkboxes. Screen reader users should be able to reach all interactive elements. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (Level A).

Disproportionate burden

We aren’t claiming disproportionate burden against any of the mobile application’s accessibility problems at this time.

What we’re doing to improve accessibility

The University of Leeds has a Web Accessibility Project that is working towards full WCAG 2.2 AA compliance for the majority of the most-used sites within the University’s web estate.

Addressing the compliance of mobile applications falls outside the scope of this project. Nonetheless, colleagues are working to improve the compliance of all mobile applications that should be accessible as well as all websites and browser-based systems.

Preparation of this accessibility statement

This statement was prepared on 24 June 2022. It was last reviewed on 18 June 2024.

This mobile application was last tested on 18 June 2024. The test was carried out by the University of Leeds.

The testing consisted of the following:

• Selecting a sample of screens and all parts of the app immediately reachable via the app’s main screen.
• Assessing all these screens using an iPhone with iOS VoiceOver and VoiceControl.
• Checking items on each page for colour contrast failures.
• Checking whether the app responded to changes in device orientation.
   

This accessibility statement applies to the RRapid eBook mobile application. It is available for iOS and Android devices.

This app is controlled by the University of Leeds and is intended for use by members of the public as well as students and staff of the University.

While we are working actively to resolve the accessibility issues with this app AbilityNet has advice that may make it more usable in its current state.

How accessible this mobile application is

We know some parts of this mobile application are not fully accessible:

• The app doesn’t respond to a switch from portrait to landscape orientation, so may be difficult to use for those who need their device positioned this way.
• There is text in images. This doesn’t always come with a functioning description either in code or in nearby text. It will be difficult for those with partial or no sight to use some of this app, particularly in the self-test questions area.
• Video content doesn’t come with captions, audio description or a media alternative. This will cause difficulties for Deaf/deaf people, those who are hard of hearing, blind people and vision-impaired people.
• The reading order communicated to assistive technologies, such as screen readers, is incorrect in some places, including the title page. This may cause confusion for some users, such as people using screen readers.
• Some parts of the interface cannot be accessed via a keyboard or screen reader interaction, such as the ‘Start course’ button on the ‘Test your knowledge’ page.
• There are problems with focus when using a screen reader, including pop-ups not automatically receiving focus.
• Some navigation buttons do not have accessible names, which will make it more difficult to control the app via voice control technology.

Feedback and contact information

If you need information in this mobile application in a different format like accessible PDF, large print, easy read, audio recording or braille, please make contact through IT Services:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

Reporting accessibility problems with this mobile application

We’re always looking to improve the accessibility of this mobile application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please make contact through IT Services and provide the mobile application you’re using and the issue you’ve identified:

• Web: Use either the contact form for people who cannot log in to the IT site or the contact form for people who can log in.
• Phone: Call the IT Service Desk on 0113 343 3333

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

More information about access to our campus is available in information for disabled visitors.

If you have any specific questions, details for different sections of the University are listed on our contact page.

Technical information about this mobile application’s accessibility

University of Leeds is committed to making its mobile applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 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.

These issues have been found via simple testing of the mobile application. There may be more accessibility problems than mentioned here.

Non-compliance with the accessibility regulations

We plan to address all the following issues by the end of 2024.

• The app doesn’t respond to a switch from portrait to landscape orientation. This fails WCAG 2.2 success criterion 1.3.4 Orientation (Level AA).
• Text in images don’t always come with a functioning description either in code or in nearby text. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (Level A).
• Video content doesn’t come with captions, audio description or a media alternative. This fails WCAG 2.2 success criteria 1.2.2 Captions (Prerecorded) (Level A), 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A), 1.2.5 Audio Description (Prerecorded) (Level AA).
• The reading order is incorrect in some places. This fails WCAG 2.2 success criterion 1.3.2 Meaningful Sequence (Level A).
• Some parts of the interface cannot be accessed via a keyboard or screen reader interaction. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (Level A).
• There are problems with pop-ups not automatically receiving focus. This fails WCAG 2.2 success criteria 2.4.3 Focus Order (Level A).
• Some navigation buttons do not have accessible names. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (Level A).
• Error messages on the Case Log screen aren’t presented to the user by assistive technologies. This fails WCAG 2.2 success criterion 4.1.3 Status Messages (Level AA).

Disproportionate burden

We aren’t claiming disproportionate burden against any of the mobile application’s accessibility problems at this time.

What we’re doing to improve accessibility

The University of Leeds has a Web Accessibility Project that is working towards full WCAG 2.2 AA compliance for the majority of the most-used sites within the University’s web estate.

Addressing the compliance of mobile applications falls outside the scope of this project. Nonetheless, colleagues are working to improve the compliance of all mobile applications that should be accessible as well as all websites and browser-based systems.

Preparation of this accessibility statement

This statement was prepared on 24 June 2022. It was last reviewed on 24 April 2024.

This mobile application was last tested on 21 June 2022. The test was carried out by the University of Leeds.

The testing consisted of the following:

• Selecting a sample of screens including the main app screen, contents page, case log page, and self-text questions page. 
• Assessing all these screens using an iPhone with iOS VoiceOver and VoiceControl.
• Checking items on each page for colour contrast failures.
• Checking whether the app responded to changes in device orientation.