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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 MAIN CONTENTINFO footer

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
Heading Hierarchy
17 headings, 2 skip(s)
REVIEW
17 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 How a 5,300-year-old tool is rewriting the story of ancient Egypt
  • H2 Search for a course
  • H2 Global Scholarships
  • H2 Undergraduate Open Day
  • H2 International students
  • H2 Who we are
  • H2 Donate now
  • H2 Latest news
  • H4 Elite MBAs still influence who reaches top of corporate America skipped
  • H4 Trait choice and selection key to helping corals survive heatwaves
  • H4 Lough Neagh sand mining threatens lake’s ecosystem, research warns
  • H2 Latest research and innovations
  • H2 Our research
  • H2 Work with us
  • H2 Study with us
  • H5 Newcastle skipped
  • H5 Malaysia | Singapore

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Form Accessibility
Action
6 of 14 controls have issues
REVIEW
6 of 14 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" name="searchSubmit">; <input type="submit">
Info::
8 control(s) properly labeled
14 controls
8 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#search-paneltextSearch...for/id
#courseSelectselectnone
#SearchBoxtextWhat do you want to study?for/id
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
searchSubmitsubmit(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
inputsubmit(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" name="searchSubmit">; <input type="submit">

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

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 Page Not Found - 404 - Newcastle University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 How a 5,300-year-old tool is rewriting t…
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Search for a course
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Global Scholarships
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Undergraduate Open Day
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 International students
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Donate now
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest news
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest research and innovations
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our research
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Work with us
1.64:1
#000000
on
#00345B
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
title Newcastle University | World Top 140 Res…
1.74:1
#000000
on
#003862
needs 4.5:1 (normal text)
16px · top of page (header area)
a Consent
1.69:1
#000000
on
#00365E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Details
1.50:1
#000000
on
#1E2E37
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a [#IABV2SETTINGS#]
1.44:1
#000000
on
#322716
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.18:1
#000000
on
#291104
needs 4.5:1 (normal text)
16px · above the fold
div This website uses cookies
1.14:1
#000000
on
#260D04
needs 4.5:1 (normal text)
16px · above the fold
div We use necessary cookies to make our sit…
1.26:1
#000000
on
#281C10
needs 4.5:1 (normal text)
16px · above the fold
a our cookie policy
1.33:1
#000000
on
#2D2011
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_BANNER_ICON#]
1.45:1
#000000
on
#31281B
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_TOAST_TEXT#]
1.47:1
#000000
on
#32291C
needs 4.5:1 (normal text)
16px · above the fold

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 How a 5,300-year-old…1.64:13.0:1
#000000
#00345B
Fail
h2 Search for a course1.64:13.0:1
#000000
#00345B
Fail
h2 Global Scholarships1.64:13.0:1
#000000
#00345B
Fail
h2 Undergraduate Open D…1.64:13.0:1
#000000
#00345B
Fail
h2 International studen…1.64:13.0:1
#000000
#00345B
Fail
h2 Donate now1.64:13.0:1
#000000
#00345B
Fail
h2 Latest news1.64:13.0:1
#000000
#00345B
Fail
h2 Latest research and …1.64:13.0:1
#000000
#00345B
Fail
h2 Our research1.64:13.0:1
#000000
#00345B
Fail
h2 Work with us1.64:13.0:1
#000000
#00345B
Fail
title Newcastle University…1.74:14.5:1
#000000
#003862
Fail
a Consent1.69:14.5:1
#000000
#00365E
Fail
a Details1.50:14.5:1
#000000
#1E2E37
Fail
a [#IABV2SETTINGS#]1.44:14.5:1
#000000
#322716
Fail
a About1.18:14.5:1
#000000
#291104
Fail
div This website uses co…1.14:14.5:1
#000000
#260D04
Fail
div We use necessary coo…1.26:14.5:1
#000000
#281C10
Fail
a our cookie policy1.33:14.5:1
#000000
#2D2011
Fail
div [#GPC_BANNER_ICON#]1.45:14.5:1
#000000
#31281B
Fail
div [#GPC_TOAST_TEXT#]1.47:14.5:1
#000000
#32291C
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.

A+
Alt Text Quality
1 of 71 images have issues
PASS
1 of 71 images have issues
Warning::
1 image(s) with generic alt text
Info::
4 decorative image(s) correctly marked
Info::
66 image(s) with good alt text
71 images 66 good alt text 4 decorative 1 generic
IssueCount
generic1 image(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 29 passed
PASS
91

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open Search div.primary > div.row > div.controls > div.search-toggle
Open Menu div.primary > div.row > div.controls > div.menu-toggle

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Elite MBAs still influence who reaches top of corporate America div.promoPanelsContainer > div.promo > a > h4
How is Voice® bringing academics, research, and the public together? div.promoPanelsContainer > div.promo > a > h4
Newcastle div.row > div.footerContent > div.footerColumn > h5

These are opportunities to improve keyboard navigation in your application.

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
Search your study level Undergraduate Postgraduate div.fieldWrapper > div.selectBox > label.wrap > select#courseSelect

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.

○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-*]` attributes match their 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
●Input buttons have discernible text.
●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
●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 are distinguishable without relying on color.
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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
○`<input type="image">` elements have `[alt]` text
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback