Accessibility Statement for The Human Heart - 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 2.0.4 of the Human Heart mobile application.

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 (by using system zoom to magnify the screen).
Increase the display size (by using system zoom to magnify the screen).
Tab through the content; the current location will be indicated by a clear visual change (note limitations on keyboard accessibility as described below).
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 (note limitations as described below).
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. There is an in-built screen reader (note limitations as described below) that will read content when tapped on directly.
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

A PC version which provides further (but not fully compliant) accessibility options is also available.

AR Mode

The Augmented Reality (AR) option within the app requires users to point the device camera at a ‘trigger image’ to launch it and maintain the camera over the trigger image to interact with the content. This fails WCAG 2.2 success criterion 2.5.4 (Motion Actuation) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

However, all learning material within the AR option of the app is provided in the Standard and Accessibility modes.

Screen reader use

The app is not accessible to non-sighted users. In Accessibility mode, the app has a built-in screen reader which cannot be customised or controlled by the user.

The app is not compatible with the native IOS screen reader (VoiceOver) and users will need to turn VoiceOver off to be able to activate any of the app buttons and to allow the built-in screen reader to read. Students may not be able to exit the app if they don't have a shortcut set up to turn VoiceOver on/off.

The built-in screen reader cannot be operated using the standard VoiceOver gestures. Users need to tap buttons and selectable options to get the built-in screen reader to read them.

This will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Descriptions of content

The app is highly visual, some elements are not sufficiently described for users with visual impairment. For example, the structures and functions of the heart, the Show Blood Flow animation and Show Cycle animation. ‘Play Heartbeat’ option is visual but currently has no sound. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Links

The built-in screen reader does not announce links.

This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships), WCAG 2.2 success criterion 2.4.4 (Link purpose) and WCAG 2.2 success criterion 4.1.2 (Name, Role, Value) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Use of colour

Pins to show the current selection rely on colour alone to identify information. Flow of blood animation relies on coloured arrows. The ECG uses colour to portray information. This fails WCAG 2.2 success criterion 1.4.1 (Use of colour) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Contrast

Contrast between pins and the heart model is not high enough in some areas. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Use of keyboard

The app is not compatible with an external keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard), WCAG 2.2 success criterion 2.1.2 (No Keyboard Trap), WCAG 2.2 success criterion 2.4.3 (Focus Order), WCAG 2.2 success criterion 2.4.7 (Focus Visible). We are unable to verify if the app meets WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence) or WCAG 2.2 success criterion 2.4.11 (Focus not obscured (minimum)). Depending on the position of the model, focusable elements may be hidden and can only be brought into focus by rotating the model. However, the information provided by each pin can be accessed by using the previous and next buttons after the 'Show pins' option is activated.

This will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Pointer Gestures

A two-finger swipe is required to move the Heart model. This fails WCAG 2.2 success criterion 2.5.1 (Pointer gestures) and will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Dragging Movements

The model can only be rotated using dragging movements. This fails WCAG 2.2 success criterion 2.5.7 (Dragging movements). This will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

Target Size

Due to the development environment used to create the app, we are unable to verify the exact size of the menu buttons and other targets. Depending on the position of the model, pins can be very close together or overlapping, therefore this is likely to fail WCAG 2.2 success criterion 2.5.8 (Target size (minimum)). This will be reviewed following the release of an update to the development environment which should provide improved accessibility support (expected to be end of 2024).

However, the information provided by each pin can be accessed by using the previous and next buttons after the 'Show pins' option is activated.

A PC version which provides further (but not fully compliant) accessibility options is also available.

Preparation of this accessibility statement

This statement was prepared on 17/02/22. This statement was last reviewed on 24/10/24.

This mobile app was last tested on 09/10/24. The testing was carried out by the Technical Testing Team, Learner and Discovery Services (LDS).

The app is not page-based. Manual testing was carried out to evaluate its compliance as a whole against WCAG 2.2.

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

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 and apps, you should raise a complaint via the complaints and appeals process.

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

Explore our app stores

Google Play Apple store