Skip to content

Web accessibility statement for Nottingham Trent University

Nottingham Trent University (NTU) is committed to making its websites and mobile applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to Nottingham Trent University’s external website, staff intranet, student intranet.

We want as many people as possible to be able to use these websites. This means you should be able to:

  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the websites using just a keyboard
  • navigate most of the websites using speech recognition software
  • listen to most of the websites using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

Compliance status

These websites are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible due to non-compliance with the accessibility regulations. Where we have content that is not yet accessible, we have an ongoing programme of work that will help us to reach compliance. We release code updates fortnightly and ensure that we are prioritising accessibility fixes within these.

Colour contrast

We have conducted a thorough audit of colour contrasts across our site and have made every effort to choose AA compliant colour contrasts. However there may be occasional instances where inaccessible colour combinations arise which may fail WCAG 2.2 success criteria 1.4.3: Contrast minimum (AA). These issues are dealt with as soon as they are spotted.

PDFs

Most PDF documents uploaded before 23 September 2018 are not fully accessible to screen reader software. We endeavour to ensure that any new PDFs are accessible. To support this, we have developed documentation and delivered training sessions to our website editors.

Videos

Most of our videos include transcripts, but do not include separate audio descriptions. This does mean that provision of video will fall short of the WCAG 2.2 AA standards. Some embedded videos are not captioned or use automatically generated captions which may be inaccurate. These issues fail WCAG 2.2 success criteria 1.2.2 (A), 1.2.3 (A), 1.2.5 (AA).

To improve our compliance in this area, we have developed documentation and delivered training to our website editors.

Text alternatives for images

Some images do not have a text alternative, or the text alternative is unhelpful, so people using a screen reader cannot understand the non-text content. This fails WCAG 2.2 success criteria 1.1.1: non-text content (A).

We have embedded information about how to write alt text in the training that all new editors must undergo before being given access to edit the website, as well as creating resources for our editors to refer to.

Page structure

Some pages may have incorrect heading structures. This fails WCAG 2.2 success criteria 2.4.6: Headings and Labels (AA).

We have embedded information about how to structure headings in the training that all new editors must undergo before being given access to edit the website, as well as creating resources for our editors to refer to. We regularly audit heading levels to correct any errors.

Tables

Some pages contain tables which do not have headers or may use tables for layout purposes. This fails WCAG 2.2 success criteria 1.3.1: Info and Relationships (A).

We have updated our documentation and training materials to ensure publishers are aware of other ways of presenting content and are aware of how to use tables properly if required.

Third-party tools

Our site uses third-party applications which may not be fully accessible. We work to ensure that the content on these applications is accessible, and we are working with our third-party providers to explore the provision of accessible code on their platforms. We endeavour to ensure that future suppliers are compliant. Current examples of third-party tools are:

  • Wistia – video player
  • Google Maps
  • Flockler
  • The Ambassador Platform (TAP)
  • The Conversation
  • Vepple

How we tested these websites

These websites are scanned automatically every five days using an external service. The scan report highlights any content that is not compliant with WCAG 2.2 (AA). We also completed manual checks.

What we’re doing to improve accessibility

We have an ongoing programme of work to address any accessibility issues that are highlighted by our scans. We are continually working on our content and site structure and are finding ways to make the site easier to navigate.

We are continually developing training and guidance on how to create accessible content to help website editors as part of our devolved editor model, and have brought in external expertise to deliver accessibility training to our devolved editorship.

Preparation of this accessibility statement

This statement was first prepared on 21 March 2018. It was prepared by NTU through self-assessment using Siteimprove and manual checks.

This statement was last reviewed on 4 September 2025.

Feedback and contact information

We’re always looking to improve the accessibility of our websites. If you think there are accessibility requirements we've not met or addressed in this statement, please use the contact details below.

If you need information on these websites in a different format or have a query, please get in touch:

We’ll consider your request and get back to you in 10 working days.

Enforcement procedure

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’).

If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).