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:
- Zoom in up to 500% without the text spilling off the screen (for instance using Ctrl and +)
- Navigate most of the website using just a keyboard
- 'Skip to main content' using tab on your keyboard on most of our pages
- Listen to most of the website using a screen reader
- Navigate our online forms using just a keyboard
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 seven of the last eight quarters. The index scores higher education websites in the UK for a variety of quality indicators, including for accessibility, based on a random selection of 125 of our more than 5,000 pages. We are the Sitemorse Accessibility Rockstar of the Year among UK and Irish universities, with a ranking of 8 out of ten.
However, we have dropped out of the top 30 in the monthly Silktide Index, which also tests a random selection of 125 of our more than 5,000 pages for accessibility. The selection of pages were scored against Web Content Accessibility Guidelines (WCAG) version 2.1 at 82% for level A, 62% for AA and 62% 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 include accessibility within our internal policies
- We assign clear accessibility targets and responsibilities
- We employ formal accessibility quality assurance methods
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:
- Some PDF documents aren't fully accessible to screen reader software
- Some of our older videos don't have captions
- Keyboard-only users may find it difficult to access all of our content, for instance on a few of our Virtual Open Day pages
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:
- Need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille
- Can’t view the map on our ‘contact us’ page
- Find any problems that are not listed on this page
- Think we are not meeting the requirements of the accessibility regulations
Submit an accessibility support request
We’ll consider your request and get back to you in two 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, 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.
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 may experience an unexpected focus order when they open up hidden content. This doesn't meet WCAG 2.1 success criterion 2.4.3 (focus order). We are looking at a solution for 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). 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). 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.
The main search field at the top of every page does not change appearance when selected. This doesn't meet WCAG 2.1 success criterion 2.4.7 (focus visible). We are looking at a solution for this issue.
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.
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.
Some of our new videos (produced after 23 September 2020) do not yet have audio descriptions. This doesn't meet WCAG 2.1 success criterion 1.2.5 (Audio Description (Prerecorded)). Audio descriptions are being produced for all these videos where relevant and will be added as soon as they are ready.
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.
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.
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.
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.
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:
- Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed
- We are adding full transcripts to our videos
- Functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes
- Information about the user's location within a set of web pages is available
- The purpose of each link can be identified from link text alone, except where the purpose of the link would be ambiguous to users in general
- Section headings are used to organise the content
- We provide easy-read alternatives to technically advanced text
How we tested this website
This website was last tested on 14 September 2020. All our pages are tested each week by the Silktide platform, which checks the content on our 5,000-plus pages against the W3C (World Wide Web Consortium) WCAG 2.1 accessibility standards using automated testing techniques. The pages were found to be 82% compliant on level A, 79% compliant on AA and 78% compliant on AAA.
A sample of the site has been tested by a visually impaired user and we also tested a random sample of pages manually using Accessibility Insights for Web and Accessibility Insights for Windows.
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:
- Working through our existing PDFs and replacing them with HTML web pages or accessible alternatives
- Replacing document programme specifications on course pages with on-page HTML content
- A training programme for website contributors and moderators on how to build accessible web pages
- An accessibility taskforce using the Silktide platform to identify and address accessibility issues
- Working on functionality to include audio description on all applicable videos uploaded on or after 23 September 2020
This statement was prepared on 30 July, 2019. It was last updated on 6 October, 2020.