Accessibility Statement for stats.digitalresources.jisc.ac.uk

This accessibility statement applies to statistics.digitalresources.jisc.ac.uk(also using the URL https://stats.ukdataservice.ac.uk/).

This website is run by Jisc (as a partner in the UK Data Service). We want as many people as possible to be able to use this able to use this website. For example, that means you should be able to:

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

How to request content in an accessible format

If you are unable to access the data or information on this website then we will work with you to get your requests to you in a suitable format:

We will get back in touch with you within 7 days to work out how best we can respond to your request.

If you cannot get through on the above phone number, please leave a voicemail - we are checking our voicemail regularly.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems that aren't listed on this page or think we're not meeting accessibility requirements, contact our Marketing and Communications Manager on 01206 872001 or by email: comms@ukdataservice.ac.uk.

Enforcement procedure

If you contact us with a complaint and you are not happy with our response contact the Equality Advisory and Support Service (EASS).

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).

Technical information about this website’s accessibility

Jisc is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

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

Disproportionate Burden

This section covers issues that we cannot fix right now. We have assessed the cost of fixing these issues but believe that doing so would be a disproportionate burden within the meaning of the law.

https://stats2.digitalresources.jisc.ac.uk runs on the OECD .Stat platform, a third party software. Some parts of .Stat we are not able to fix, however, we will work with the .Stat developers to highlight and fix issues wherever possible.

Some of the default icons have very low contrast, meaning that they are difficult for people with low vision to see. This This fails WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)).

Text does not reflow to match smaller screen sizes or zooming in to 200% and above. This means we do not meet WCAG 2.1 success criterion 1.4.10 (Reflow).

Some of our pages have Headings that skip a level (from H2 to H4), this makes it difficult users of assistive technology to navigate. This means we fail WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 2.4.1 (Bypass Blocks) and 2.4.6 (Headings and Labels). We do not at the present time have the ability to change these tags, this code is generated by .Stat.

Some of our images contain alternative text that is unhelpful or missing. These images are default link logos created by .Stat, we cannot edit or restyle them ourselves. This means we fail WCAG 2.1 success criterion 1.1.1 (Non-Text Content). We will bring this to the attention of the developers and ask them to make changes.

We have some 'onmouseover' events that do not have a corresponding keyboard equivalent. This means that keyboard users are not being treated the same. This means we do not meet WCAG 2.1 success criterion 2.1.1 (Keyboard). We will bring this to the attention of the developers and ask them to make changes.

Some of our forms are not labelled. This means we fail WCAG 2.1 success criterion 2.4.6 (Headings and Labels) and 1.1.1 (Non-text Content) and 3.3.2 (Labels or instructions). We will bring this to the attention of the developers and ask them to make changes.

We have not marked up the web pages into a proper structure and/or identification of page regions/landmarks to aid navigation. This means we do not meet WCAG 2.1 success criterion 2.4.1 (Bypass blocks). We will bring this to the attention of the developers and ask them to make changes.

We have used a table layout to position text whereas tables should be for presenting tabular data. This means we do not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) and 1.3.2 (Meaningful Sequence). We will bring this to the attention of the developers and ask them to make changes.

We have table header elements that contain no text, this means screen reader users may not understand the context of tables. This means we do not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We will bring this to the attention of the developers and ask them to make changes.

Using a keyboard you cannot easily navigate the dataset lists or the charts, this makes it very difficult for keyboard users to access the data. This means we do not meet WCAG 2.1 success criterion 2.1.1 (Keyboard). We will bring this to the attention of the developers and ask them to make changes.

Some of our images contain alternative text that is unhelpful or missing. These images are default link logos created by .Stat, we cannot edit or restyle them ourselves. This means we fail WCAG 2.1 success criterion 1.1.1 (Non-Text Content). We will bring this to the attention of the developers and ask them to make changes.

Although we have suitable titles, when moving from one dataset to another dataset title tag does not update. This means we fail WCAG 2.1 success criterion 2.4.2 (Page Titles). We will bring this to the attention of the developers and ask them to make changes.

Some of our links contain repeated links (adjacent links go to the same URL). This means we fail WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)). We will ensure that links do not repeat where possible.

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

Third Party Content

Our website contains third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third party to improve its accessibility. This may include:

What we are doing to improve accessibility

We will be working on tackling the accessibility issues listed above by talking to the developers and making them aware of the issues.

Preparation of this accessibility statement

This statement was prepared on 28 July 2023.

This website was last tested on 28 July 2023. The test was carried out by the UKDS ADU team.

Content modified from the GOV.UK accessibility statement - used through the Open Government Licence v3.0.