Skip to content
https://livechatinc.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) ASIDE 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

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

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
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 This page doesn't exist | ChatBot | LiveChat.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
13 icon(s) detected
REVIEW
13 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 Present
✓ Multiple Sizes Present
A+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
  • H1 The live chat software that gets the job done
  • H2 LiveChat® is intuitive customer service software. Quick to set up, easy for your team to use and a go-to choice for your customers.
  • H2 Engage with live chat, sell with ease
  • H3 Sell more products with live chat online
  • H3 Sell more products with live chat online
  • H2 Make premium support your new standard
  • H3 Create a flawless experience with an online chat
  • H3 Create a flawless experience with an online chat
  • H2 Automate support and sales with AI customer service chatbots
  • H2 Boost your team’s performance with Copilot inside the app
  • H2 Connect with tools that support your business growth
  • H3 LiveChat® completes your customer shopping experience
  • H3 Bring your favorite tools together for a seamless workflow
  • H3 Bring your favorite tools together for a seamless workflow
  • H2 Monitor how live chat impacts your business
  • H3 Turn live chat data into exceptional customer care
  • H3 Turn live chat data into exceptional customer care
  • H2 They say... chatting has never been easier
  • H3 Kent Bicycles Service Center 🇺🇸
  • H3 The Cake Planner 🇺🇸
  • H3 MONTBLANC LMDM 🇦🇺
  • H3 ÓRTTU 🇺🇸
  • H3 Aylala 🇵🇱
  • H3 Luxurious Beds and Linens 🇨🇦
  • H3 X NIHILO 🇦🇺
  • H3 Store Supplies 🇺🇸
  • H3 Fromanteel Watches 🇺🇸
  • H3 TurkstraLumberLtd 🇨🇦
  • H3 MB Sentinel 🇺🇸
  • H3 JetSkiCovers 🇺🇸
  • H3 KORA Organics 🇺🇸
  • H3 PATH projects 🇺🇸
  • H3 South Horizon T-Shirt Company 🇺🇸
  • H3 ENDER LEGARD 🇬🇧
  • H3 White Rabbit Skin Care 🇬🇧
  • H3 CustomIcing.com.au 🇦🇺
  • H3 Security Store House 🇺🇸
  • H4 Simple pricing for every need
  • H4 Looking for an enterprise live chat solution?
  • H2 We’re here for you 24/7/365
A+
Alt Text Quality
All 149 images OK
PASS
All 149 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
4 decorative image(s) correctly marked
Info::
143 image(s) with good alt text
149 images 143 good alt text 4 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailBusiness Emailaria-label
emailemailBusiness Emailaria-label
urlurlWebsite addressaria-label
emailemailBusiness Emailaria-label
emailemailBusiness Emailaria-label
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: LiveChat
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name LiveChat ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name LiveChat Display Mode standalone Icons 2 icon(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 The live chat softwa…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 LiveChat® is20.82:13.0:1
#000000
#FEFEFE
Pass
h2 . Quick to set up, e…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 and a go-to choice f…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Engage with live cha…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Make premium support…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Automate support and…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Boost your team’s …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Connect with tools t…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Monitor how live cha…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 They say... chatting…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 We’re here for you…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Sell more products w…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Sell more products w…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Create a flawless ex…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Create a flawless ex…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 LiveChat® completes…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Bring your favorite …20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Bring your favorite …20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Turn live chat data …20.82:13.0:1
#000000
#FEFEFE
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 92/100 — 3 failing, 25 passed
PASS
92

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Get the full AI suite. Try Text platform aside.c-productbar > div.o-container-xl > div.b--u-py-1.5 > p.c-productbar__text

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
Get the full AI suite. Try Text platform aside.c-productbar > div.o-container-xl > div.b--u-py-1.5 > p.c-productbar__text
Try Text platform div.b--u-py-1.5 > p.c-productbar__text > a.u-text-white > strong.u-text-underline
AUTOMATE CUSTOMER SERVICE section.b--u-pt-6 > div.u-maxw-12 > div.u-text-center > p.b--u-text-xs

These are opportunities to improve the legibility of your content.

Best practices

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
●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
●Elements use only permitted ARIA attributes
●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
●Touch targets have sufficient size and spacing.
●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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback