Website accessibility statement

Accessibility statements for our digital services

The accessibility statement on this page explains how accessible the University of Derby website is and how we audit it. As a University we operate a range of systems which will each have their own Accessibility Statement. Read our other accessibility statements

Using this website

This website is run by the University of Derby. We want as many people as possible to be able to use this website and are committed to ensuring digital accessibility for people with disabilities. For example, that means you should be able to:

We have also made the website text easy to understand.

We were sixth in the March 2022 Silktide Index of 157 UK university websites with a score of 92%. The monthly index is based on automated tests carried out on a random selection of 125 of our 6,000 pages for accessibility against Web Content Accessibility Guidelines (WCAG) version 2.1. Our overall Silktide accessibility score for the full site is 94%, scoring at 95% for level A, 94% for AA and 93% for AAA. 

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

Measures to support accessibility

We are using the following measures to ensure accessibility of the University of Derby website:

We tested our website for accessibility during the design process, for example with a partially sighted student, and we carry out similar testing on the live site.

How accessible is our website?

We know some parts of this website aren't fully accessible:

What to do if you can't access parts of this website

We’re always looking to improve the accessibility of this website. Please contact us using our accessibility support form (linked below) if you:

Submit an accessibility support request 

We’ll consider your request and get back to you in two 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, contact the Equality Advisory and Support Service (EASS).

Technical information about our website's accessibility

The University of Derby is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

There are a few instances where keyboard-only users or users of assistive technology may experience an unexpected focus order when they open up hidden content or modal dialogs. This doesn't meet WCAG 2.1 success criterion 2.4.3 (focus order). We are working with AbilityNet to resolve this issue.

There are a few instances where keyboard-only users may not be able to access all the content, for instance within the Virtual Open Days area and in our privacy preference centre modal window. This doesn't meet WCAG 2.1 success criterion 2.1.1 (keyboard). We are looking at a solution for this issue.

Keyboard-only users cannot 'skip to main content' on our Virtual Open Days pages. This doesn't meet WCAG 2.1 success criterion 2.4.1 (bypass blocks). This content was developed by an external supplier. We are looking at a solution for this issue.

There are a few instances on our Virtual Open Days where two adjacent links point to the same destination. This doesn't meet WCAG 2.1 success criterion 1.1.1 (non-text content). This content was developed by an external supplier. We are looking at a solution for this issue.

Some of our PDFs and other documents published after 23 September 2018 - or published before that date but essential for administrative processes - don't fully meet accessibility requirements. We are working through these documents to ensure their content will be accessible or that an accessible alternative is available.

Keyboard-only users may have difficulty tabbing past the search panel at the top of each page. The search panel opens automatically when it is given focus and without any further input from the user. The panel then remains visible when it has been dismissed meaning the content behind it cannot be seen. This doesn't meet WCAG 2.1 success criteria 3.2.1 (on focus) and 2.4.3 (focus order). We are looking at a solution for this issue as a priority.

Some error messages on forms are not associated with their form controls, which means some assistive technology users may not fully understand the content. This doesn't meet WCAG 2.1 success criterion 1.3.1 (information and relationships). We are working with AbilityNet to resolve this issue.

Some title elements, for instance on search listings, are not marked up as headings or with the correct heading level, which means some assistive technology users may not fully understand the content. This doesn't meet WCAG 2.1 success criterion 1.3.1 (information and relationships). We are working with AbilityNet to resolve this issue.

There is some loss of content and functionality at 400% browser zoom on smaller screens, for instance in the home page course search. This doesn't meet WCAG 2.1 success criterion 1.4.10 (reflow). We are working with AbilityNet to resolve this issue.

When the page is resized to 400%, the ‘sticky’ yellow (or blue) main call-to-action button obscures content on the page. This doesn't meet WCAG 2.1 success criterion 1.4.10 (reflow).  Our developers are investigating this issue and expect to have a solution by June 2022. 

There is insufficient colour contrast on focused form elements. This doesn't meet WCAG 2.1 success criterion 1.4.11 (non-text contrast). We are working with AbilityNet to resolve this issue.

Pages with search filters reload on checkbox selection, which may be unexpected behaviour for some users. This doesn't meet WCAG 2.1 success criterion 3.2.2 (on input). We are working with AbilityNet to resolve this issue.

Some assistive technology users may not perceive the purpose and operation of some accordion controls. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

Some assistive-technology users may not perceive the purpose and operation of suggestions displayed when they enter information into a search field as they are not programmatically determined. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

Some interactive components, such as the close icon button on our section menu, lack an accessible role and name and assistive-technology users may not perceive their purpose and operation. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

A number of interactive components, such as the 'In this section' menu, do not declare their expanded or collapsed state and assistive-technology users may not perceive their purpose and operation. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

The focus on the ‘In this section’ menu header is not clear for keyboard users. This doesn't meet WCAG 2.1 success criteria 2.4.7 (focus visible), 2.4.4 (link purpose (in context)) and 4.1.2 (name, role, value). Our developers are investigating this issue and expect to have a solution by June 2022.

The currently active page in a multi-page list is not programmatically determined and this may confuse or mislead users of assistive technology. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

Some visually hidden content, for instance in our course modules, is exposed to assistive technology users. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value). We are working with AbilityNet to resolve this issue.

There are a number of parsing (coding) issues, including elements with duplicate attributes, which can affect accessibility technology. This doesn't meet WCAG 2.1 success criterion 4.1.1 (parsing). We are looking at a solution for this issue.

The focus is not visible for keyboard users when they initially tab through the content in the ‘Updates’ and ‘Research at Derby’ carousels on the Home page. This doesn't meet WCAG 2.1 success criterion 2.4.7 (focus visible). Our developers are investigating this issue and expect to have a solution by June 2022.

The ‘next’ arrows on our carousels on the ‘Updates’ and ‘Research at Derby’ carousels on the Home page do not have discernible text and therefore their purpose is not clear. This doesn't meet WCAG 2.1 success criteria 2.4.4 (link purpose (in context)) and 4.1.2 (name, role, value). Our developers are investigating this issue and expect to have a solution by June 2022.

Most of our new videos (produced after 23 September 2020) do not have audio descriptions. This doesn't meet WCAG 2.1 success criterion 1.2.5 (Audio Description (Prerecorded)). We have assessed the provision of audio description at this time as a disproportionate burden. Please see the following section.

Disproportionate burden

New videos (produced after 23 September 2020) will have captions and transcripts but, for now, they will not be accompanied with synchronised audio descriptions as standard. This doesn't meet WCAG 2.1 success criterion 1.2.5 (Audio Description (Prerecorded). We have assessed the provision of audio description at this time as a disproportionate burden. This is based on a number of factors, including: the large number of videos produced; the changeable nature of the content; and the resource and/or costs attached to production.

This decision follows a review of audio description suppliers and our ability to create audio description ourselves. We will periodically review the market for audio description services to assess our ability to introduce audio description on our videos at a later date. In the meantime, if the closed captions and extended transcripts currently provided do not meet an individual’s accessibility requirements, an audio-described version can be made available by request for a specified video.

Please complete the accessibility support form, clearly stating for which video the audio description is required. We will aim to produce the audio description file within 15 working days of receiving the request.

Content that’s not within the scope of the accessibility regulations
PDFs and other documents

Many of our older PDFs and Word documents don't meet accessibility standards. For example, they may not be marked up so they are accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value). The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential for active administrative processes. Any new PDFs or Word documents we publish will meet accessibility standards.

Video captions

Some of our older videos don't have accurate edited captions or transcripts. This doesn’t meet WCAG 2.1 success criterion 1.2.1 (audio-only and video-only pre-recorded), 1.2.2 (captions pre-recorded), 1.2.3 (audio description or media alternative pre-recorded) and 1.2.5 (audio description pre-recorded). The regulations do not apply to recorded videos published before 23 September 2020. However, while these videos are not subject to the legislation, we have carried out an audit of all our videos and have begun a process of updating captions and adding full transcripts. Any new videos we publish will have edited captions and transcripts.

