Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Cancer Research UK ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Landmark Structure

Action

7 landmarks

REVIEW

7 landmarks

No <main> landmark found

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

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Cancer Research UK

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Cancer Research UK ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Cancer Research UK Display Mode standalone Theme Color #2d2d62 Background Color #ffffff Icons 2 icon(s)

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 We exist to beat cancer.
H2 Ways to support our vital research
H3 Get involved
H3 Volunteer with us
H3 Do your own fundraising
H2 You donate. We discover.
H3 Over the past 50 years, our work has helped double cancer survival in the UK.
H2 We're here to support you
H3 Information about cancer
H3 Cancer chat forum
H2 The power of our science
H3 Our research breakthroughs
H2 What's new?
H3 Listen to The Rest Is Science podcast
H3 Take on Big Hike 2026
H3 It's your time to Shine
H2 Our fundraising brands
H3 Together we are beating cancer

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

16 image(s) with good alt text

16 images 16 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#radio-_R_9l6dbahmledbqunb_	radio		none
#radio-_R_al6dbahmledbqunb_	radio		none
#radio-_R_bl6dbahmledbqunb_	radio		none
#field-_R_edbahmledbqunb_	text	Or enter another amount	for/id
#radio-_R_9l6lbahmledbqunb_	radio		none
#radio-_R_al6lbahmledbqunb_	radio		none
#radio-_R_bl6lbahmledbqunb_	radio		none
#field-_R_elbahmledbqunb_	text	Or enter another amount	for/id

A+

Link & Button Quality

57 links, 14 buttons — all OK

PASS

57 links, 14 buttons — all OK

57 link(s) with descriptive text

57 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

71 links and buttons have descriptive text

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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
h1 We exist to beat can…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ways to support our …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You donate. We disco…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We're here to suppor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The power of our sci…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What's new?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our fundraising bran…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get involved	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Volunteer with us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Do your own fundrais…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Over the past 50 yea…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Information about ca…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cancer chat forum	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our research breakth…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Listen to The Rest I…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Take on Big Hike 202…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 It's your time to Sh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Together we are	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 beating cancer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cancer Research UK \|…	21.00:1	4.5: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 — 2 failing, 27 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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_9l6dbahmledbqunb_ `ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_9l6dbahmledbqunb_`
ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_al6dbahmledbqunb_ `ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_al6dbahmledbqunb_`
ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_bl6dbahmledbqunb_ `ul.chakra-stack > li.css-8atqhb > label.css-8atqhb > input#radio-_R_bl6dbahmledbqunb_`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Donate now `div.chakra-tabs__tab-panels > div#tabs-_R_1ahmledbqunb_--tabpanel-0 > div.chakra-form-control > button.chakra-button`

○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

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

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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