Skip to content
https://freshdesk.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
B
Heading Hierarchy
35 headings
REVIEW
35 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Customer service that puts people first
  • H2 Introducing Vertical AI Agents and a new customer service home
  • H2 Seamless support. Smarter agents. Faster resolutions.
  • H2 Meet Freddy AI
  • H2 Join 74,000+ companies uncomplicating customer service
  • H2 The full customer service experience
  • H3 Omnichannel customer service
  • H3 Freshdesk Command Center
  • H3 Advanced ticketing
  • H3 Freddy AI Agent
  • H3 Freddy AI Copilot
  • H3 Freddy AI Insights
  • H3 Industry-leading results with Freshdesk
  • H2 Connect your business apps
  • H2 The experts agree
  • H2 Explore insights & resources on AI-powered customer service
  • H3 2025 Customer Service Report
  • H3 Forrester on the TEI of Freshworks
  • H2 Get started with Freshdesk
  • H3 Free to try. Fast to scale.
  • H3 See rapid impact in action
  • H3 Learn, explore, get inspired
  • H3 Login to account
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H4 Your Privacy
  • H3 Strictly Necessary Cookies
  • H4 Strictly Necessary Cookies
  • H3 Functional Cookies
  • H4 Functional Cookies
  • H3 Performance Cookies
  • H4 Performance Cookies
  • H3 Targeting Cookies
  • H4 Targeting Cookies
  • H3 Advertising Cookies

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 404 Page ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

A+
Alt Text Quality
All 106 images OK
PASS
All 106 images OK
Info::
47 decorative image(s) correctly marked
Info::
59 image(s) with good alt text
106 images 59 good alt text 47 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 15 controls labeled
PASS
All 15 controls labeled
Info::
15 control(s) properly labeled
15 controls
15 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#:r0:textFirst name *for/id
#:r1:textLast name *for/id
#:r2:emailWork email *for/id
#:r3:textCompany name *for/id
#webinar-slot-196selectTime slot *for/id
disclaimer-checkboxcheckboxnone
consent-checkboxcheckboxnone
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor Searcharia-label
#select-all-vendor-leg-handlercheckboxSelect All Vendorsfor/id
#select-all-vendor-groups-handlercheckboxSelect All Vendorsfor/id
#select-all-hosts-groups-handlercheckboxSelect All Hostsfor/id
#storage-access-groupcheckboxInformation storage and accessfor/id
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 Customer service tha…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Introducing Vertical…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Seamless support. Sm…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet Freddy AI21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join 74,000+ compani…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The full customer se…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect your busines…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The experts agree21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore insights & r…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get started with Fre…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Omnichannel customer…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Freshdesk Command Ce…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Advanced ticketing21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Freddy AI Agent21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Freddy AI Copilot21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Freddy AI Insights21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industry-leading res…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 2025 Customer Servic…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Forrester on the TEI…21.00:13.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.

A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 26 passed
PASS
90

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Close body#next-gen > div#wistia-video-301_popover_container

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
Study a.sc-ace17a57-0 > div.sc-ace17a57-0 > div.sc-ace17a57-0 > span.sc-b323b31-0

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Demo header.sc-6293d692-0 > nav.sc-6293d692-0 > div.sc-ace17a57-0 > li.sc-ace17a57-0

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Us div.sc-6293d692-0 > div.sc-ace17a57-0 > span.sc-b323b31-0 > a.sc-e5af17da-0
Investors div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Insights & Trends div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Training & Certification div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Student Academy div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
What’s New div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshservice for MSPs div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshservice for Business Teams div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshdesk Omni div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshchat div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshsales div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshsales Suite div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshmarketer div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freshworks Platform div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Freddy AI div.sc-6293d692-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Privacy Notice div.sc-ace17a57-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Site Terms div.sc-ace17a57-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Cookie Policy div.sc-ace17a57-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
Do Not Share My Personal Information div.sc-ace17a57-0 > ul.sc-ace17a57-0 > li.sc-6293d692-0 > a.sc-e5af17da-0
○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.
●`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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○`<frame>` or `<iframe>` elements have a title
○`<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
○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.
○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