Skip to content
https://helpguide.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Heading Hierarchy
Action
50 headings, 4 skip(s)
FIX
50 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
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.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Choose a Therapist
  • H1 Your trusted guide to mental health & wellness
  • H2 We empower you with the knowledge and skills you need to strengthen your mental health & well-being
  • H6 Guidance you can trust skipped
  • H6 Skills for life success
  • H6 Strategies to feel better
  • H6 Support you can rely on
  • H4 Recognized as a transparent and trustworthy nonprofit provider of quality health information
  • H6 Guidestar Platinum Transparency 2023 skipped
  • H6 HONcode standard for trustworthy health information
  • H6 Great Nonprofits 2022 Top Rated
  • H6 Featuring content created exclusively with Harvard Health
  • H2 Find the help you need today
  • H2 Editor’s Picks
  • H3 The Best Online Therapy Platforms
  • H3 Borderline Personality Disorder (BPD)
  • H3 Cutting and Self-Harm
  • H3 Recovering from Rape and Sexual Trauma
  • H3 ADHD in Adults
  • H3 Anxiety
  • H3 How to Stop Worrying
  • H3 Panic Attacks and Panic Disorder
  • H3 Overcoming Social Anxiety Disorder
  • H3 Addiction
  • H3 How to Stop Self-Medicating Depression, Anxiety, and Stress
  • H3 How to Help Someone with Mental Illness Accept Treatment
  • H3 Alcoholism and Alcohol Abuse
  • H3 Stress
  • H3 Stress Management
  • H3 Coping with Financial Stress
  • H3 Burnout Symptoms and Coping Tips
  • H2 The story of Morgan Leslie Segal
  • H2 Help us help others
  • H2 Join Our Newsletter
  • H2 Meditation
  • H3 Body Scan Meditation
  • H3 Coping with Uncertainty Meditation
  • H3 Gratitude in Difficult Times
  • H3 Mindful Breathing Meditation
  • H2 How HelpGuide.org changes lives
  • H2 We’re guided by leading experts in mental health and wellness
  • H4 Michael Craig Miller, M.D. skipped
  • H4 Ted Hutman, Ph.D.
  • H4 Fernando Torres-Gil, Ph.D.
  • H4 Marti Glenn, Ph.D.
  • H4 Anna Glezer, M.D.
  • H4 Laura Trejo, MSG, MPA
  • H2 Topics A-Z
  • H5 Join Our Newsletter skipped
  • H5 Mental Health Helplines

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

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

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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 3 <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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 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="gform_submit_button_11">; <input type="submit" id="gform_submit_button_12">
Info::
5 control(s) properly labeled
7 controls
5 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#therapist-location-mobiletextFind a therapistfor/id
#therapist-location-desktoptextFind a therapistfor/id
ssearchnone
#input_11_1emailEmailfor/id
#input_12_1emailEmailfor/id
#gform_submit_button_11submit(none)none
#gform_submit_button_12submit(none)none

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

<input type="submit" id="gform_submit_button_11">; <input type="submit" id="gform_submit_button_12">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – HelpGuide.org ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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

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
div.betterhelp-therapist-search > form#therapist-location-mobile-form > div.input-group > button#therapist-location-mobile-search-btn div.betterhelp-therapist-search > form#therapist-location-mobile-form > div.input-group > button#therapist-location-mobile-search-btn
div.mobile-search > div.mobile-search-inner > form.search-form > button.search-submit div.mobile-search > div.mobile-search-inner > form.search-form > button.search-submit

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.featured-topics > div.featured-topic-col > div.featured-topic > a.image-wrapper div.featured-topics > div.featured-topic-col > div.featured-topic > a.image-wrapper
div.featured-topics > div.featured-topic-col > div.featured-topic > a.image-wrapper div.featured-topics > div.featured-topic-col > div.featured-topic > a.image-wrapper

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
Our Mission div.row > div.col-8 > div.section-content > div.section-overline
See All div.container > div.section-header > a.btn > span

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
Guidance you can trust div > div.goal-col > div.goal > h6.goal-title
Guidestar Platinum Transparency 2023 div.credentials-wrapper > div.credentials > div.credential > h6.credential-title
Michael Craig Miller, M.D. div.section-experts > div.experts > div.expert > h4.expert-title
Join Our Newsletter div.footer-main-inner > div.footer-widgets > div.footer-widget > h5.footer-widget-title

These are opportunities to improve keyboard navigation in your application.

○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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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
●`[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.
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 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.
○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 41 images OK
PASS
All 41 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
5 decorative image(s) correctly marked
Info::
31 image(s) with good alt text
41 images 31 good alt text 5 decorative
IssueCount
too long5 image(s)
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
h1 Your19.32:13.0:1
#000000
#F9F5EE
Pass
h1 mental health & well…19.32:13.0:1
#000000
#F9F5EE
Pass
h2 you with the knowled…19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Find the help you ne…19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Editor’s Picks19.32:13.0:1
#000000
#F9F5EE
Pass
h2 The story of Morgan19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Help us19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Join Our Newsletter19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Meditation19.32:13.0:1
#000000
#F9F5EE
Pass
h2 How HelpGuide.org ch…19.32:13.0:1
#000000
#F9F5EE
Pass
h2 We’re guided by le…19.32:13.0:1
#000000
#F9F5EE
Pass
h2 Topics A-Z19.32:13.0:1
#000000
#F9F5EE
Pass
h3 Choose a Therapist19.32:13.0:1
#000000
#F9F5EE
Pass
h3 Anxiety19.32:13.0:1
#000000
#F9F5EE
Pass
h3 Addiction19.32:13.0:1
#000000
#F9F5EE
Pass
h3 Stress19.32:13.0:1
#000000
#F9F5EE
Pass
title HelpGuide.org – Yo…20.83:14.5:1
#000000
#FFFEFC
Pass
span Español20.83:14.5:1
#000000
#FFFEFC
Pass
a About Us19.50:14.5:1
#000000
#EEFFA7
Pass
a About Us19.50:14.5:1
#000000
#EEFFA7
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