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 have been first in the SiteMorse Index for Higher Education for user experience for the last four quarters. The index scores higher education websites in the UK for a variety of quality indicators including for accessibility. We are currently scoring 9/10 for accessibility.

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 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 listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

While text can be zoomed or magnified, it is not possible for users to modify text spacing or line height. This doesn’t meet WCAG 2.1 success criterion 1.4.12 (text spacing). We are looking at a solution to this issue.

Disproportionate burden

Some of the content on our virtual tour is not accessible due to incomplete markup. This doesn't meet WCAG 2.1 success criterion 4.1.1 (parsing). We intend to reassess this third-party content when we next review this area of the site. Please let us know what information you require and we will try to provide the information in an alternative format.

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.

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 19 September 2019. The test was carried out on a sample of 125 pages by the SiteMorse testing platform, which checks our content against the W3C (World Wide Web Consortium) WCAG 2.1 and Digital ADA (Americans with Disabilities Act) accessibility standards. No priority issues were flagged and the pages were found to be 87% compliant on level A, 99% compliant on AA and 99% compliant on AAA using automated testing techniques. 

A sample of the site has been tested by a visually impaired user and we also test pages using the W3C Website Accessibility Evaluation Report Generator.

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 statement was prepared on 30 July, 2019. It was last updated on 20 September, 2019.

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