Accessibility Statement for OU Study - iOS

The Open University (OU) 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 of version 4.4.1.5 of the OU Study mobile application, released to the App Store on 22 January 2025.

We want as many people as possible to be able to use our websites and apps, and accessibility is an essential part of our mission. To adapt the content of the app to your needs or preferences you should be able to:  

• Use the text size options within the app’s own settings to increase text size.
• Increase the display size.
• Navigate 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) 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 app is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to ‘the non-compliances’ listed below.

Non-accessible content 

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

Non-compliance with the accessibility regulations

Enlarging content

When the “Larger Text” option is turned on in the iOS accessibility settings, text in the app does not respond and remains at the default size. This fails WCAG 2.1 success criteria 1.4.4 Resize text (Level AA). An alternative way to enlarge text has been provided within the app. This option is available within the App settings

Meaningful links and buttons

Some links are not recognised and announced as links by screen readers. This makes it difficult for screen reader users to identify and activate these links. This fails WCAG 2.1 success criteria 4.1.2 Name, Role, Value (Level A) and we aim to resolve this by the end of August 2025.

Some buttons do not provide screen reader users with clear information about the purpose of the button. For example, “download” buttons and “open in browser” buttons do not indicate which document or page they relate to. This fails WCAG 2.1 success criteria 2.4.4  Link Purpose (Level A) and we aim to resolve this by the end of August 2025.

Some buttons do not provide screen reader users with clear information about the button options that are available. This fails WCAG 2.1 success criterion 1.3.1 Info and relationships (Level A) and we aim to resolve this by the end of August 2025.

On clicking the Welcome Screens button on the More screen, the screen reader announces “loading” multiple times. This fails WCAG 2.1 success criterion 1.3.1 Info and relationships (Level A) and we aim to resolve this by the end of August 2025.

The text size changer provides three ‘A’ icons in different sizes, but the screen reader announces these all as “A” which is not clear for the screen reader user. This fails WCAG 2.1 success criterion 2.4.6 Headings and labels (Level AA) and we aim to resolve this by the end of August 2025.

Headings and titles

Some hidden elements within header bars, such as the progress bar in a study topic when the progress bar is collapsed, have been hidden from view but are still announced by the screen reader. This fails  WCAG 2.1 success criterion 1.3.1 Info and relationships (Level A) and we aim to resolve this by the end of August 2025

Some page titles, such as More, are confusing for screen reader users as they are not a clickable element and users cannot obtain more information by activating it. This fails WCAG success criterion 2.4.2  Page titled (Level A) and we aim to resolve this by the end of August 2025.

Focus order

Some parts of the app do not provide a meaningful focus order. This makes them difficult to navigate by tabbing with a keyboard and difficult to use with screen readers. For example, the menu to filter module status on the Home screen requires the user to tab twice to focus on the next element after the button. This fails WCAG 2.1 success criteria 2.4.3  Focus Order (Level A) and we aim to resolve this by the end of August 2025.

Some links are not focusable with screen readers, such as links within Assessment Strategy and Assessment Guide. This fails WCAG 2.1 success criterion 2.1.1 Keyboard (Level A) and we aim to resolve this by the end of August 2025.

Some pop-up menus are currently difficult to use with screen readers because the focus is not taken into the menu when it opens. It is possible to get focus into the menu but first you need to swipe through content on the main screen. This fails WCAG 2.1 success criteria 2.4.3 Focus Order (Level A) and we aim to resolve this by the end of August 2025.

Colour contrast

The progress bar on the Planner does not provide sufficient contrast with its background. This fails WCAG 2.1 success criterion 1.4.3 Contrast (Minimum) (Level AA) and we aim to resolve this by the end of August 2025.

Gestures

Some content is out of reach when scrolling using screen reader scroll gestures. This fails WCAG 2.1 success criterion 2.5.1 Pointer Gestures (Level A) and we aim to resolve this by the end of August 2025.

Target size

Various clickable elements such as links, edit fields, time and date pickers, slider controls and buttons are not large enough. This fails WCAG 2.1 success criteria 2.5.5 Target Size (Level AAA) and we aim to resolve this by the end of August 2025.

(Note: WCAG 2.1 Success Criteria 2.5.5 Target size is a Level AAA criterion, and we are not required to support this as part of the Public Sector Bodies Accessibility Regulations. However, we believe that this is an important aspect of app accessibility and so we have included this in our accessibility testing for apps).

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

The following types of content may not always be accessible, and they are not included within the scope of the accessibility regulation.

Video and audio

Wherever possible we provide transcripts for audio, and captions, audio descriptions and transcripts for video. Sometimes these alternatives are not available. Pre-recorded time-based media published before 23rd September 2020 is exempt from meeting the accessibility regulations.

Live audio and video

Adding captions to all live video streams is exempt from meeting the accessibility regulations.

PDFs and other documents

PDFs or other documents that are not essential to providing our services and were published before 23rd September 2018 are exempt from meeting the accessibility regulations. We are working to ensure that any new PDFs or other documents that we publish will meet accessibility standards. 

Maps

Online maps and mapping services are exempt from meeting the accessibility regulations. 

Third party content not within OU control

Third party content that is not funded, developed by, or under the control of the OU is exempt from meeting the accessibility regulations. 

Preparation of this accessibility statement

This statement was prepared on 20 December 2024. It was last reviewed on 20 December 2024.

This app was last tested on 6 April 2023. The testing was carried out by the Accessibility and Usability Evaluation Team at The Open University.

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

Feedback and contact information

If you find that a certain section of our app 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 ongoing advice and guidance.

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).