Skip to content
https://www.zendesk.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Heading Hierarchy
Action
43 headings, 3 skip(s)
FIX
43 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 Platform
  • H5 Products
  • H5 Solutions
  • H5 Resources
  • H2 Zendesk Relate 2026
  • H5 Pricing skipped
  • H5 Sign in
  • H5 Language
  • H2 Zendesk Relate 2026
  • H1 Deliver beautifully simple service with Zendesk AI Agents
  • H2 Trusted by 100,000+ companies
  • H2 (empty)
  • H3 Secure your spot
  • H3 Ali Wong
  • H2 Self‑improving AI Agents on any platform
  • H2 Zendesk named a Strong Performer in The Forrester Wave™
  • H2 Recognized by industry leaders
  • H2 The complete customer service solution
  • H2 Make employee service effortless
  • H2 Improve faster with the Resolution Learning Loop™
  • H2 Additional resources
  • H2 Exceed every customer expectation
  • H2 Maximize your ROI
  • H3 Improve time to value
  • H3 Reduce effort per ticket
  • H3 Keep costs low
  • H2 Powering 100,000+ of the best customer and employee experiences
  • H2 Footer
  • H5 Products skipped
  • H5 Features
  • H5 Resources
  • H5 Company
  • H5 Trending
  • H3 Products
  • H3 Features
  • H3 Resources
  • H3 Company
  • H3 Trending
  • H3 How can we help? Contact us.
  • H2 Do Not Sell or Share My Personal Information
  • H4 "Sale" and "Sharing" Third-Party Cookies skipped
  • H4 Essential Cookies
  • H3 Cookie List

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
9 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 9 <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 Page not found | Zendesk ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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 Missing
✓ Multiple Sizes Present
A
Landmark Structure
23 landmarks
PASS
23 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
3 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN ASIDE "top-promo-promo-2002959398" 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 98 images OK
PASS
All 98 images OK
Info::
48 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
98 images 50 good alt text 48 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#:Rld1q5k676:--inputemailWork emailaria-label
#:R55l1q5k676:--inputcheckboxI agree to Zendesk contacting me with marketing-related communications.for/id
#ot-group-id-SPD_BGcheckbox"Sale" and "Sharing" Third-Party Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/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 Deliver beautifully …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Zendesk Relate 202621.00:13.0:1
#000000
#FFFFFF
Pass
h2 Zendesk Relate 202621.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by 100,000+ …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Self‑improving AI …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Zendesk named a Stro…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recognized by indust…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The complete custome…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make employee servic…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Improve faster with …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Additional resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Exceed every custome…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Maximize your ROI21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Powering 100,000+ of…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Footer21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Do Not Sell or Share…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Secure your spot21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ali Wong21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Improve time to valu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Reduce effort per ti…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 95/100 — 2 failing, 31 passed
PASS
95

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.

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
Products div.StyledCol-sc-inuw62-0 > div.StyledAccordion-sc-niv9ic-0 > div.StyledSection-sc-v2t9bd-0 > div.StyledHeader-sc-2c6rbr-0

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
Testimonial 1 div#quoteCarouselWrapper > div.sc-9cc5ddc5-2 > nav.sc-9cc5ddc5-4 > button.sc-9cc5ddc5-3
Testimonial 2 div#quoteCarouselWrapper > div.sc-9cc5ddc5-2 > nav.sc-9cc5ddc5-4 > button.sc-9cc5ddc5-3
Testimonial 3 div#quoteCarouselWrapper > div.sc-9cc5ddc5-2 > nav.sc-9cc5ddc5-4 > button.sc-9cc5ddc5-3
Testimonial 4 div#quoteCarouselWrapper > div.sc-9cc5ddc5-2 > nav.sc-9cc5ddc5-4 > button.sc-9cc5ddc5-3
Pricing div.StyledInnerPanel-sc-8nbueg-0 > div.LinkGroupstyle__LinkGroupRoot-sc-e6je4r-0 > div > a.StyledButton-sc-qe3ace-0

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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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.
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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