Skip to content
https://helpscout.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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: #4176fa
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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
Heading Hierarchy
Action
43 headings, 3 skip(s)
REVIEW
43 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
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.
  • H4 By industry
  • H1 The most intuitivecustomer support platform
  • H3 Clarity where it counts skipped
  • H3 Built for real teamwork
  • H3 AI that multiplies your team
  • H6 Lindsay Cohen skipped
  • H2 One home for all your support conversations
  • H2 Plus, all the little things support teams love
  • H3 Get a boost from AI
  • H3 Company management
  • H3 Snooze
  • H3 Send later
  • H3 Workflows
  • H3 Saved replies
  • H3 Multiple Inboxes
  • H3 Channels
  • H3 Meet Beacon: your embeddable support hub
  • H4 Answer instantly with AI
  • H4 Keep human help within reach
  • H4 Save customers time
  • H3 Get closer to customers with in-app messages
  • H4 Welcome and onboard
  • H4 Gather feedback and NPS®
  • H4 Share what’s new
  • H3 Reporting that tells a story
  • H4 “What’s our volume across channels?”
  • H4 “How’s our response time?”
  • H4 “Where can we improve?”
  • H3 Stay organized automatically
  • H4 Assign the right person for the job
  • H4 Never miss important messages
  • H4 Simplify the queue for your team
  • H3 100+ powerful integrations
  • H2 Why do 12,000+ companies choose Help Scout?
  • H3 World-class support
  • H3 Ease of use
  • H3 Built to scale
  • H2 Start for Free
  • H4 Product skipped
  • H4 Solutions
  • H4 Compare
  • H4 Company
  • H4 Support

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

B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Help Scout
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Help Scout ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode ✗
Name Help Scout Theme Color #4176fa Background Color #ffffff Icons 2 icon(s)
A+
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer
A+
Alt Text Quality
All 113 images OK
PASS
All 113 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
55 decorative image(s) correctly marked
Info::
56 image(s) with good alt text
113 images 56 good alt text 55 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 One home for all you…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Plus, all the little…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Why do 12,000+ compa…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Start for Free20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Clarity where it cou…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Built for real teamw…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 AI that multiplies y…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Get a boost from AI20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Company management20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Snooze20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Send later20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Workflows20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Saved replies20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Multiple Inboxes20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Channels20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Meet Beacon: your em…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Get closer to custom…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Reporting that tells…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Stay organized autom…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 100+ powerful integr…20.65:13.0:1
#000000
#FDFDFD
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 98/100 — 1 failing, 27 passed
PASS
98

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.

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
Clarity where it counts div.BentoBoxBlock--Card > div.content > div > h3.type--headline-semibold-L
Lindsay Cohen div.attribution > div.AvatarWithName > div.has-bio > h6.type--headline-semibold-S
Product div.container > div.flex > div.SiteFooter--column > h4.type--headline-medium-S

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
●`[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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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 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
○`<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
○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.
○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
○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.

Send Feedback