Skip to main content
Logos of Government Digital Service and Cabinet Office

Accessibility report for www.nottinghamcollege.ac.uk


Introduction

Website accessibility regulations came into force on 23 September 2018. The regulations mean that public sector bodies now have a legal obligation to meet accessibility requirements for their websites.

To check how well the public sector are meeting the requirements, the Government Digital Service (part of the Cabinet Office) has been monitoring a sample of public sector websites.

You’ve been sent this report because https://www.nottinghamcollege.ac.uk/ is one of the websites we’ve monitored. This document explains:

  • which parts of your website we looked at
  • how we checked the accessibility of those pages
  • the accessibility issues found and how important they are
  • what you need to do next to fix the issues

You can read more about the web accessibility regulations.


How accessible the website is

We checked https://www.nottinghamcollege.ac.uk/ on 12 January 2023 against the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.

Based on our testing, this site is partially compliant with WCAG 2.1 AA. This means there are some things which are not fully accessible.


How we checked

We use a mixture of simple manual checks and automated tests to find only the most common barriers to users with accessibility needs. We would expect your organisation to fully audit the website to find any other accessibility issues.

Manual checks included using each page without a mouse, viewing the page at different zoom settings, and simulating viewing the page on a small screen.

The automated tests were completed using the latest version of Axe.

Tests were completed using different settings in the Google Chrome browser on Mac OSX with a 13 inch screen.


Pages we checked

Page name and URLs of the pages we checked
Page Name URL

Home

https://www.nottinghamcollege.ac.uk/

Contact

https://www.nottinghamcollege.ac.uk/contact

Accessibility statement

https://www.nottinghamcollege.ac.uk/accessibility

About us

https://www.nottinghamcollege.ac.uk/about-us

News

https://www.nottinghamcollege.ac.uk/about-us/news

Governors' Meetings Minutes - Audit Committee 20 June 2022

https://assets.nottinghamcollege.ac.uk/PDFs/Minutes-Audit-Committee-20.06.22.pdf


The issues we found

Only serious accessibility issues on the sample of pages we tested are listed in this report – these will cause problems for users with access needs when using your website. There are likely to be smaller errors which will make things more difficult for some users. You must carry out your own audit to find and fix issues on other pages.


Home page issues

https://www.nottinghamcollege.ac.uk/

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.1.1 Keyboard

Users should be able to use a keyboard to access all content and functionality of a web page. This means the page can be used by people with no vision as well as people who use alternative keyboards or input devices that act as a keyboard.

  • The dropdown menus are not accessible using the keyboard. For example, 'Skills Bootcamps' under 'Adult learning' cannot be accessed using the keyboard, however this is accessible using the mouse
Issue:2

WCAG 2.4.7 Focus Visible

A visible focus helps users know which element has keyboard focus and where they are on the page.

When an element gets focus there should be a visible border around it. Highlighting the element that has keyboard focus or is hovered over can provide information like whether the element is interactive or the scope of that element.

Operating systems have a native indication of focus, which is available in many browsers. The default display of the focus indicator is not always highly visible and may even be difficult to see especially on coloured backgrounds.

  • The keyboard focus is not visible on the close button in the top corner of the webpage

  • The keyboard focus is not visible to change the featured article in the carousel. This refers to the buttons; 'Opening evenings', 'Apply now', 'University level' and 'Adult learning'

  • The keyboard focus becomes lost after tabbing from the 'Kind - Strategic Digital Agency' button at the bottom of the webpage

  • At 200% zoom, the keyboard focus is not visible on links in the footer of the webpage. This refers to the links; 'Explore', 'Legal' and 'Corporate'

Issue:3

WCAG 2.4.3 Focus Order

Users should be able to navigate a web page in an order that makes sense. Keyboard navigation should reflect a navigation sequence that is consistent with the meaning of content. Logical navigation reduces confusion and shows logical relationships between content and components.

