Accessibility Statement for Chinese@OU

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 Android version 2.2 and iOS version 2.2 of the Chinese@OU 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 (note the app is restricted to landscape orientation).
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. (note limitations as described below).
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.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

Screen reader use

The app is not accessible to non-sighted users as it is not compatible with the native screen reader. We are unable to verify if the app meets WCAG 2.2 success criterion 1.1.1 (Non-text content), WCAG 2.2 success criterion 1.3.1 (Info and Relationships), WCAG 2.2 success criterion 2.4.6 (Headings and Labels), WCAG 2.2 success criterion 2.5.3 (Label in Name), WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). 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).

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

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

Structure

To a visual user the app is well-structured and consistent. However, as the app is not compatible with the native screen reader or with an external keyboard it is not possible to test if the app fully meets WCAG 2.2 success criterion 1.3.1 (Info and Relationships). 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, and some sections require users to see a specific Chinese character or characters and then select an English equivalent from a list of options provided (e.g., in Reading Test). These elements are not described for users with visual impairment, and the app is not compatible with the native screen reader. 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 app is not compatible with the native screen reader, so links are not announced. 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 and sensory characteristics

Some of the information and on-screen instructions rely on or refer to colour, shape, audio or visual location. For example, correct/incorrect answers are sometimes shown only by a change of colour. Some instructions are in audio form. This fails WCAG 2.2 success criterion 1.3.3 (Sensory Characteristics) and 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

The ‘Toggle’ button in the settings does not have sufficient contrast with the background (all Themes). The ‘Delete’ icon does not have sufficient contrast with the background (all Themes). In the Night Sky Theme there is insufficient contrast between the text and the button background. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)) and 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).

Pointer Gestures

The Writing activity in this app provides users with the opportunity to practise drawing Chinese characters on a screen using their fingers. This requires strokes to be drawn in a particular order and position, however this activity is for practice only. Users unable to draw the characters on the screen can still watch them being drawn in the model provided. This fails WCAG 2.2 success criterion 2.5.1 (Pointer Gestures) but is considered an exception due to path-based gestures being essential for this activity.

The Writing activity also requires the user to slide a horizontal menu. This fails WCAG 2.2 success criterion 2.5.1 (Pointer Gestures). 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).

Dragging Movements

The Word Search activity can only be completed using dragging movements. Note: you are able to reveal the correct answers without completing the grid.

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. Some of the buttons are small and close together, 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).

Pointer Cancellation

Links are activated on the down event. This fails WCAG 2.2 success criterion 2.5.2 (Pointer Cancellation) 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).

Orientation

The App is restricted to landscape orientation. This fails WCAG 2.2 success criterion 1.3.4 (Orientation) 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).

Alternative versions of the activities can be found on the Alternative Formats page.

Preparation of this accessibility statement

This statement was prepared on 14/04/23. It was last reviewed on 24/10/24.

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

The sample used for testing consisted of pages from within each activity type. 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

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