Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ 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: #212b58

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 ✗

Landmark Structure

16 landmarks

REVIEW

16 landmarks

No <main> landmark found

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

10 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Error Page - 404 Error Page - University of Liverpool ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

A+

Heading Hierarchy

29 headings

PASS

29 headings

Single H1 present

H1 University of Liverpool
H2 Open Days
H2 Discover the University of Liverpool
H2 Study with us
H2 Visit us on an Open Day
H2 Discover Liverpool in India
H2 Our rankings and reputation
H3 World Top 150
H3 Teaching Gold
H3 18th in the UK
H3 World Top 150
H2 Lightbulb moments at the VG&M
H2 Our research: Transforming lives, changing the world
H2 Discover a vibrant student life in Liverpool
H2 We're making an impact across the globe
H2 Latest news
H3 XJTLU granted Freedom of the City by Liverpool City Council
H3 Muon g-2 experiment wins prestigious Breakthrough Prize in Fundamental Physics
H3 Large UK trial shows bone healing ‘superpower’ in children
H3 Political Studies Association prizes for Liverpool researchers
H2 Upcoming events
H3 The Adam Buxton Band
H3 Pint of Science 2026
H3 Book Panel: Fewer Children, Longer Lives: Population Ageing, Pronatalism and New Social Divides
H2 Website footer
H3 Information for
H3 Study at Liverpool
H3 Quick links
H3 Contact us

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

2 decorative image(s) correctly marked

11 image(s) with good alt text

13 images 11 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 14 controls labeled

PASS

All 14 controls labeled

14 control(s) properly labeled

14 controls

14 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	checkbox		none
input	checkbox		none
#rb-search--global__input	search	Search	for/id
#rb-search--global__scope_all	radio	All	for/id
#rb-search--global__scope_courses	radio	Courses	for/id
#rb-search--global__scope_staff	radio	Academic staff	for/id
#rb-search--global__scope_news	radio	News	for/id
#rb-search--global__scope_events	radio	Events	for/id
#course_query	text	Find your course	for/id
#course_level_all	radio	All courses	for/id
#course_level_undergraduate	radio	Undergraduate	for/id
#course_level_postgraduate-taught	radio	Postgraduate taught	for/id
#course_level_postgraduate-research	radio	Postgraduate research	for/id

A+

Link & Button Quality

228 links, 18 buttons — all OK

PASS

228 links, 18 buttons — all OK

228 link(s) with descriptive text

228 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

246 links and buttons have descriptive text

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Open Days	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover the Univers…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Study with us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Visit us on an Open …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover Liverpool i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our rankings and rep…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Lightbulb moments at…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our research: Transf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover a vibrant s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We're making an impa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest news	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upcoming events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Website footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 World Top 150	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Teaching Gold	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 18th in the UK	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 World Top 150	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Information for	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Study at Liverpool	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quick links	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 28 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
form.rb-block-container > fieldset.rb-fieldset > div.rb-formgroup > button.rb-button `form.rb-block-container > fieldset.rb-fieldset > div.rb-formgroup > button.rb-button`

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

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●Touch targets have sufficient size and spacing.

●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

○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

○Select elements have associated label elements.

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

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