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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-noau7d
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Segment | Customer Data Platform (CDP)
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Segment | Customer Data Platform (CDP) ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Segment | Customer Data Platform (CDP) Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 header MAIN ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 1 pass AA only
h1 Segment ❤️ Twilio. We're finally mov…
1.04:1
#000000
on
#000716
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
h2 Same CDP, new home base.
1.04:1
#000000
on
#000716
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
h2 Collect real-time data in unified profil…
1.04:1
#000000
on
#000716
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Resources to learn, build, or troublesho…
1.04:1
#000000
on
#000716
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
a Support Plans
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
a Partner Solutions
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
a API Status
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
a Login
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
span Contact sales
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
span Start for free
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
span Contact sales
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
span Start for free
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · above the fold
span We're merging our websites to make thing…
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Twilio.com
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Visit Twilio.com
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span See what's possible
1.04:1
#000000
on
#000716
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

8 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 Segment ❤️ Twili…1.04:13.0:1
#000000
#000716
Fail
h2 Same CDP, new home b…1.04:13.0:1
#000000
#000716
Fail
h2 Collect real-time da…1.04:13.0:1
#000000
#000716
Fail
h2 Resources to learn, …1.04:13.0:1
#000000
#000716
Fail
title Twilio Segment Custo…6.76:14.5:1
#000000
#929294
Pass
a ___7.11:14.5:1
#000000
#969697
Pass
button Support7.37:14.5:1
#000000
#999999
Pass
a Help Center7.37:14.5:1
#000000
#999999
Pass
a Support Plans1.04:14.5:1
#000000
#000716
Fail
a Partner Solutions1.04:14.5:1
#000000
#000716
Fail
a API Status1.04:14.5:1
#000000
#000716
Fail
a Login1.04:14.5:1
#000000
#000716
Fail
span Contact sales1.04:14.5:1
#000000
#000716
Fail
span Start for free1.04:14.5:1
#000000
#000716
Fail
span Contact sales1.04:14.5:1
#000000
#000716
Fail
span Start for free1.04:14.5:1
#000000
#000716
Fail
span We're merging our we…1.04:14.5:1
#000000
#000716
Fail
a Twilio.com1.04:14.5:1
#000000
#000716
Fail
span Visit Twilio.com1.04:14.5:1
#000000
#000716
Fail
span See what's possible1.04:14.5:1
#000000
#000716
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 27 passed
REVIEW
88

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No Yes div.prefPanel > div > div.cookiecat > div.switch
No Yes div.prefPanel > div > div.cookiecat > div.switch

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pop-outerdiv07877461049271264 > div#pop-div205010762741367273 > div#pop-div308067838302903054 > div#pop-frame037344766296205445 div#pop-outerdiv07877461049271264 > div#pop-div205010762741367273 > div#pop-div308067838302903054 > div#pop-frame037344766296205445

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
Customer data pipeline div.layout-container > div.layout-column > div.richtext > h5
Required Cookies div.cookiecat > div > span.gwt-InlineHTML > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.footer > div.right > a div > div.footer > div.right > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of 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
VIEW REQUIRED COOKIES div.prefPanel > div > div.cookiecat > a.viewcookie
DETAILED SETTINGS div.prefPanel > div > div.cookiecat > a.viewcookie
No div > div.cookiecat > div.switch > span.gwt-InlineHTML
Yes div > div.cookiecat > div.switch > span.gwt-InlineHTML
DETAILED SETTINGS div.prefPanel > div > div.cookiecat > a.viewcookie
No div > div.cookiecat > div.switch > span.gwt-InlineHTML
Yes div > div.cookiecat > div.switch > span.gwt-InlineHTML
○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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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.
○`<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.
○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.
A
Heading Hierarchy
6 headings, 1 skip(s)
PASS
6 headings, 1 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.
  • H1 Segment ❤️ Twilio. We're finally moving in together on Twilio.com!
  • H2 Same CDP, new home base.
  • H2 Collect real-time data in unified profiles—and so much more
  • H5 Customer data pipeline skipped
  • H5 Customer Data Platform
  • H2 Resources to learn, build, or troubleshoot

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
1 of 9 images have issues
PASS
1 of 9 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
9 images 5 good alt text 1 decorative 1 missing
IssueCount
missing1 image(s)
too long2 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

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback