Skip to content
https://qualtrics.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
F
Heading Hierarchy
Action
81 headings, 7 skip(s)
FIX
81 headings, 7 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Customer Experience
  • H3 What Qualtrics does:
  • H3 What you can achieve:
  • H4 Gartner® Magic Quadrant™ for Voice of the Customer 2026
  • H2 Employee Experience
  • H3 What Qualtrics does:
  • H3 What you can achieve:
  • H4 2025 Forrester Wave™: Employee Experience Management Platforms
  • H2 Market Research
  • H3 What Qualtrics does:
  • H3 What you can achieve:
  • H4 2026 Forrester Wave™: Experience Research Platforms
  • H2 By industry
  • H4 Healthcare trends shaping patient experience in 2026 skipped
  • H2 By team
  • H4 2026 Consumer Experience Trends Report skipped
  • H2 By use case
  • H4 2026 Employee Experience Trends Report skipped
  • H2 Popular resources
  • H4 Experience Live skipped
  • H2 Company
  • H4 See Qualtrics in action skipped
  • H2 X4 Summit
  • H4 See Qualtrics in action skipped
  • H2 Support
  • H3 Customer Experience
  • H4 What Qualtrics does:
  • H4 What you can achieve:
  • H4 Gartner® Magic Quadrant™ for Voice of the Customer 2026
  • H3 Employee Experience
  • H4 What Qualtrics does:
  • H4 What you can achieve:
  • H4 2025 Forrester Wave™: Employee Experience Management Platforms
  • H3 Market Research
  • H4 What Qualtrics does:
  • H4 What you can achieve:
  • H4 2026 Forrester Wave™: Experience Research Platforms
  • H3 By industry
  • H4 Healthcare trends shaping patient experience in 2026
  • H3 By team
  • H4 2026 Consumer Experience Trends Report
  • H3 By use case
  • H4 2026 Employee Experience Trends Report
  • H3 Popular resources
  • H4 Experience Live
  • H3 Company
  • H4 See Qualtrics in action
  • H3 X4 Summit
  • H4 See Qualtrics in action
  • H3 Change language
  • H1 The leader in experience management
  • H2 Give every decision the context it deserves
  • H2 Make experience your biggest advantage
  • H2 Stay ahead of market shifts
  • H3 How Qualtrics helps
  • H2 Turn moments into measurable outcomes
  • H3 How Qualtrics helps:
  • H2 Drive action everywhere it matters
  • H3 How Qualtrics helps:
  • H2 See how we’ve helped leading organizations
  • H2 Trust is not a feature. It’s our track record.
  • H2 The power of connected intelligence
  • H2 Listen
  • H2 Understand
  • H2 Act
  • H4 In a branch or online, give customers what they need—before they have to ask. skipped
  • H4 In a branch or online, give customers what they need—before they have to ask.
  • H4 In a branch or online, give customers what they need—before they have to ask.
  • H4 In a branch or online, give customers what they need—before they have to ask.
  • H2 The global destination for experience professionals
  • H2 Ready to build unbreakable loyalty?
  • H3 Request demo
  • H4 Thank you.
  • H3 What you can achieve
  • H3 What Qualtrics does
  • H3 Industries
  • H3 Teams
  • H3 Get support
  • H3 The Company
  • H3 Request a demo
  • H3 Thank you

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

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
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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 Present
✗ Multiple Sizes Missing
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
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 404 Page Not Found - Qualtrics ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <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 navigation" 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 39 images OK
PASS
All 39 images OK
Info::
39 image(s) with good alt text
39 images 39 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 23 controls labeled
PASS
All 23 controls labeled
Info::
23 control(s) properly labeled
23 controls
23 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#faV2-0-1radioListenfor/id
#faV2-0-2radioUnderstandfor/id
#faV2-0-3radioActfor/id
#edit-first-nametextFirst Name*for/id
#edit-last-nametextLast Name*for/id
#edit-companytextCompany*for/id
#edit-job-titletextJob Title*for/id
#edit-emailemailEmail*for/id
#edit-phone-numbertelPhone Number*for/id
#edit-countryselectCountry*for/id
#edit-lead-commentstextareaLead Commentsfor/id
#edit-marketing-optincheckboxYes, I would like to receive marketing communications regarding Qualtrics products, services, and eventsfor/id
#edit-privacy-optincheckboxPrivacy Optinfor/id
#edit-first-name--2textFirst Name*for/id
#edit-last-name--2textLast Name*for/id
#edit-company--2textCompany*for/id
#edit-job-title--2textJob Title*for/id
#edit-email--2emailEmail*for/id
#edit-phone-number--2telPhone Number*for/id
#edit-country--2selectCountry*for/id
#edit-lead-comments--2textareaLead Commentsfor/id
#edit-marketing-optin--2checkboxYes, I would like to receive marketing communications regarding Qualtrics products, services, and eventsfor/id
#edit-privacy-optin--2checkboxPrivacy Optinfor/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
h1 The leader in experi…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Give every decision …18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Make experience your…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Stay ahead of market…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Turn moments into m…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Drive action everywh…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 See how we’ve help…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 organizations18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Trust is not a featu…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 The power of connect…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Listen18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Understand18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Act18.61:13.0:1
#000000
#EDF2F4
Pass
h2 The global destinati…18.61:13.0:1
#000000
#EDF2F4
Pass
h2 Ready to build unbre…18.61:13.0:1
#000000
#EDF2F4
Pass
h3 What Qualtrics does:18.61:13.0:1
#000000
#EDF2F4
Pass
h3 What you can achieve…18.61:13.0:1
#000000
#EDF2F4
Pass
h3 What Qualtrics does:18.61:13.0:1
#000000
#EDF2F4
Pass
h3 What you can achieve…18.61:13.0:1
#000000
#EDF2F4
Pass
h3 What Qualtrics does:18.61:13.0:1
#000000
#EDF2F4
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, 27 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

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
AI assistant body.path-frontpage > q-focus-sentinel > div
After AI assistant body.path-frontpage > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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
Feedback div.QSIFeedbackButton > button#QSIFeedbackButton-btn > div > div

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
In a branch or online, give customers what they need—before they have to ask. div#tab-panel-83711 > div.tab-module-item__content > div.tab-module-item__headline > h4.headline--h4

These are opportunities to improve keyboard navigation in your application.

○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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`<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