Live video

Our live video streams don't have captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 (captions live). We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. However, we will add captions when we embed an edited version of the video streams on our website.

Maps

Our online maps, for instance in our Virtual Open Days area, are not fully accessible for keyboard-only users. This doesn't meet WCAG 2.1 success criterion 2.1.1 (keyboard). Some of our maps do not provide sufficient contrast for visually impaired users. This doesn't meet WCAG 2.1 success criterion 1.4.11 (non-text contrast). Our online maps are exempt from meeting the accessibility regulations. This is third-party content that is neither funded nor developed by us, nor under our control.

Discover Uni

The colour contrast of the text on the Discover Uni statistics panels does not have sufficient colour contrast for visually impaired users. This doesn't meet WCAG 2.1 success criterion 1.4.3 (contrast (minimum)). Also there is no way to control the animation within the Discover Uni panels. This doesn't meet WCAG 2.1 success criterion 2.2.2 (pause, stop, hide). The Discover Uni panels are exempt from meeting the accessibility regulations. This is third-party content that is neither funded nor developed by us, nor under our control. 

Text in forms

Text within forms does not respond on text spacing. This doesn't meet WCAG 2.1 success criterion 1.4.12 (text spacing). The text styling within forms is exempt from meeting the accessibility regulations. This is third-party content that is neither funded nor developed by us, nor under our control. 

Messenger 

Users are unable to use a keyboard to usefully access the Messenger "Hi! How can we help you?" chat box. It is possible to tab to the chat box but there is no indication that it has focus. This doesn't meet WCAG 2.1 success criterion 2.1.1 (keyboard).  

Also, the Messenger frames do not have useful title attribute values. This doesn't meet WCAG 2.1 success criterion 2.4.1 (bypass blocks) and 4.1.2 (name, role, value).  

And, when the page is resized to 400%, the Messenger chat box and button obscure content on the page. It is possible to remove the chat box by clicking on the “-” but not the logo/button. This doesn't meet WCAG 2.1 success criterion 1.4.10 (reflow).  

The Messenger platform is exempt from meeting the accessibility regulations. This is third-party content that is neither funded nor developed by us, nor under our control. 

Additional accessibility considerations

The Web Content Accessibility Guidelines (WCAG) define three levels of conformance: level A, level AA and level AAA. Although our goal is WCAG 2.1 Level AA conformance, we have also applied some level AAA success criteria:

How we tested this website

This website was last tested on 9 March 2022 by the Central Digital and Data Office. This involved a review of seven pages, using manual checks and automated tests using the latest version of Axe. All our pages are also tested each week by the Silktide platform, which makes automated checks of 6,000 pages against the W3C (World Wide Web Consortium) WCAG 2.1 accessibility standards using automated testing techniques. 

A sample of the site has been tested by a visually impaired user.

What we’re doing to improve accessibility

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

This statement was prepared on 30 July, 2019. It was last reviewed on 29 March, 2021.

Campus accessibility

Please see our campus accessibility guides for detailed online access guides for our campuses and sites.

We first prepared this statement on 30 July, 2019. We are logging every change we make to this page.

  • 30 July, 2019: statement first published
  • 20 September, 2019: updated latest test and Sitemorse results and linked to new form for users to report issues
  • 14 September, 2020: updated with latest test information from Silktide, Accessibility Insights for Web, Accessibility Insights for Windows and Sitemorse quarterly results
  • 6 October, 2020: updated with information about audio descriptions on new videos
  • 19 February 2021: updated with latest information from Silktide (including the Silktide Index) and Sitemorse quarterly results
  • 15 March 2021: updated with disproportionate burden statement and latest information from Silktide
  • 13 July 2021: updated with latest information from AbilityNet review
  • 29 March 2022: updated with latest information from Central Digital and Data Office review