Skip to content
https://headspace.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Heading Hierarchy
Action
45 headings, 2 skip(s)
FIX
45 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 What we offer
  • H6 How we help
  • H6 Explore our library
  • H6 Who we serve
  • H6 What we offer
  • H6 Our approach
  • H6 Resources
  • H6 Headspace app subscriptions
  • H6 Human care services
  • H6 Businesses
  • H6 Explore the blog
  • H6 Mental health articles
  • H6 Meditation articles
  • H6 Mindfulness articles
  • H6 Sleep articles
  • H6 Resources for business
  • H6 About Headspace
  • H6 Our expertise
  • H6 Join us
  • H2 all with Headspace
  • H2 What kind of headspace are you looking for?
  • H2 The mental health app for every moment
  • H3 Always-there support
  • H3 Feel-good 
library
  • H3 Bedtime essentials
  • H3 Do-anywhere exercises
  • H3 Convenient online therapy
  • H2 Members are enjoying happier and healthier lives
  • H2 Over 4,000 leading organizations choose Headspace
  • H2 Explore our library
  • H5 Meet Ebb skipped
  • H5 Wiggle to Wind Down
  • H5 Mindful Families Collection
  • H5 Politics Without Panic
  • H5 Headspace XR
  • H5 Mental Strength Training
  • H5 LinkedIn Life Skills
  • H2 Join the millions who use Headspace every day
  • H2 Frequently asked questions
  • H4 Get some Headspace skipped
  • H4 Our content
  • H4 About us
  • H4 Support
  • H4 My Headspace
  • H4 Get the app

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <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
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 22 passed
REVIEW
80

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.

ARIA

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1
div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1 div.css-dymk12 > div.css-2ohn2g > div.css-13ndvf0 > div.css-1z038j1

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ebb div.css-fpmqj3 > svg > g > g
You div.css-fpmqj3 > svg > g > g

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#navbar-header-header > div.css-1b5cois > nav.css-4kugue > button.css-v74ccp header#navbar-header-header > div.css-1b5cois > nav.css-4kugue > button.css-v74ccp
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5
div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5 div.css-hfwumi > div.css-13unig > div > button.css-1qi2pw5

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.

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
Stress less div.css-gd0lmb > div.css-14ntoh4 > div.css-h02uj7 > div.css-m6qmz1
0.0k div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1vuavp0
meditating div.css-15vu3re > div.css-12uavp7 > div.css-10xddwb > p.css-1xr9gj
Join the millions who use Headspace every day div.css-1m771rd > div.css-15vu3re > div.css-12uavp7 > h2.css-161yfi3
App Store Rating div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Downloads div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
0M+ div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-3kok21
Minutes Meditated div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm
Selected Awards div.css-12uavp7 > div.css-ulqck6 > div.css-3io4e8 > p.css-1vw7yqm

These are opportunities to improve the legibility of your content.

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
Meet Ebb div.css-hsndhj > div.css-15vu3re > div.css-1kp8ita > h5.css-hblk6z
My Headspace div.css-1hg1vm1 > div.css-yh8ihz > div.css-1clntmr > h4.css-1j454q2

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-12nesms
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i
div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i div.css-b95f0i > div.css-fvg637 > div.deeper-dive-indicators > button.css-1hati0i

These items highlight common accessibility best practices.

○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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` 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
○Links are distinguishable without relying on color.
○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.
○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.
A+
Alt Text Quality
All 119 images OK
PASS
All 119 images OK
Info::
58 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
119 images 61 good alt text 58 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#audio-input-range-_r_1_rangeBreathe into Stressfor/id
#audio-input-range-_r_2_rangeSOS Racing Thoughtsfor/id
#audio-input-range-_r_3_rangeTravel Sleep Tipsfor/id
#subscription-email-form-inputemailemailaria-label
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)
ElementRatioRequiredFGBGResult
h2 all with Headspace19.25:13.0:1
#000000
#F9F4F2
Pass
h2 What kind of headspa…19.25:13.0:1
#000000
#F9F4F2
Pass
h2 The mental health ap…19.25:13.0:1
#000000
#F9F4F2
Pass
h2 Members are enjoying…19.25:13.0:1
#000000
#F9F4F2
Pass
h2 Over 4,000 leading o…19.25:13.0:1
#000000
#F9F4F2
Pass
h2 Explore our library19.25:13.0:1
#000000
#F9F4F2
Pass
h2 Join the millions wh…19.25:13.0:1
#000000
#F9F4F2
Pass
h2 Frequently asked que…19.25:13.0:1
#000000
#F9F4F2
Pass
h3 Always-there support19.25:13.0:1
#000000
#F9F4F2
Pass
h3 Feel-good 
library19.25:13.0:1
#000000
#F9F4F2
Pass
h3 Bedtime essentials19.25:13.0:1
#000000
#F9F4F2
Pass
h3 Do-anywhere exercise…19.25:13.0:1
#000000
#F9F4F2
Pass
h3 Convenient online th…19.25:13.0:1
#000000
#F9F4F2
Pass
title Mental Health App fo…14.08:14.5:1
#000000
#FFCE00
Pass
nobr HSA/FSA eligible: sa…14.08:14.5:1
#000000
#FFCE00
Pass
a For You21.00:14.5:1
#000000
#FFFFFF
Pass
a Meditation21.00:14.5:1
#000000
#FFFFFF
Pass
a Online therapy21.00:14.5:1
#000000
#FFFFFF
Pass
a Mindfulness21.00:14.5:1
#000000
#FFFFFF
Pass
a Sleep21.00:14.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.

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

Send Feedback