Skip to content
https://nottingham.ac.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
favicon.ico Present
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Triangle Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

19 pass 1 fail WCAG AA
title University of Nottingham
1.36:1
#000000
on
#10263B
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Find your dream cour…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hundreds of work pla…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Master's Virtual Ope…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Research21.00:13.0:1
#000000
#FFFFFF
Pass
h2 University news21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured events21.00:13.0:1
#000000
#FFFFFF
Pass
h3 From dedication to d…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 to changing lives to…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New exhibition marks…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How primitive plants…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Engineers develop ne…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 3D printing will ena…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New exhibition marks…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How primitive plants…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Engineers develop ne…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 3D printing will ena…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New exhibition marks…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Unjust incarceration…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Profit with purpose:…21.00:13.0:1
#000000
#FFFFFF
Pass
title University of Nottin…1.36:14.5:1
#000000
#10263B
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 25 passed
REVIEW
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Quick links div#accordionExample > div.accordion-item > h2#Quick_links-heading > a.accordion-button
Students div#accordionExample > div.accordion-item > h2#Students-heading > a.accordion-button
Staff div#accordionExample > div.accordion-item > h2#Staff-heading > a.accordion-button
Alumni div#accordionExample > div.accordion-item > h2#Alumni-heading > a.accordion-button

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select study level Undergraduate Postgraduate Research opportunities Apprentice… div.row > div.col-md-4 > div.search-select > select#cfinder-filter

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.news-carousel > ul.slick-dots > li.slick-active > button
Go to slide 2 div.news-carousel > ul.slick-dots > li > button
Go to slide 3 div.news-carousel > ul.slick-dots > li > button
Go to slide 4 div.news-carousel > ul.slick-dots > li > button

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 Clearing - you've got this
  • H2 Find your dream course
  • H2 Hundreds of work placements
  • H2 Master's Virtual Open Days
  • H2 Research
  • H3 From dedication to discovery,to changing lives together.
  • H2 University news
  • H3 New exhibition marks 250 years since the Declaration of Independence and reveals Notts connection to early US history
  • H3 How primitive plants evolved to survive Earth’s most catastrophic extinction event
  • H3 Engineers develop new plasma spray technique to deliver stronger, more reliable Tungsten–Copper protective coatings
  • H3 3D printing will enable researchers to see how human cells sense and respond to their environment
  • H3 New exhibition marks 250 years since the Declaration of Independence and reveals Notts connection to early US history
  • H3 How primitive plants evolved to survive Earth’s most catastrophic extinction event
  • H3 Engineers develop new plasma spray technique to deliver stronger, more reliable Tungsten–Copper protective coatings
  • H3 3D printing will enable researchers to see how human cells sense and respond to their environment
  • H3 New exhibition marks 250 years since the Declaration of Independence and reveals Notts connection to early US history
  • H2 Featured events
  • H3 Unjust incarceration of U.S. immigrants during World War II
  • H3 Profit with purpose: how impact investing is reshaping capitalism
  • H2 Quick links
  • H2 Students
  • H2 Staff
  • H2 Alumni
A+
Alt Text Quality
All 35 images OK
PASS
All 35 images OK
Info::
35 image(s) with good alt text
35 images 35 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="send" id="SearchQueryControl_SearchButton">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#SearchQueryControl_SearchTextBoxsearchSearch our site...aria-label
#cfinder-inputsearchSearch our courses...for/id
#cfinder-filterselectSearch our courses...for/id
#SearchQueryControl_SearchButtonsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="send" id="SearchQueryControl_SearchButton">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback