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 4 REVIEW 3 FIX

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: #000000bf

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

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

No <nav> landmark found

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 University of Birmingham 404 page ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

14 icon(s) detected

REVIEW

14 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 Undergraduate Open Days

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · mid-page

h2 500 Million Years in a garden

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 QS subject rankings success

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Search our courses

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Faster trials for rare cancers

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built in Birmingham

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Find your place, in a place like no othe…

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 All the space you need

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 All the space you need

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A campus full of opportunity

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Supporting you

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Experience Helios at The Exchange

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join our dynamic community

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Meet Tamsin

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet Rishi

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet Josh

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet Tamsin

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet Rishi

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Your choice regardin…	6.92:1	3.0:1	#000000	#949494	Pass
h2 Undergraduate Open D…	6.92:1	3.0:1	#000000	#949494	Pass
h2 Undergraduate Open D…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 500 Million Years in…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 QS subject rankings …	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Search our courses	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Faster trials for ra…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Built in Birmingham	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Find your place, in …	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 All the space you ne…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 All the space you ne…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 A campus full of opp…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Supporting you	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Experience Helios at…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Join our dynamic com…	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Meet Tamsin	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Meet Rishi	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Meet Josh	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Meet Tamsin	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h3 Meet Rishi	1.08:1	3.0:1	#000000	#0D0D0D	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.

Heading Hierarchy

22 headings

PASS

22 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Your choice regarding cookies on this site
H1 (empty)
H2 Undergraduate Open Days
H2 Undergraduate Open Days
H2 500 Million Years in a garden
H2 QS subject rankings success
H2 Search our courses
H2 Faster trials for rare cancers
H2 Built in Birmingham
H3 Meet Tamsin
H3 Meet Rishi
H3 Meet Josh
H3 Meet Tamsin
H3 Meet Rishi
H3 Meet Josh
H2 Find your place, in a place like no other.
H2 All the space you need
H2 All the space you need
H2 A campus full of opportunity
H2 Supporting you
H2 Experience Helios at The Exchange
H2 Join our dynamic community

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

7 decorative image(s) correctly marked

8 image(s) with good alt text

15 images 8 good alt text 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	text	Select search	for/id
#studyLevel	select	Select studyLevel	for/id

A+

Link & Button Quality

44 links, 20 buttons — all OK

PASS

44 links, 20 buttons — all OK

44 link(s) with descriptive text

44 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

64 links and buttons have descriptive text

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: University of Birmingham

192x192 icon present

512x512 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name University of Birmingham ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓

Name University of Birmingham Display Mode minimal-ui Theme Color #FF227F Background Color #FF227F Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 passed

PASS

100

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.

○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

●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

●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

●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

●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

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

○No element has a `[tabindex]` value greater than 0

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

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