The UDo web application is a web version of the native University app. It 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 web application and the core user interface.
The accessibility of the content and any bespoke inhouse development in the web application is overseen by the University of Derby Portal and Application Development Team and content editors.
Using this web application
The UDo web 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:
- Most content that is communicated visually is available to assistive technologies
- If styling is removed, most content should remain in a logical order
- Where possible, we have tried to avoid using visual characteristics to communicate information
- Where possible, we have avoided using colour as the only way to convey some information
- Most content is fully usable when text is enlarged up to 200%
- Page content will sometimes resize to a single column with no horizontal and vertical scrolling
- Many important graphical objects, interface components, and states have a colour contrast of 3:1
- Line height, spacing between paragraphs and letter and word spacing can often be changed without breaking anything
- Where extra content is shown or hidden on focus, it can often be dismissed, interacted with (and not disappear when the user moves to it) and will stay visible until dismissed by the user
- Most menus, links, buttons, and other controls can be operated by keyboard
- Some blocks of links and other interactive elements may be bypassed by keyboard user
- When using a keyboard to move through a page, the order should make sense
- The web application should have two or more ways of finding content, such as a navigation menu, search feature, or site map
- When using a keyboard to move through a page, you can always tell where you are
- Links, controls or form fields that automatically trigger a change in context have been avoided
- All features with the same functionality are labelled consistently
- Instructions and labels are required to aid user input
- Where appropriate, all HTML tags have start and end tags
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 web application?
We know some parts of this web application are not fully accessible:
- Not all information provided by images have an appropriate text equivalent
- You may not be able to listen to some of the web application using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
- Not all videos have captions that are synchronised with the audio
- Not all videos with important visual information have audio descriptions
- Some text may not have sufficient contrast against the background colour
- There may be some instances where an image of text has been used
- Not all pages have a unique title that indicates its purpose and context
- The purpose of every link may not be clear from its link text
- Headings and labels may not be clear and descriptive
- Some forms may not provide understandable error and verification messages
What to do if you cannot access parts of this web application or have a complaint
We are always looking to improve the accessibility of this web 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 email@example.com.
You can contact us about any issues, for example, if you:
- Find any problems that are not listed on this page
- Think we are not meeting the requirements of the accessibility regulations
We will consider your request and get back to you in 5-10 working days.
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 web 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 web applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This web application is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed.
Content within the web 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:
- Incorrect use of heading levels
- Missing alt text on images
- Ambiguous link text
- Poor colour contrast on text
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
- Not all information provided by images have an appropriate text equivalent. This does not meet WCAG 2.1 success criterion 1.1.1 (non-text content).
- You may not be able to listen to some of the web application using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver). This does not meet WCAG 2.1 success criterion 1.2 (time-based media).
- Not all videos have captions that are synchronised with the audio. This does not meet WCAG 2.1 success criterion 1.2.4 (captions).
- Not all videos with important visual information have audio descriptions. This does not meet WCAG 2.1 success criterion 1.2.5 (audio description).
- Some text may not have sufficient contrast against the background colour. This does not meet WCAG 2.1 success criterion 1.4.3 (contrast minimum).
- There may be some instances where an image of text has been used. This does not meet WCAG 2.1 success criterion 1.4.5 (images of text).
- Not all pages have a unique title that indicates its purpose and context. This does not meet WCAG 2.1 success criterion 2.4.2 (page titled).
- The purpose of every link may not be clear from its link text. This does not meet WCAG 2.1 success criterion 2.4.4 (link purpose).
- Headings and labels may not be clear and descriptive. This does not meet WCAG 2.1 success criterion 2.4.6 (headings and labels).
- Some forms may not provide understandable error and verification messages. This does not meet WCAG 2.1 success criterion 3.3.1 (error identification).
We are in the initial stages of planning to resolve these issues, see what we are doing to improve accessibility.
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 web application
This web application was last tested on 10 May 2021. This involved testing a sample of several types of content within the web application using:
- Accessibility Insights for Web, browser extension for Google Chrome
- VoiceOver screen reader
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:
- Reviewing the training offer for content editors
- Reviewing content governance
- Raising accessibility issues which are part of the platform with the third-party supplier
Preparation of this accessibility statement
This statement was prepared on 18 June 2021. It was last reviewed on 18 June 2021.