Accessibility

F

Heading Hierarchy

Action

41 headings, 5 skip(s)

FIX

41 headings, 5 skip(s)

Multiple H1 headings (11 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

H1 University of Bath
H2 A leading UK university with an international reputation for teaching and research excellence.
H3 Experience the University at a Postgraduate Virtual Open Day
H2 Study at Bath
H1 A global university duplicate H1
H3 Undergraduate prospectus 2027 skipped
H3 Master's prospectus 2026
H1 Improve your employability duplicate H1
H2 International careers support
H2 Making an impact
H1 Informing the direction of research duplicate H1
H3 Centre for Sustainable and Circular Technologies (CSCT) skipped
H3 Institute for Advanced Automotive Propulsion Systems (IAAPS)
H1 Tackling issues of global significance duplicate H1
H2 Supporting the community
H1 Working with the community duplicate H1
H3 Public events skipped
H3 Sign up to our Community Newsletter
H1 Sustainable Bath duplicate H1
H2 Work at Bath
H1 Be part of a vibrant and innovative community duplicate H1
H3 Education & Research skipped
H3 Management, Specialist and Administration
H3 Operations & Facilities Support
H3 Technical & Experimental
H1 Come and work at Bath duplicate H1
H2 Collaborate with us
H1 Support for your business duplicate H1
H3 Enterprise and entrepreneurship skipped
H3 Student engagement, employability and recruitment
H1 Driving innovation duplicate H1
H2 Our research impact
H3 Research with Impact
H2 Sport University of the Year 2026
H2 News stories
H3 Promiscuity and parental behaviour in birds driven by demographics, not the other way around
H3 Using a new online mental health tool just once boosts UK teenagers’ hope and emotional wellbeing
H3 Elite MBAs still influence who reaches the top of corporate America, University of Bath study shows
H3 Bath researchers join £6.7M programme to tackle global health challenges
H3 More from our Media Centre
H2 Social media

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

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

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

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

D

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: University of Bath

192x192 icon present

PWA Install Criteria Not Installable

Name University of Bath ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name University of Bath Icons 6 icon(s)

D

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: #202329

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.

D

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 ✗

D

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

3 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

C

Landmark Structure

Action

18 landmarks

REVIEW

18 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Search landmark 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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

B

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 Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h1 University of Bath

1.21:1

#000000

on

#1F1917

needs 3.0:1 (large text)

32px · mid-page

h2 A leading UK university with an internat…

1.16:1

#000000

on

#161616

needs 3.0:1 (large text)

24px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 University of Bath	1.21:1	3.0:1	#000000	#1F1917	Fail
h1 A global university	7.37:1	3.0:1	#000000	#999999	Pass
h1 Improve your employa…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Informing the direct…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Tackling issues of g…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Working with the com…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Sustainable Bath	7.37:1	3.0:1	#000000	#999999	Pass
h1 Be part of a vibrant…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Come and work at Bat…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Support for your bus…	7.37:1	3.0:1	#000000	#999999	Pass
h1 Driving innovation	7.37:1	3.0:1	#000000	#999999	Pass
h2 A leading UK univers…	1.16:1	3.0:1	#000000	#161616	Fail
h2 Study at Bath	7.37:1	3.0:1	#000000	#999999	Pass
h2 International career…	7.37:1	3.0:1	#000000	#999999	Pass
h2 Making an impact	7.37:1	3.0:1	#000000	#999999	Pass
h2 Supporting the commu…	7.37:1	3.0:1	#000000	#999999	Pass
h2 Work at Bath	7.37:1	3.0:1	#000000	#999999	Pass
h2 Collaborate with us	7.37:1	3.0:1	#000000	#999999	Pass
h2 Our research impact	7.37:1	3.0:1	#000000	#999999	Pass
h2 Sport University of …	7.37:1	3.0:1	#000000	#999999	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+

Alt Text Quality

All 45 images OK

PASS

All 45 images OK

2 decorative image(s) correctly marked

43 image(s) with good alt text

45 images 43 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#university-nav-checkbox	checkbox	Open menu	for/id
#university-search-checkbox	checkbox	Open search	for/id
query	text	Search bath.ac.uk	aria-label
input	submit	Search	aria-label

A+

Link & Button Quality

69 links, 15 buttons — all OK

PASS

69 links, 15 buttons — all OK

69 link(s) with descriptive text

69 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

84 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 99/100 — 1 failing, 31 passed

PASS

99

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.

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
Undergraduate prospectus 2027 `div.flex-wrapper > article.dual-block-text > div.link-wrapper > h3.link-heading`

These are opportunities to improve keyboard navigation in your application.

○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]`s are contained by their required parent element

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

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

●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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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