Accessibility

D

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.

D

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.

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <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.

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 Samaritans homepage ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

B

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 7 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Samaritans	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 We're waiting for yo…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Let's prevent suicid…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Workplace wellbeing …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Every hour. Every da…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Why we need you to b…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 3,462 volunteers	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 It costs £52,628.40	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 10,632 calls	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Every hour. Every da…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Samaritans news	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Changing the way we …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Policy and research	5.24:1	3.0:1	#000000	#7F7F7F	Pass
title Samaritans \| Every l…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
a Skip to main content	5.24:1	4.5:1	#000000	#7F7F7F	Pass
p See content specific…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
p Choose another count…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
option United Kingdom	5.24:1	4.5:1	#000000	#7F7F7F	Pass
option England	5.24:1	4.5:1	#000000	#7F7F7F	Pass
option Scotland	4.96:1	4.5:1	#000000	#7B7B7B	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

8 landmarks

PASS

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A

Heading Hierarchy

33 headings

PASS

33 headings

Single H1 present

2 empty heading(s)

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

H1 Samaritans
H2 We're waiting for your call
H2 Let's prevent suicide today. Because tomorrow's too late.
H2 Workplace wellbeing courses
H2 Every hour. Every day. Every life.
H2 Donate today
H2 Talk to someone
H2 What we do
H2 Why we need you to be part of our Christmas story
H2 3,462 volunteers
H2 It costs £52,628.40
H2 10,632 calls
H2 (empty)
H2 Every hour. Every day. Every life.
H2 (empty)
H2 I'm looking for information about Samaritans in...
H2 Volunteer with us
H2 Samaritans news
H2 How the 10 Year Health Plan could support suicide prevention
H2 Suicide Prevention Consortium: what we learned and what’s next
H2 Megan Boxall runs 200 marathons in 200 days for Samaritans
H2 Changing the way we think about suicide
H2 Suicide facts and figures
H2 Samaritans' Media Guidelines
H2 The internet and suicide
H2 Our policy and research
H2 Samaritans Futureproofing Programme
H2 How we can help
H2 Support us
H2 Policy and research
H2 About Samaritans
H2 116 123
H2 Newsletter

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 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A

Form Accessibility

1 of 6 controls have issues

PASS

1 of 6 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select name="locale">

5 control(s) properly labeled

6 controls

5 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search	text	Search our website	for/id
#id_amount	number	Change amount (required)	for/id
#id_amount	number	Change amount (required)	for/id
#id_amount	number	Change amount (required)	for/id
#id_amount	number	Change amount (required)	for/id
locale	select	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Link & Button Quality

101 links, 28 buttons — all OK

PASS

101 links, 28 buttons — all OK

101 link(s) with descriptive text

101 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

129 links and buttons have descriptive text

A

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 30 passed

PASS

93

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go `div.nation-selector__form > a.button > div.button__inner > span.nation-selector__button-text--mobile`
More about volunteering `div.horizontal-card__container > a.horizontal-card__link > span > span.horizontal-card__link-text`
view other ways to get in touch `div.call-to-action > div.call-to-action__inner > a.button > div.button__inner`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
United Kingdom England Scotland Ireland Northern Ireland Wales `div.nation-selector__form > div.filters > div.filters__filter-wrapper > select.filters__select`

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 today Make today the day you make a gift to Samaritans. Your donation w… `section.section > div.wrapper > div.grid > a.card-new`
Talk to someone Suicidal thoughts can be complex, frightening and confusing. I… `section.section > div.wrapper > div.grid > a.card-new`
What we do We make sure there’s always someone to listen if you’re in crisis o… `section.section > div.wrapper > div.grid > a.card-new`
How the 10 Year Health Plan could support suicide prevention 13th April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide Prevention Consortium: what we learned and what’s next 2nd April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Megan Boxall runs 200 marathons in 200 days for Samaritans 30th March 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide facts and figures We're the only organisation collating suicide data f… `div.grid > div.grid__double-width > div.grid > a.card-new`
Samaritans' Media Guidelines Samaritans' Media Guidelines help journalists rep… `div.grid > div.grid__double-width > div.grid > a.card-new`
The internet and suicide The role online content can play in suicide risk and … `div.grid > div.grid__double-width > div.grid > a.card-new`
Our policy and research Our research and policy work drives change that helps … `div.grid > div.grid__double-width > div.grid > a.card-new`
Newsletter Stay on top of our latest news and updates `div.footer__inner > div.footer__nav-container > section.grid > a.footer-cta`

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

●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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○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

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