The focus order may differ from the visual reading order as long as a user can still understand the web page without sight.

  • The keyboard tabs into the cookie banner at the bottom of the webpage last, therefore this covers content
Issue:4

WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast.

Poor colour contrast makes it difficult for someone with sight loss to see the content properly. If there is a big difference between the background and foreground colours it should be much easier to see the difference between them.

  • Dark grey text on a black background does not have sufficient colour contrast for smaller sized text. This refers to the 'Kind' label in the footer of the webpage
Issue:5

WCAG 1.4.1 Use of Colour: Links must be distinguishable without relying on colour.

Issue found using Deque Axe.

Links must be distinguished from surrounding text in a way that does not rely on colour.

Colour should not be the only way of visually identifying links on the page. Users with sight loss or problems perceiving colour may not be able to identify the difference in colour between a link and the rest of the content. You should ensure that all links on a page are identifiable by at least one additional method other than colour.

  • This refers to the word 'Disclaimer' in the footer of the webpage

Contact page issues

https://www.nottinghamcollege.ac.uk/contact

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.4.7 Focus Visible

  • The keyboard focus is not visible on the expanding menus listed under 'Frequently asked questions'
Issue:2

WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast.

  • Dark grey text on a black background does not have sufficient colour contrast for smaller sized text. This refers to the 'Kind' label in the footer of the webpage
Issue:3

WCAG 1.3.5 Identify Input Purpose: Autocomplete attribute must be used correctly.

Issue found using Deque Axe.

Autocomplete attribute must be used correctly.

Adding an appropriate autocomplete token to a form field helps assistive technology understand the type of input that is expected. This helps users to know what input is expected if the label is not familiar to them.

For each form element that accepts user data:

  • Check to see if the personal data is one of the 53 types shown in WCAG 2.1 Section 7 – Input Purposes for User Interface Components.
  • Check that the autocomplete attribute is set with the correct value to show the purpose of the component.
  • This refers to the text box under the title 'City'. To solve this problem, you need to fix the following: the autocomplete attribute is incorrectly formatted
Issue:4

WCAG 1.4.1 Use of Colour: Links must be distinguishable without relying on colour.

  • This refers to the word 'Disclaimer' in the footer of the webpage

Accessibility statement page issues

https://www.nottinghamcollege.ac.uk/accessibility

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.1.1 Keyboard

  • The dropdown menus are not accessible using the keyboard. For example, 'Leadership team' under 'Corporate' cannot be accessed using the keyboard
Issue:2

WCAG 2.4.7 Focus Visible

  • The keyboard focus becomes lost after tabbing from the 'Kind - Strategic Digital Agency' button at the bottom of the webpage

  • At 200% zoom, the keyboard focus is not visible on links in the footer of the webpage. This refers to the links; 'Explore', 'Legal' and 'Corporate'

Issue:3

WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast.

  • Dark grey text on a black background does not have sufficient colour contrast for smaller sized text. This refers to the 'Kind' label in the footer of the webpage
Issue:4

WCAG 1.4.1 Use of Colour: Links must be distinguishable without relying on colour.

  • This refers to the word 'Disclaimer' in the footer of the webpage

About us page issues

https://www.nottinghamcollege.ac.uk/about-us

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.1.1 Keyboard

  • The dropdown menus are not accessible using the keyboard. For example, 'Leadership team' under 'Corporate' cannot be accessed using the keyboard
Issue:2

WCAG 2.4.7 Focus Visible

  • At 200% zoom, the keyboard focus is not visible on links in the footer of the webpage. This refers to the links; 'Explore', 'Legal' and 'Corporate'
Issue:3

WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast.

  • Dark grey text on a black background does not have sufficient colour contrast for smaller sized text. This refers to the 'Kind' label in the footer of the webpage
Issue:4

WCAG 1.4.1 Use of Colour: Links must be distinguishable without relying on colour.

  • This refers to the word 'Disclaimer' in the footer of the webpage

News page issues

