UDo mobile application accessibility statement

The UDo mobile application is a portal that enables students and staff to access a range of content and services.

UDo is built on the CampusM platform, supplied by Ex Libris, who are part of the ProQuest group. ProQuest are working to improve the accessibility of the content upload tools, the framework of the mobile application and the core user interface.

The accessibility of the content and any bespoke inhouse development in the mobile application is overseen by the University of Derby Portal and Application Development Team and content editors.

Using this mobile application

The UDo mobile application is run by the University of Derby. We want as many people as possible to be able to use the app and are committed to ensuring digital accessibility for people with disabilities. For example, that means:

AbilityNet has advice on making your device easier to use if you have a disability. AbilityNet is a UK (United Kingdom) charity that exists to change the lives of disabled people by helping them to use digital technology at work, at home or in education.

How accessible is this mobile application?

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

What to do if you cannot access parts of this mobile application or have a complaint

We are always looking to improve the accessibility of this mobile application. If you have any issues with inaccessible content, are unable to obtain an accessible version, or you feel the need to complain about our site and content accessibility, please contact us in the first instance via our central feedback form.

Submit an accessibility support request

The Portal and Application Development Team are responsible for reviewing accessibility support requests. You can contact the team directly via itservicecentre@derby.ac.uk.

You can contact us about any issues, for example, if you:

We will consider your request and get back to you in 5-10 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint after following the process set out above, contact the Equality Advisory and Support Service (EASS).

Technical information about our mobile application's accessibility

ProQuest, the third-party supplier, are working to improve accessibility of the CampusM platform. You can find out more about the platforms accessibility review and read the core platform accessibility statement online:

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

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

Non-accessible content

Content within the mobile application is created and maintained by content editors, who are responsible for creating accessible content. There is currently no mechanism to automatically check the accessibility of content, therefore it is possible for content with accessibility issues to be published. For example:

Some content has been created using Microsoft Sway. This content can include common accessibility issues previously mentioned. The Sway platform has features that by default go against accessibility best practice such as horizontal scrolling and moving content. These features can be turned off using Sway’s accessibility mode. Sway is part of Office 365; you can find out more about its accessibility in the Microsoft office 365 accessibility statement (requires login).

Non-compliance with the accessibility regulations

We are in the initial stages of planning to resolve these issues, see what we are doing to improve accessibility.

Disproportionate burden

CampusM is under an existing contract. The platform is provided and updated by the third-party supplier; we continue to work with them to improve the accessibility of the current platform. As systems are reviewed, we will access the options available to improve the accessibility.

How we tested this mobile application

This mobile application was last tested on 20 May 2021. This involved testing a sample of several types of content within the mobile application using:

What we are doing to improve accessibility

We have a rolling programme of updating content in accordance with the guidelines set out by the WCAG. This includes:

Preparation of this accessibility statement

This statement was prepared on 18 June 2021. It was last reviewed on 18 June 2021.

We are logging every change we make to this page, including dates and what has changed.

  • 18 June, 2021: statement first published