Skip to content
https://klaviyo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Alt Text Quality
Action
23 of 124 images have issues
FIX
23 of 124 images have issues
Critical::
23 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
22 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
56 decorative image(s) correctly marked
Info::
45 image(s) with good alt text
124 images 45 good alt text 56 decorative 23 missing
IssueCount
missing23 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
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::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 8 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::
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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
emailemail(Email address)placeholder only
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Klaviyo ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 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 Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h1 AI marketing & service to grow relations…
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Meet Composer
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Autonomous agents that do the work
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Your data, intelligence, and AI agents w…
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fueling growth for brands that don’t s…
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport
h2 350+ pre-built integrations
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join the 193,000+ customers growing with…
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Frequently asked questions
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Marketing Agent
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Customer Agent
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Marketing that carries the conversation
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI built for every customer moment
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Service that solves and sells
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Analytics that deliver your next win
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CDP that gives you the full data story
1.18:1
#000000
on
#121A07
needs 3.0:1 (large text)
19px · bottom of viewport
title Klaviyo: AI Email Marketing & SMS | B2C …
1.26:1
#000000
on
#1D1E20
needs 4.5:1 (normal text)
16px · top of page (header area)
a ___
1.12:1
#000000
on
#0E1214
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.14:1
#000000
on
#141510
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.33:1
#000000
on
#202420
needs 4.5:1 (normal text)
16px · top of page (header area)
a Help center
3.31:1
#000000
on
#506459
needs 4.5:1 (normal text)
16px · above the fold

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI marketing & servi…1.18:13.0:1
#000000
#121A07
Fail
h2 Meet Composer1.18:13.0:1
#000000
#121A07
Fail
h2 Autonomous agents th…1.18:13.0:1
#000000
#121A07
Fail
h2 Your data, intellige…1.18:13.0:1
#000000
#121A07
Fail
h2 Fueling growth for b…1.18:13.0:1
#000000
#121A07
Fail
h2 350+ pre-built integ…1.18:13.0:1
#000000
#121A07
Fail
h2 Join the 193,000+ cu…1.18:13.0:1
#000000
#121A07
Fail
h2 Frequently asked que…1.18:13.0:1
#000000
#121A07
Fail
h3 Marketing Agent1.18:13.0:1
#000000
#121A07
Fail
h3 Customer Agent1.18:13.0:1
#000000
#121A07
Fail
h3 Marketing that carri…1.18:13.0:1
#000000
#121A07
Fail
h3 AI built for every c…1.18:13.0:1
#000000
#121A07
Fail
h3 Service that solves …1.18:13.0:1
#000000
#121A07
Fail
h3 Analytics that deliv…1.18:13.0:1
#000000
#121A07
Fail
h3 CDP that gives you t…1.18:13.0:1
#000000
#121A07
Fail
title Klaviyo: AI Email Ma…1.26:14.5:1
#000000
#1D1E20
Fail
a ___1.12:14.5:1
#000000
#0E1214
Fail
a Skip to main content1.14:14.5:1
#000000
#141510
Fail
a Home1.33:14.5:1
#000000
#202420
Fail
a Help center3.31:14.5:1
#000000
#506459
Fail

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
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
9 of 9 <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+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 AI marketing & service to grow relationships
  • H2 Meet Composer
  • H2 Autonomous agents that do the work
  • H3 Marketing Agent
  • H3 Customer Agent
  • H2 Your data, intelligence, and AI agents working as one
  • H3 Marketing that carries the conversation
  • H3 AI built for every customer moment
  • H3 Service that solves and sells
  • H3 Analytics that deliver your next win
  • H3 CDP that gives you the full data story
  • H2 Fueling growth for brands that don’t settle
  • H2 350+ pre-built integrations
  • H2 Join the 193,000+ customers growing with Klaviyo
  • H2 Frequently asked questions
A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 24 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

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 > q-focus-sentinel > div
After AI assistant body > 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
Powering 193,000+ relationship-driven brands across 100 countries div.homepage > section > div.section-content > p

These are opportunities to improve the legibility of your content.

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
Go to slide 1: Marketing that carries the conversation div.carousel-wrapper > div.carousel-controls > div.carousel-dots > button.carousel-dot
Go to slide 2: AI built for every customer moment div.carousel-wrapper > div.carousel-controls > div.carousel-dots > button.carousel-dot
Go to slide 3: Service that solves and sells div.carousel-wrapper > div.carousel-controls > div.carousel-dots > button.carousel-dot
Go to slide 4: Analytics that deliver your next win div.carousel-wrapper > div.carousel-controls > div.carousel-dots > button.carousel-dot
Go to slide 5: CDP that gives you the full data story div.carousel-wrapper > div.carousel-controls > div.carousel-dots > button.carousel-dot

These items highlight common accessibility best practices.

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
Watch video section > div.section-content > video-modal-trigger.video-modal-trigger > button.video-trigger
○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
●`[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 are distinguishable without relying on color.
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○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