E-Journals Finder accessibility statement

Using this website

The EBSCO Full Text Finder (E-Journals Finder) website, one of our Library guides, is run by 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:

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's E-Journals Finder website:

How accessible is our website?

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

We are currently addressing these issues by adding in appropriate alt-text into images and making the background colour darker (in order to make text stand out better on screen).

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 contact us in the first instance via our central accessibility feedback form.

Submit an accessiblity support request

You can also contact the Library directly:

You can contact us about any issues, for example, if you:

We’ll consider your request and get back to you in two to five 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.

Our E-Journals Finder website is not 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

Some images don’t display alt-text for images. This doesn’t meet WCAG 2.1 success criterion 1.1.1. We are looking to add alt-text to all images within E-Journals Finder by September 2020. When we publish new content, we’ll make sure our use of images meets accessibility standards.

Some list elements (li) are not wrapped inside (ul) or (ol) parent elements, making it hard for users with screen readers to determine when they arrive at a list on a page and how many items are in the list. This doesn’t meet WCAG 2.1 success criterion 1.3.1. We are looking at a solution to this issue.

Some form elements within the site currently lack labels. This doesn’t meet WCAG 2.1 success criteria 1.3.1. or 3.3.2. We are looking at a solution to this issue.

Some attributes may not contain focusable elements. This doesn’t meet WCAG 2.1 success criteria 1.3.1. or 4.1.2. We are looking at a solution to this issue.

Some text displayed on tabs and banners aren’t clear. This doesn’t meet WCAG 2.1 success criterion 1.4.3. We are looking at addressing this issue by using a stronger background colour that allows text to be read more clearly.

Some duplicate ID attribute values may break the accessibility of labels for focusable elements such as forms or table header cells. This doesn’t meet WCAG 2.1 success criterion 4.1.1. We are looking at a solution to the issue.

Some ARIA attributes may be unrecognised, causing elements of the platform not to work properly. This doesn’t meet WCAG 2.1 success criterion 4.1.1. We are looking at a solution to the issue.

Some button-names (e.g. drop-down menus) don’t have discernible text. This doesn’t meet WCAG 2.1 success criterion 4.1.2. We are looking at a solution to the issue.

Disproportionate burden

At present, there is nothing we have found that could be considered a ‘disproportionate burden’.

Content that is 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 structured so they’re 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 administration purposes relating to tasks we perform as a Public Body.

However, some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

Any new PDFs or Word documents we publish will meet accessibility standards.

In the meantime, you can always contact us to request a copy that is accessible for you at library@derby.ac.uk and we will do our best to make this available without delay.

Additional accessibility considerations

At present, we’re not aware of additional accessibility considerations for this platform but we will monitor and update this to reflect any changes.

How we tested this website

This website was last tested on 5 November 2019. The test was carried out on a sample of four pages by the University of Derby Libraries. We used the Accessibility Insights for Web add-on, testing in Google Chrome.

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 5 November 2019. It was last updated on 5 November 2019.

Accessibility statement updates log

Going forward, we will be logging all the changes we make to the page, including dates and what has changed.

Website accessibility queries

As previously mentioned, please contact us in the first instance via our central feedback form.

Submit an accessiblity support request

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

  • 20 December, 2019: statement first published