Skip to content
https://pendo.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title #1 Global Software Experience Management Platform | Pendo.io ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
6 landmarks
REVIEW
6 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
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!) 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

A
Heading Hierarchy
28 headings, 1 skip(s)
PASS
28 headings, 1 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.
  • H1 The AI-powered analytics and adoption platform for builders
  • H3 Agent Analytics skipped
  • H3 Predict
  • H3 MCP
  • H3 Agent Mode
  • H3 35T
  • H3 1B+
  • H3 50K+
  • H2 Turn every release into a revenue moment
  • H3 Platform
  • H3 Solutions
  • H3 Resources
  • H3 Pricing
  • H3 See Pendo in action for yourself
  • H3 Customers
  • H3 Company
  • H3 Support
  • H3 Popular Links
  • H2 We live for product conversations.
  • H3 Platform
  • H3 Solutions
  • H3 Resources
  • H3 Pricing
  • H3 See Pendo in action for yourself
  • H3 Customers
  • H3 Company
  • H3 Support
  • H3 Popular Links

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

A+
Alt Text Quality
All 89 images OK
PASS
All 89 images OK
Info::
50 decorative image(s) correctly marked
Info::
39 image(s) with good alt text
89 images 39 good alt text 50 decorative
All images have appropriate alt text.
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 AI-powered analy…10.60:13.0:1
#000000
#FD9EA3
Pass
h2 Turn every release i…17.95:13.0:1
#000000
#ECEEE7
Pass
h2 We live for product …17.49:13.0:1
#060119
#ECEEE7
Pass
h3 Agent Analytics17.95:13.0:1
#000000
#ECEEE7
Pass
h3 Predict17.95:13.0:1
#000000
#ECEEE7
Pass
h3 MCP17.95:13.0:1
#000000
#ECEEE7
Pass
h3 Agent Mode17.95:13.0:1
#000000
#ECEEE7
Pass
h3 35T17.95:13.0:1
#000000
#ECEEE7
Pass
h3 1B+17.95:13.0:1
#000000
#ECEEE7
Pass
h3 50K+17.95:13.0:1
#000000
#ECEEE7
Pass
title Product Experience &…17.98:14.5:1
#000000
#EDEEE7
Pass
a Get a Demo17.98:14.5:1
#000000
#EDEEE7
Pass
button Platform17.86:14.5:1
#000000
#EDEDE6
Pass
button Solutions16.94:14.5:1
#000000
#EFE5DF
Pass
button Resources15.96:14.5:1
#000000
#F1DCD7
Pass
a Pricing14.71:14.5:1
#000000
#F3D0CC
Pass
a Login13.41:14.5:1
#000000
#F6C2C2
Pass
a Start for Free12.19:14.5:1
#000000
#F9B4B1
Pass
a Get a Demo11.49:14.5:1
#000000
#FBABA7
Pass
p Pendo connects your …10.35:14.5:1
#000000
#FD9C93
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, 23 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

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
Platform Analytics Guides Session Replay NPS Listen Feedback Validate Roadmap… div.builder-blocks > div.builder-block > section.css-88hukf > footer.builder-block
Legal Privacy Policy Manage Preferences 877.320.8484 © Pendo.io, Inc. All r… div.builder-blocks > div.builder-block > section.css-88hukf > div.builder-block

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 a demo -> div.builder-block > div.builder-block > span.builder-text > p
View all customer stories -> a.builder-block > div.builder-block > span.builder-text > p
“We’re div > blockquote.mb-8 > p.text-2xl > span.word
getting div > blockquote.mb-8 > p.text-2xl > span.word
input div > blockquote.mb-8 > p.text-2xl > span.word
[from div > blockquote.mb-8 > p.text-2xl > span.word
Pendo] div > blockquote.mb-8 > p.text-2xl > span.word
directly div > blockquote.mb-8 > p.text-2xl > span.word
inside div > blockquote.mb-8 > p.text-2xl > span.word
the div > blockquote.mb-8 > p.text-2xl > span.word
product, div > blockquote.mb-8 > p.text-2xl > span.word
right div > blockquote.mb-8 > p.text-2xl > span.word
as div > blockquote.mb-8 > p.text-2xl > span.word
users div > blockquote.mb-8 > p.text-2xl > span.word
interact div > blockquote.mb-8 > p.text-2xl > span.word
with div > blockquote.mb-8 > p.text-2xl > span.word
[our] div > blockquote.mb-8 > p.text-2xl > span.word
agents. div > blockquote.mb-8 > p.text-2xl > span.word
We’re div > blockquote.mb-8 > p.text-2xl > span.word
learning div > blockquote.mb-8 > p.text-2xl > span.word
whether div > blockquote.mb-8 > p.text-2xl > span.word
it’s div > blockquote.mb-8 > p.text-2xl > span.word
helping div > blockquote.mb-8 > p.text-2xl > span.word
them div > blockquote.mb-8 > p.text-2xl > span.word
do div > blockquote.mb-8 > p.text-2xl > span.word
their div > blockquote.mb-8 > p.text-2xl > span.word
job, div > blockquote.mb-8 > p.text-2xl > span.word
whether div > blockquote.mb-8 > p.text-2xl > span.word
it’s div > blockquote.mb-8 > p.text-2xl > span.word
actually div > blockquote.mb-8 > p.text-2xl > span.word
moving div > blockquote.mb-8 > p.text-2xl > span.word
pipeline. div > blockquote.mb-8 > p.text-2xl > span.word
That div > blockquote.mb-8 > p.text-2xl > span.word
kind div > blockquote.mb-8 > p.text-2xl > span.word
of div > blockquote.mb-8 > p.text-2xl > span.word
feedback div > blockquote.mb-8 > p.text-2xl > span.word
is div > blockquote.mb-8 > p.text-2xl > span.word
critical div > blockquote.mb-8 > p.text-2xl > span.word
to div > blockquote.mb-8 > p.text-2xl > span.word
building div > blockquote.mb-8 > p.text-2xl > span.word
the div > blockquote.mb-8 > p.text-2xl > span.word
right div > blockquote.mb-8 > p.text-2xl > span.word
agents—and div > blockquote.mb-8 > p.text-2xl > span.word
improving div > blockquote.mb-8 > p.text-2xl > span.word
them div > blockquote.mb-8 > p.text-2xl > span.word
fast.” div > blockquote.mb-8 > p.text-2xl > span.word
VP of Product, Demandbase div.flex > div.flex > div > p.text-sm
Visit the Trust Center -> a.builder-block > div.builder-block > span.builder-text > p
Get a demo -> a.builder-block > div.builder-block > span.builder-text > p

These are opportunities to improve the legibility of your content.

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
MCP div#panel-2-content > div.flex > div.flex > h3.text-white

These are opportunities to improve keyboard navigation in your application.

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.__variable_f8506d html.__variable_f8506d

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
●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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○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
○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