Online Store accessibility statement

Using this website

The University of Derby Online Store (unishop.derby.ac.uk) website is run by WPM Education on behalf of the University of Derby. We want as many people as possible to be able to use the site 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
  • Navigate most of the website using just a keyboard
  • 'Skip to main content' using tab on your keyboard
  • Listen to most of the website using a screen reader
  • Navigate our online forms using just a keyboard

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 Online Store website:

  • We include accessibility within our internal policies
  • We assign clear accessibility targets and responsibilities
  • We employ formal accessibility quality assurance methods

How accessible is our website? 

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

  • Some page elements do not have enough colour contrast
  • Some pages do not have the language specified
  • Not all form elements have labels
  • Not all links have accessible text
  • The table headers attribute is not exclusively used to refer to other cells in the table
  • Some pages have multiple static elements with the same id attribute

What to do if you can't access parts of this website or have a complaint 

We’re always looking to improve the accessibility of this website.  

If you have any issues with inaccessible content or are unable to obtain an accessible version, or you feel the need to complain about our site and content accessibility, please email us at onlineshop@derby.ac.uk  or contact us via our central feedback form. 

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 after following the process set out above, 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 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

There are some elements that do not provide enough colour contrast between text and its background so that it may be difficult to be read by people with moderately low vision (who do not use contrast-enhancing assistive technology). This doesn’t meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). We are working with our suppliers for a solution to this issue.

Some HTML documents do not have a lang (language) attribute. If the language of a webpage is not specified, the screen reader assumes the default language set by the user. Language settings become an issue for users who speak multiple languages and access website in more than one language. It is essential to specify a language and ensure that it is valid, so website text is pronounced correctly. This doesn’t meet WCAG 2.1 success criterion 3.1.1 Language of Page. We are working with our suppliers for a solution to this issue.

Some Form elements do not have labels. The purpose of form elements such as checkboxes, radio buttons, input fields, etc, is often apparent to sighted users, even if the form element is not programmatically labelled. Screen readers users require useful form labels to identify form fields. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships and 3.3.2 Labels or Instructions. We are working with our suppliers for a solution to this issue.

Some links do not have discernible text. Text helps users understand the purpose of each link so they can decide whether they want to follow the link. Whenever possible, provide link text that identifies the purpose of the link without needing additional context. Assistive technology has the ability to provide users with a list of links that are on the web page. Link text that is as meaningful as possible will aid users who want to choose from this list of links. Meaningful link text also helps those who wish to tab from link to link. Meaningful links help users choose which links to follow without requiring complicated strategies to understand the page. This doesn’t meet WCAG 2.1 success criterion 1 4.1.2 Name, Role, Value and 2.4.4 Link Purpose (In Context). We are working with our suppliers for a solution to this issue.

Some table elements that use the headers attribute may not refer to other cells of that same table. Screen readers have a specific way of announcing tables. When tables are not properly marked up, this creates the opportunity for confusing or inaccurate screen reader output. Sighted users can usually tell at a glance what the table's headers are and what their relationship to the data is. For non-sighted users this must be done in the markup. This doesn’t meet WCAG 2.1 success criterion 1.3.1: Info and Relationships. We are working with our suppliers for a solution to this issue.

Some ID attribute values are not unique. The ID attribute uniquely identifies elements on a page. It does not make sense to duplicate an ID. Duplicate IDs can break the accessibility of labels for forms, table header cells, etc, by the second instance being skipped by screen readers, or by client-side scripts. This doesn’t meet WCAG 2.1 success criterion 4.1.1 Parsing. We are working with our suppliers for a solution to this issue.

Disproportionate burden

Our Supplier is aware of the of new accessibility requirements for public sector bodies, specifically in relation to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, as well as the Equality Act 2010.

The deadline for these changes is 23 September 2020 for pre-existing websites, and they are working to ensure any required changes are implemented well in advance of this date. They are continually releasing changes to the platform, many of which are designed to improve accessibility as well as functionality.

We will ensure new accessibility requirements are requisite criteria when the system is comes up for review.

Content that’s not within the scope of the accessibility regulations. 

We are not aware of any content that falls outside the scope of the accessibility regulations.  

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 as follows:

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

How we tested this website

This website was last tested on 18 December 2019. The test was carried out on a sample of 12 pages using the Accessibility Insights for Web add-on, which checks our content against the W3C (World Wide Web Consortium) WCAG 2.1 and Digital ADA (Americans with Disabilities Act) accessibility standards.

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 18 December 2019. It was last updated on 18 December 2019.

Website accessibility information form 

You can contact us in via our central feedback form.

Submit an accessibility support request

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

  • 11 August, 2020: statement first published