Accessibility Statement for The OU Myprogress - iOS

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

This accessibility statement applies to the iOS version 7.14 (2024) of the OU Myprogress app owned by MyKnowledgeMap, available at Apple App Store.

We want as many people as possible to be able to use our websites and mobile apps, and accessibility is an essential part of our mission. On our Accessibility hub, you'll find everything you need to answer any questions you have about accessibility, whether you're a student or a member of staff.

To adapt the content to your needs or preferences you should be able to:

• Increase the text size.
• Increase the display size.
• Tab through the content; the current location will be indicated by a clear visual change.
• Use zoom to magnify the screen.
• Use the app in either portrait or landscape display.
• Use single pointer gestures (e.g. requiring only one finger or pointer) which do not require precise movement (e.g. swiping) to activate controls.
• Use a screen reader (e.g. VoiceOver for IOS and TalkBack for Android) to listen to the content of screens and use any functionality on the page.
• AbilityNet also provides advice on making your device easier to use if you have a disability.

Compliance Status

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below

Non-accessible content

The content listed below is non-accessible for the following reason(s):

Non-compliance with the accessibility regulations

Display orientation:

The orientation of the app remains locked in portrait mode even when the device is rotated to landscape display orientation. This fails WCAG 2.2 Success Criterion 1.3.4: Orientation (Level A). This will be resolved by the end of December 2025.

Labelling and markup issues:

Links are incorrectly marked up as buttons. Several links are announced as buttons when a user navigates the screen using a screen reader. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships Orientation (Level A). This will be resolved by the end of June 2025.

Focus order issues:

Illogical focus order in tab navigation: When navigating section 1, section 2, and section 3 tab panels in the Apprentice Reflections form, the screen reader focus order does not follow the tab panel navigation pattern (or the visual layout of the content). This fails WCAG 2.2 Success Criterion 2.4.3: Focus Order (Level A). This will be resolved by the end of June 2025.

The text input fields following the headings Off the Job and Additional Support Needs do not receive focus. This fails WCAG 2.2 Success Criterion 2.4.3: Focus Order (Level A). This will be resolved by the end of June 2025.

Screen reader usage:

The table associated with the Likert scale is not accessible with screen readers: It is not clear which Switch button is associated with which option, and it can be very confusing for screen reader users. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A). This will be resolved by the end of June 2025.

Form submission status:

On saving an incomplete form and closing, or on submitting a completed form, the status message indicating whether the form has been saved as a draft or submitted successfully is not automatically announced by screen readers. This fails WCAG 2.2 Success Criterion 4.1.3: Status Messages (Level AA). This will be resolved by the end of June 2025.

Confusing section layout:

There are three sections displayed as tabs on the Apprentice goals and confirmation screen next to each other. There is also a Next button in section 1 to move to section 2, although all three sections are displayed on the same screen, resulting in too many form fields on one screen. In addition to screen reader users, this can also impact users with cognitive impairments. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A). This will be resolved by the end of June 2025.

Instructions are provided within a text field:

Text fields are used to provide instructions in some forms, which can be very confusing. Users normally expect text fields to be edit/input fields, and instructions to be included outside the text field. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A). This will be resolved by the end of June 2025.

Multiple choice options not announced by screen readers:

The selection status of multiple-choice options in forms is not announced by the screen reader. For example, it does not say 'Yes, radio button checked', or 'Yes, selected'. When reviewing a form later, screen reader users won't be able to identify which option they selected. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A). This will be resolved by the end of June 2025.

Insufficient colour contrast:

The colour used in the edit field boundaries and on other elements does not meet colour contrast requirements. This fails WCAG 2.2 Success Criterion 1.4.3: Contrast (Minimum) (Level AA). This will be resolved by the end of June 2025.

Preparation of this accessibility statement

This statement was prepared on 28 November 2022.

This statement was last reviewed on 4 September 2024.

This mobile app was last tested on 25 November 2022. Testing was carried out by the Accessibility and Usability Evaluation (AUE) team at The Open University.

The sample used for testing consisted of key screens from the OU Myprogress app. Manual testing was carried out on the sample content, and this included a review using the native screen reader for Android (TalkBack).

Feedback and contact information

If you find that a certain section of our website is not accessible and you can’t get access to the information that you need please use the Open University Accessibility Feedback Form to request support and we will ensure that you are provided with the information you require. You will need to provide your contact details and Personal Identifier if you are a student so we can get back to you. You should expect to hear back from us within 5 working days.

The OU is very experienced in meeting accessibility needs for our students. In many cases we are able to provide module and other study support materials in alternative formats for students who indicate a need for this when completing a Disability Support Form.

In addition, some module materials are available in different formats and can be downloaded from module websites. Students can contact their Student Support Team for advice.

If you are a student, or someone who has had contact with the University before, and have a complaint about the accessibility of our websites, you should raise a complaint via the complaints and appeals process.

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 are based in the UK, and you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).