Skip to content
https://www.intercom.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
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'>.
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
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: #050505
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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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.
C
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title Intercom Boilerplate ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 23 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.

ARIA

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
Discord div.overflow-hidden > div.flex > div.flex > div.shrink-0
API div.overflow-hidden > div.flex > div.flex > div.shrink-0
Email div.overflow-hidden > div.flex > div.flex > div.shrink-0
Facebook Messenger div.overflow-hidden > div.flex > div.flex > div.shrink-0
Instagram div.overflow-hidden > div.flex > div.flex > div.shrink-0
Messenger div.overflow-hidden > div.flex > div.flex > div.shrink-0
Slack div.overflow-hidden > div.flex > div.flex > div.shrink-0
Voice div.overflow-hidden > div.flex > div.flex > div.shrink-0
WhatsApp div.overflow-hidden > div.flex > div.flex > div.shrink-0

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.

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
A fully-featured div.col-span-full > div.col-span-12 > h2.text-heading-2 > span.text-current/40
to resolve queries faster, deliver personalized service, engage proactively, an… div.col-span-full > div.col-span-12 > p.text-callout > span.text-current/40
Convert any conversation into a ticket with one click, automatically categorize… h3.group > button#base-ui-_R_ajb5fiv6budbH2_ > div.text-current/70 > p.text-body
Build powerful automations to route conversations, manage SLAs, and configure e… h3.group > button#base-ui-_R_ejb5fiv6budbH2_ > div.text-current/70 > p.text-body
Deliver tailored experiences div.col-span-full > div.col-span-full > h3.text-heading-3 > span.text-current/40
at the right moment div.col-span-full > div > h3.text-heading-3 > span.text-current/40
Keep customers informed about new features, known issues, and policy changes wi… h3.group > button#base-ui-_R_1adb5fiv6budbH2_ > div.text-current/70 > p.text-body
Build omnichannel message journeys with a no-code visual builder, targeting cus… h3.group > button#base-ui-_R_1qdb5fiv6budbH2_ > div.text-current/70 > p.text-body
every interaction div.col-span-full > div > h3.text-heading-3 > span.text-current/40
Monitor every AI and human conversation in real time, with AI-powered scoring a… h3.group > button#base-ui-_R_1alb5fiv6budbH2_ > div.text-current/70 > p.text-body
Access pre-built reports covering every support use case, and a fully customiza… h3.group > button#base-ui-_R_1qlb5fiv6budbH2_ > div.text-current/70 > p.text-body

These are opportunities to improve the legibility of your content.

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
Learn more div.border-linen > div#base-ui-_R_6jb5fiv6budbH1_ > div > a.font-sans!
Learn more div.border-linen > div#base-ui-_R_qdb5fiv6budbH1_ > div > a.font-sans!
Learn more div.border-linen > div#base-ui-_R_qlb5fiv6budbH1_ > div > a.font-sans!
Terms div#footer-terms-and-conditions > div.flex > div.flex > a.text-base
Privacy div#footer-terms-and-conditions > div.flex > div.flex > a.text-base
Security div#footer-terms-and-conditions > div.flex > div.flex > a.text-base

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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
●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 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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
  • H1 The only helpdesk designed for the AI Agent era
  • H2 A complete solution for AI and human agents
  • H3 AI-powered agent workspace
  • H3 A seamless experience for customers and agents
  • H3 AI-powered Insights across every interaction
  • H3 A self-improving system
  • H3 A world-class AI Agent
  • H2 A fully-featured AI-powered helpdesk
  • H3 Resolve queries faster
  • H4 Copilot
  • H4 AI-enhanced ticketing
  • H4 No code automations
  • H4 Copilot+-
  • H4 AI-enhanced ticketing+-
  • H4 No code automations+-
  • H3 Deliver tailored experiences across every channel
  • H4 Omnichannel
  • H4 Live customer intelligence
  • H4 Apps and integrations
  • H3 Engage customersat the right moment
  • H4 Onboarding tools
  • H4 Proactive notifications
  • H4 Targeted messaging sequences
  • H4 Onboarding tools+-
  • H4 Proactive notifications+-
  • H4 Targeted messaging sequences+-
  • H3 Monitor and improve every interaction
  • H4 Insights
  • H4 Always-on QA
  • H4 Reporting
  • H4 Insights+-
  • H4 Always-on QA+-
  • H4 Reporting+-
  • H2 A true partner with deep domain expertise
  • H3 The company you can trust
  • H3 Expert support, at every stage
  • H3 The AI Agent Blueprint
  • H2 Transparent pricing
  • H3 Intercom with Fin
  • H2 Perfect customer experiences, powered by Intercom
A
Alt Text Quality
6 of 79 images have issues
PASS
6 of 79 images have issues
Warning::
6 image(s) with generic alt text
Info::
73 image(s) with good alt text
79 images 73 good alt text 6 generic
IssueCount
generic6 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
h1 The only helpdesk de…14.45:13.0:1
#000000
#D6D6D6
Pass
h2 A complete solution21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI-powered helpdesk21.00:13.0:1
#000000
#FFFFFF
Pass
h2 deep domain expertis…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Transparent pricing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Perfect customer exp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI-powered agent wor…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A seamless experienc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI-powered Insights …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A self-improving sys…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A world-class AI Age…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resolve queries fast…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 across every channel21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Engage customers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Monitor and improve21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The company you can …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Expert support, at e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The AI Agent Bluepri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Intercom with Fin21.00:13.0:1
#000000
#FFFFFF
Pass
title Intercom | The only …18.88:14.5:1
#000000
#F4F3EC
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