Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #6b2c91

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Form Accessibility

2 of 12 controls have issues

REVIEW

2 of 12 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="text" name="vendor-search-handler" id="vendor-search-handler">

10 control(s) properly labeled

12 controls

10 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#searchBox	text	Search text	for/id
#study-level	select	Level of study	for/id
#course-name	text	Subject area of course name	for/id
#ot-group-id-C0002	checkbox	Performance cookies	for/id
#ot-group-id-C0003	checkbox	Functional cookies	for/id
#ot-group-id-C0004	checkbox	Targeting cookies	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#chkbox-id	checkbox	checkbox label	for/id
input	submit	(none)	none
#vendor-search-handler	text	(none)	none

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

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

Link & Button Quality

2 issue(s) across 174 links and 18 buttons

REVIEW

2 issue(s) across 174 links and 18 buttons

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.manchester.ac.uk/discover/privacy-information/data-protection/coo…; https://www.onetrust.com/solutions/consent-and-preferences/?utm_source=cmp&ut…

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.mobile-menu-icon (#50 on page); button.mobile-menu-icon (#388 on page)

172 link(s) with descriptive text

174 links

0 empty

0 generic text

2 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.manchester.ac.uk/discover/pr…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/solutions/conse…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

188 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.manchester.ac.uk/discover/privacy-information/data-protection/coo…; https://www.onetrust.com/solutions/consent-and-preferences/?utm_source=cmp&ut…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.mobile-menu-icon (#50 on page); button.mobile-menu-icon (#388 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 File Not Found | The University of Manchester ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 The University of Manchester

2.60:1

#000000

#694367

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Find your course

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Study with us

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discover Manchester

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Feature

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest news

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Key University metrics

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quick links

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact us

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Find us

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connect with us

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your privacy is important

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy preference centre

2.60:1

#000000

#694367

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Manchester joint most successful quizzer…

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Landmark Manchester–Cambridge partners…

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 How a simple blood test could detect dea…

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Your privacy

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Strictly necessary cookies

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Performance cookies

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Functional cookies

2.60:1

#000000

#694367

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The University of Ma…	2.60:1	3.0:1	#000000	#694367	Fail
h2 Find your course	2.60:1	3.0:1	#000000	#694367	Fail
h2 Study with us	2.60:1	3.0:1	#000000	#694367	Fail
h2 Discover Manchester	2.60:1	3.0:1	#000000	#694367	Fail
h2 Feature	2.60:1	3.0:1	#000000	#694367	Fail
h2 Latest news	2.60:1	3.0:1	#000000	#694367	Fail
h2 Key University metri…	2.60:1	3.0:1	#000000	#694367	Fail
h2 Quick links	2.60:1	3.0:1	#000000	#694367	Fail
h2 Contact us	2.60:1	3.0:1	#000000	#694367	Fail
h2 Find us	2.60:1	3.0:1	#000000	#694367	Fail
h2 Connect with us	2.60:1	3.0:1	#000000	#694367	Fail
h2 Your privacy is impo…	2.60:1	3.0:1	#000000	#694367	Fail
h2 Privacy preference c…	2.60:1	3.0:1	#000000	#694367	Fail
h3 Manchester joint mos…	2.60:1	3.0:1	#000000	#694367	Fail
h3 Landmark Manchester�…	2.60:1	3.0:1	#000000	#694367	Fail
h3 How a simple blood t…	2.60:1	3.0:1	#000000	#694367	Fail
h3 Your privacy	2.60:1	3.0:1	#000000	#694367	Fail
h3 Strictly necessary c…	2.60:1	3.0:1	#000000	#694367	Fail
h3 Performance cookies	2.60:1	3.0:1	#000000	#694367	Fail
h3 Functional cookies	2.60:1	3.0:1	#000000	#694367	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+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

29 headings

PASS

29 headings

Single H1 present

H1 The University of Manchester
H2 Support that makes a difference
H2 Find your course
H2 Study with us
H2 Discover Manchester
H2 Feature
H2 Latest news
H3 Manchester joint most successful quizzers in series’ history.
H3 Landmark Manchester–Cambridge partnership moves forward
H3 How a simple blood test could detect deadliest brain tumours
H2 Bold ideas in action
H2 Key University metrics
H2 Quick links
H2 Contact us
H2 Find us
H2 Connect with us
H2 Your privacy is important
H2 Privacy preference centre
H3 Your privacy
H3 Strictly necessary cookies
H3 Performance cookies
H3 Functional cookies
H3 Targeting cookies
H4 Your privacy
H4 Strictly necessary cookies
H4 Performance cookies
H4 Functional cookies
H4 Targeting cookies
H3 Back

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

3 decorative image(s) correctly marked

17 image(s) with good alt text

20 images 17 good alt text 3 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 29 passed

PASS

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.headerContent > div#headerContent-container > div.menu-search-icons > button.search-icon `div.headerContent > div#headerContent-container > div.menu-search-icons > button.search-icon`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[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

●`<frame>` or `<iframe>` elements have a title

●`<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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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

○`<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

○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.

○Identical links have the same purpose.

○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.