Accessibility

F

Heading Hierarchy

Action

44 headings, 5 skip(s)

FIX

44 headings, 5 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H6 "I can't believe it's free!"
H6 "Your AI Agent replaced me!"
H6 "I just want to hug you!"
H1 How millions of companies help chat with service inform wow educate reply to delight
H1 How millionsof companies help chat with service inform wow educate reply to delight duplicate H1
H6 All your Live Chat Ticketing Knowledge Base CRM and Chat Pages in one, organized place. 100% Free - Read why skipped
H6 All your Live Chat Ticketing Knowledge Base CRM and Chat Pages in one, organized place. 100% Free - Read why
H6 Over 3 Billion people interact with a tawk.to widget every month
H2 Why tawk.to?
H5 Because you need a free and easy way to communicate with your customers skipped
H2 Get close
H2 Get organized
H2 Get in front
H3 How does it work?
H2 Add a small JavaScript snippet to your site — it takes 30 seconds to get started
H2 Don't take our word for it though ...
H2 See how 5+ MILLION people use tawk.to to get closer to their customers
H3 All the Features, without the price tag
H2 A truly customizable live chat and customer communication platform packed with premium features
H6 ..and much, much more. skipped
H3 Have questions?
H2 Let's do our best to answer your most frequently asked questions
H5 How many agents can we add? skipped
H5 How can you offer this for free?
H5 Do you limit the number of concurrent chats?
H5 Is our data safe?
H5 Will I ever be charged to use the software?
H5 Are there any Ads?
H5 How do I get support?
H5 Where can I find documentation?
H5 Do you offer a self-hosted solution?
H5 How many businesses use tawk.to?
H5 When is your next Meetup?
H5 Where are you based?
H3 “You shouldn't have to pay to chat with the visitors on your website. They're your visitors!”
H3 Forever Free. It's that simple.
H2 People prefer to message
H6 120s set-up • Free Forever • Secure skipped
H3 Get tawk.to
H3 Products
H3 Services
H3 Resources
H3 About
H3 Let's tawk?

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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)

Skip navigation link detected

8 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 8 <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

23 landmarks

REVIEW

23 landmarks

No <main> landmark found

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

8 <nav> landmark(s) found

4 of 8 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

B

Alt Text Quality

2 of 39 images have issues

REVIEW

2 of 39 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

29 decorative image(s) correctly marked

8 image(s) with good alt text

39 images 8 good alt text 29 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C

Link & Button Quality

Action

4 issue(s) across 352 links and 0 buttons

REVIEW

4 issue(s) across 352 links and 0 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.tawk.to/; https://www.tawk.to/; https://www.tawk.to/; https://www.tawk.to/

11 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://help.tawk.to/; https://dashboard.tawk.to/signup; https://www.tawk.to/tawk-to-for-windows/; https://help.tawk.to/; https://developer.tawk.to/; https://status.tawk.to/; https://www.linkedin.com/company/tawk-to; https://x.com/intent/follow?screen_name=tawktotawk; https://www.facebook.com/tawkto/; https://instagram.com/tawktotawk (+1 more)

337 link(s) with descriptive text

352 links

4 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.tawk.to/	(empty)	empty	Add link text or aria-label
https://www.tawk.to/	(empty)	empty	Add link text or aria-label
https://www.tawk.to/	(empty)	empty	Add link text or aria-label
https://www.tawk.to/	(empty)	empty	Add link text or aria-label
https://help.tawk.to/	found here	new tab	Add '(opens in new tab)' to text
https://dashboard.tawk.to/signup	Web Browser	new tab	Add '(opens in new tab)' to text
https://www.tawk.to/tawk-to-for-windows/	Windows	new tab	Add '(opens in new tab)' to text
https://help.tawk.to/	Help Center	new tab	Add '(opens in new tab)' to text
https://developer.tawk.to/	Developers	new tab	Add '(opens in new tab)' to text
https://status.tawk.to/	Status	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/tawk-to	Linkedin-in	new tab	Add '(opens in new tab)' to text
https://x.com/intent/follow?screen_name=…	Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/tawkto/	Facebook-f	new tab	Add '(opens in new tab)' to text
https://instagram.com/tawktotawk	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCmmsTnO…	Youtube	new tab	Add '(opens in new tab)' to text

337 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.tawk.to/; https://www.tawk.to/; https://www.tawk.to/; https://www.tawk.to/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://help.tawk.to/; https://dashboard.tawk.to/signup; https://www.tawk.to/tawk-to-for-windows/; https://help.tawk.to/; https://developer.tawk.to/; https://status.tawk.to/; https://www.linkedin.com/company/tawk-to; https://x.com/intent/follow?screen_name=tawktotawk; https://www.facebook.com/tawkto/; https://instagram.com/tawktotawk (+1 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title tawk.to | Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Lighthouse Accessibility Audits

Action

Score 78/100 — 8 failing, 22 passed

REVIEW

78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How many agents can we add? `div.elementor-widget-container > div.elementor-accordion > div.elementor-accordion-item > h5#elementor-tab-title-2451`
How do I get support? `div.elementor-widget-container > div.elementor-accordion > div.elementor-accordion-item > h5#elementor-tab-title-1851`

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
AI can now answer chats for you! `center > a > div.tag_highlight > span`
Forever Free. It's that simple. `div.elementor-widget-container > h3.elementor-headline > span.elementor-headline-dynamic-wrapper > span.elementor-headline-dynamic-text`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div#qp8vtg83dekk1776807389221 > iframe#s5412aje6k341776807389262 `body.home > div#qp8vtg83dekk1776807389221 > iframe#s5412aje6k341776807389262`

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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content `body.home > a.skip-link`

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.

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
All your Live Chat Ticketing Knowledge Base CRM and Chat Pages in one, organize… `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title`
Because you need a free and easy way to communicate with your customers `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5.elementor-heading-title`
..and much, much more. `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title`
120s set-up • Free Forever • Secure `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h6.elementor-headline`

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
Previous slide `div.elementor-widget-container > div.elementor-swiper > div.elementor-main-swiper > div.elementor-swiper-button`
Next slide `div.elementor-widget-container > div.elementor-swiper > div.elementor-main-swiper > div.elementor-swiper-button`
Go to slide 1 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`

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-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

●`[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

●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

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[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

○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

○Buttons have an accessible name

○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.

○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.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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+

Form Accessibility

No form controls

PASS

No form controls

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)

Element	Ratio	Required	FG	BG	Result
h2 Why tawk.to?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get close	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get organized	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get in front	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Add a small JavaScri…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Don't take our word …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See how 5+ MILLION p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A truly customizable…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Let's do our best to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 People prefer to mes…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How does it work?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 All the Features, wi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Have questions?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 “You shouldn't hav…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get tawk.to	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Let's tawk?	21.00:1	3.0: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.