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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404-error | University of Leeds ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: MyWebSite
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name MyWebSite ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name MyWebSite Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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
h2 Changes to our privacy policy
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Tell us whether you accept cookies
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
24px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 University of Leeds10.53:13.0:1
#000000
#00D0A0
Pass
h2 Changes to our priva…1.30:13.0:1
#000000
#212121
Fail
h2 Tell us whether you …1.30:13.0:1
#000000
#212121
Fail
h2 Your privacy options21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Undergraduate Open D…10.53:13.0:1
#000000
#00D0A0
Pass
h2 Find your course10.53:13.0:1
#000000
#00D0A0
Pass
h2 Our rankings10.53:13.0:1
#000000
#00D0A0
Pass
h2 Introducing Leeds10.53:13.0:1
#000000
#00D0A0
Pass
h2 Life at Leeds10.53:13.0:1
#000000
#00D0A0
Pass
h2 World-leading resear…10.53:13.0:1
#000000
#00D0A0
Pass
h2 Footer navigation10.53:13.0:1
#000000
#00D0A0
Pass
h2 Contact information10.53:13.0:1
#000000
#00D0A0
Pass
h2 Site information10.53:13.0:1
#000000
#00D0A0
Pass
h3 Our use of cookies5.24:13.0:1
#000000
#A37557
Pass
h3 Explore Leeds10.53:13.0:1
#000000
#00D0A0
Pass
h3 Funding and scholars…10.53:13.0:1
#000000
#00D0A0
Pass
h3 Postgraduate Virtual…10.53:13.0:1
#000000
#00D0A0
Pass
h3 Funding and scholars…10.53:13.0:1
#000000
#00D0A0
Pass
h3 Introducing Leeds10.53:13.0:1
#000000
#00D0A0
Pass
h3 Study and courses10.53:13.0:1
#000000
#00D0A0
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
Landmark Structure
20 landmarks
PASS
20 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
2 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "University links" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
35 headings
PASS
35 headings
Info::
Single H1 present
  • H2 Changes to our privacy policy
  • H2 Tell us whether you accept cookies
  • H2 Your privacy options
  • H3 Our use of cookies
  • H3 Strictly necessary cookies
  • H3 Cookies that measure website use
  • H3 Cookies that help with our communications and marketing
  • H1 University of Leeds
  • H2 Undergraduate Open Days 2026
  • H2 Find your course
  • H3 Explore Leeds
  • H3 Funding and scholarships
  • H3 Postgraduate Virtual Open Day
  • H3 Funding and scholarships
  • H2 Our rankings
  • H2 Introducing Leeds
  • H3 Introducing Leeds
  • H2 Life at Leeds
  • H3 Romy's story
  • H3 Joceline Kamajaya
  • H3 Emilio’s story
  • H3 Pragya Sharma
  • H2 World-leading research to shape a better future
  • H3 Latest news
  • H3 Queen Elizabeth Prize for Higher and Further Education
  • H3 Minimising the impact of melting glaciers
  • H3 When parks don’t feel like safe public spaces
  • H3 Positive impact of supermarket junk food restrictions revealed
  • H3 Embedding young people’s voices in global development
  • H2 Footer navigation
  • H3 Study and courses
  • H3 About Us
  • H3 Quicklinks and contacts
  • H2 Contact information
  • H2 Site information
A+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
12 images 9 good alt text 1 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#analytics_cookiescheckboxnone
#remarketing_cookiescheckboxnone
#global-masthead__search-fieldsearchSearch leeds.ac.ukfor/id
#radio-undergraduateradioUndergraduatefor/id
#radio-mastersradioMastersfor/id
#querysearchSearch coursesfor/id
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 29 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.
●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
●Elements with the `role=text` attribute do not have focusable descendents.
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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
○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
○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.
○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