Skip to content
https://mentalhealth.org.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Form Accessibility
Action
4 of 5 controls have issues
FIX
4 of 5 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-search">; <input type="submit" id="edit-submit-search--2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="edit-s">; <input type="text" name="s" id="edit-s--2">
Info::
1 control(s) properly labeled
5 controls
1 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#mhf-dropdown-selectselectnone
#edit-s--2text(Search)placeholder only
#edit-stext(Search)placeholder only
#edit-submit-search--2submit(none)none
#edit-submit-searchsubmit(none)none

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

<input type="submit" id="edit-submit-search">; <input type="submit" id="edit-submit-search--2">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s" id="edit-s">; <input type="text" name="s" id="edit-s--2">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #fff
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 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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV "block-mhf-theme-headermenuunitedkingdom-menu" 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

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

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::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Mental Health Foundation. Mental Health Awareness Week Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
26 icon(s) detected
REVIEW
26 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::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA 3 pass AA only
title Mental Health Foundation | Everyone dese…
2.96:1
#000000
on
#95394A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
2.96:1
#000000
on
#95394A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Open submenu
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
a Explore mental health
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
span Open submenu
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
a About us
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
span Open submenu
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
span Close submenu
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
span Our work
1.19:1
#000000
on
#200054
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Header menu19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Today I want to:19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Highlights19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Quick links19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Nations19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Social19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Sign up for email up…19.29:13.0:1
#000000
#F5F5F7
Pass
h2 Footer19.29:13.0:1
#000000
#F5F5F7
Pass
title Mental Health Founda…2.96:14.5:1
#000000
#95394A
Fail
span Menu2.96:14.5:1
#000000
#95394A
Fail
a Our work6.84:14.5:1
#000000
#939394
Pass
span Open submenu6.84:14.5:1
#000000
#939394
Pass
a Get involved6.84:14.5:1
#000000
#939394
Pass
span Open submenu1.19:14.5:1
#000000
#200054
Fail
a Explore mental healt…1.19:14.5:1
#000000
#200054
Fail
span Open submenu1.19:14.5:1
#000000
#200054
Fail
a About us1.19:14.5:1
#000000
#200054
Fail
span Open submenu1.19:14.5:1
#000000
#200054
Fail
span Close submenu1.19:14.5:1
#000000
#200054
Fail
span Our work1.19:14.5:1
#000000
#200054
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.

A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H2 Header menu
  • H1 Everyone deservesgood mental health
  • H2 Today I want to:
  • H2 Mental Health Awareness Week 11 - 17 May 2026
  • H2 Highlights
  • H2 Our bold new recommendations for the proposed under-16s social media ban
  • H2 Blog
  • H2 Why human connection matters at university
  • H2 Blog
  • H2 Mental Health Awareness Week Skydive
  • H2 Event
  • H2 Small Talk, Big Change podcast
  • H2 Podcast
  • H2 Information and guidance
  • H3 A-Z Topics
  • H3 How-to guides
  • H3 Looking after your mental health
  • H3 Supporting someone else with their mental health
  • H2 For professionals
  • H3 Helping someone with a mental health problem
  • H3 Mental health statistics
  • H3 Resources for working with young people
  • H2 Support our work
  • H3 Fundraise
  • H3 Donate
  • H3 Participate
  • H3 Shop
  • H2 Quick links
  • H2 Nations
  • H2 Social
  • H2 Sign up for email updates
  • H2 Footer
A+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
17 image(s) with good alt text
18 images 17 good alt text
IssueCount
too long1 image(s)
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: MHF
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name MHF 192×192 icon 512×512 icon Start URL /?homescreen=1 Display Mode standalone
Name MHF Display Mode standalone Theme Color #fff Background Color #fff Icons 9 icon(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_vudLORvw3tiXqeLrR5dFVsDHN3UQBN4rmFbQY7HDUzU.css?delta=2&language=en&theme=mhf_theme&include=eJxdjlFuxCAQQy9EgqoeCA3gBCpg0DBs056-fLTabD_9LD_ZQxXicHUeiO7IZcVhTzQIFRNYYKPMTmWnD7pMzCMUHlPgGj2sCmBqOpwmVNjApSBo5naDZ2G_VE-QIHyLiku3ipjpDtMyb8s3a9u6cH1ZfPJrxf6YI5DCCuvbu-kkdAr1NP7OP8k-W5--5JEQjWB0biM_4CratP_y7pl16NqZb_T0Jb8HvFCLuZ0_OlR8eQ
Print Stylesheet Print Optimized
Print stylesheet /sites/default/files/css/css_vudLORvw3tiXqeLrR5dFVsDHN3UQBN4rmFbQY7HDUzU.css?delta=2&language=en&theme=mhf_theme&include=eJxdjlFuxCAQQy9EgqoeCA3gBCpg0DBs056-fLTabD_9LD_ZQxXicHUeiO7IZcVhTzQIFRNYYKPMTmWnD7pMzCMUHlPgGj2sCmBqOpwmVNjApSBo5naDZ2G_VE-QIHyLiku3ipjpDtMyb8s3a9u6cH1ZfPJrxf6YI5DCCuvbu-kkdAr1NP7OP8k-W5--5JEQjWB0biM_4CratP_y7pl16NqZb_T0Jb8HvFCLuZ0_OlR8eQ Inline @media print Not detected
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
`[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 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
Identical links have the same purpose.
`[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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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