https://www.nottinghamcollege.ac.uk/about-us/news

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.1.1 Keyboard

  • The dropdown menus are not accessible using the keyboard. For example, 'Leadership team' under 'Corporate' cannot be accessed using the keyboard
Issue:2

WCAG 2.4.7 Focus Visible

  • The keyboard focus becomes lost after tabbing from the 'Kind - Strategic Digital Agency' button at the bottom of the webpage

  • At 200% zoom, the keyboard focus is not visible on links in the footer of the webpage. This refers to the links; 'Explore', 'Legal' and 'Corporate'

Issue:3

WCAG 1.4.3 Contrast (minimum): Elements must have sufficient colour contrast.

  • Dark grey text on a black background does not have sufficient colour contrast for smaller sized text. This refers to the 'Kind' label in the footer of the webpage
Issue:4

WCAG 1.4.1 Use of Colour: Links must be distinguishable without relying on colour.

  • This refers to the word 'Disclaimer' in the footer of the webpage

Governors' Meetings Minutes - Audit Committee 20 June 2022 issues

https://assets.nottinghamcollege.ac.uk/PDFs/Minutes-Audit-Committee-20.06.22.pdf

Names and URLs of pages we checked
# Issue and description Where the issue was found
Issue:1

WCAG 2.4.2 Page titled

PDF documents should have titles that describe the topic or purpose of the page. Titles help users understand the topic without having to read the entire document.

Without a descriptive title a user may need to spend time searching the document to decide whether the content is relevant.

When a PDF is displayed in a browser the title will usually be displayed in the top title bar or as the tab name.

  • The page title is missing from the PDF document
Issue:2

WCAG 1.1.1 Non-text content

People with sight loss may not see an image clearly on a page. You need to use a text alternative to share the information. The alternative text must describe the information or function represented by the image.

Screen readers can share the alternative text with the user. In PDF documents you must ensure that images are tagged correctly with alternative text.

  • Alternative text is missing from the logo at the top of the document

Your accessibility statement

As part of the regulations you must publish an accessibility statement.

An accessibility statement for the website was found but:

  • accessibility issues were found during the test that were not included in the statement

  • mandatory wording is missing

More information about accessibility statements can be found at https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps.

A sample statement can be found at https://www.gov.uk/government/publications/sample-accessibility-statement.


What to do next

It is a requirement of The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 that public sector websites are accessible.

You should fix the issues that were found and do your own accessibility audit to check for issues that go beyond the scope of simple accessibility testing.

You need to review your accessibility statement to cover the issues found in this report, including ones related to your accessibility statement, and any other accessibility issues found during your own site audit.


Enforcement

On behalf of the Minister for the Cabinet Office we provide the Equality and Human Rights Commission (EHRC) with details about public sector bodies who have been monitored. If accessibility issues remain after giving you time to fix them, the EHRC may take further action.

Public sector bodies must publish an accessibility statement and review it regularly. If the decision is taken that a public sector body has failed to publish an accessibility statement or that the accessibility statement is incorrect, the Minister for the Cabinet Office may publish the name of the body and a copy of the decision.

The enforcement process can be found at https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#how-the-accessibility-regulations-will-be-monitored-and-enforced.


Contact and more information

This test was conducted by the Government Digital Service on behalf of the Minister of the Cabinet Office as part of their obligations to monitor the accessibility of public sector websites in the United Kingdom.

As the monitoring body we cannot offer specific advice on approaches or general accessibility queries other than questions directly related to the items in this report.

Any questions about this report can be sent to accessibility-monitoring@digital.cabinet-office.gov.uk.

Further information on guidance and tools for digital accessibility can be found at https://www.gov.uk/guidance/guidance-and-tools-for-digital-accessibility.

Help with accessibility auditing and publishing an accessibility statement can be found at https://www.gov.uk/guidance/make-your-website-or-app-accessible-and-publish-an-accessibility-statement.

Help us improve accessibility reports

Don’t include personal or financial information like your National Insurance number or credit card details.