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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
D
Heading Hierarchy
Action
41 headings, 2 skip(s)
FIX
41 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Where amazing customer experiences are built
  • H2 Build what matters
  • H2 The ultimate toolbox for customer engagement
  • H4 Messaging skipped
  • H4 Email
  • H4 Voice
  • H4 Authentication and identity
  • H4 Customer Data Platform
  • H2 Builder is a mindset, not a job title
  • H3 Ready, set, <code>
  • H3 Launch experiences like never before
  • H3 Personal is powerful. Boom.
  • H3 Break down dirty data siloes
  • H3 Don’t study benchmarks. Set them.
  • H2 Where innovation has no limitations.
  • H3 Shopify helps millions of merchants build customer relationships
  • H3 Cleveland Clinic personalized patient communications for better care
  • H3 Intuit built efficient customer authentication at global scale
  • H3 United Way scaled a support line to connect millions with social services
  • H3 Toyota Connected wins the race toward innovation with Twilio Flex
  • H2 Because average experiences never make headlines
  • H4 Make every interaction smarter with AI skipped
  • H4 Individualized experiences across channels
  • H4 Context at your fingertips with customer data
  • H4 Proven scale and trust
  • H2 We believe in building value, not hype
  • H2 TL;DR: Don’t wait for the future. Build it.
  • H2 Let's find the right products for you
  • H2 Generating your product picks...
  • H2 See your product picks
  • H1 Generating Toolkit... See your toolkit duplicate H1
  • H2 What's in your toolkit
  • H3 (empty)
  • H2 Add-ons to enhance your basic toolkit
  • H3 (empty)
  • H2 Ask about your toolkit
  • H2 Toolkit summary
  • H3 Products
  • H3 Add-ons
  • H2 Ready, set, build! Resources to get started
  • H2 Put the toolkit to use

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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
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::
4 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 4 <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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV MAIN ASIDE 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

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

C
Alt Text Quality
Action
12 of 34 images have issues
REVIEW
12 of 34 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
34 images 21 good alt text 1 decorative 12 missing
IssueCount
missing12 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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title An icon of a right chevron ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Twilio
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Twilio ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Twilio Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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 Where amazing customer experiences are b…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Generating Toolkit...
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
32px · bottom of viewport
h2 The ultimate toolbox for customer engage…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Builder is a mindset, not a job title
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Where innovation has no limitations.
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Because average experiences never make h…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 We believe in building value, not hype
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 TL;DR: Don’t wait for the future. Buil…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Let's find the right products …
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Generating your product pi…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 See your product picks
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What's in your toolkit
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Add-ons to enhance your basic toolkit
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ask about your toolkit
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Toolkit
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready, set, build! Resources to get star…
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Put the
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ready, set, <code>
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Launch experiences like never before
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Personal is powerful. Boom.
1.08:1
#000000
on
#000D25
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient

10 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 Where amazing custom…1.08:13.0:1
#000000
#000D25
Fail
h1 Generating Toolkit..…1.08:13.0:1
#000000
#000D25
Fail
h2 The ultimate toolbox…1.08:13.0:1
#000000
#000D25
Fail
h2 Builder is a mindset…1.08:13.0:1
#000000
#000D25
Fail
h2 Where innovation has…1.08:13.0:1
#000000
#000D25
Fail
h2 Because average expe…1.08:13.0:1
#000000
#000D25
Fail
h2 We believe in buildi…1.08:13.0:1
#000000
#000D25
Fail
h2 TL;DR: Don’t wait …1.08:13.0:1
#000000
#000D25
Fail
h2 Let's find the right…1.08:13.0:1
#000000
#000D25
Fail
h2 Generating your prod…1.08:13.0:1
#000000
#000D25
Fail
h2 See your product pic…1.08:13.0:1
#000000
#000D25
Fail
h2 What's in your toolk…1.08:13.0:1
#000000
#000D25
Fail
h2 Add-ons to enhance y…1.08:13.0:1
#000000
#000D25
Fail
h2 Ask about your toolk…1.08:13.0:1
#000000
#000D25
Fail
h2 Toolkit1.08:13.0:1
#000000
#000D25
Fail
h2 Ready, set, build! R…1.08:13.0:1
#000000
#000D25
Fail
h2 Put the1.08:13.0:1
#000000
#000D25
Fail
h3 Ready, set, <code>1.08:13.0:1
#000000
#000D25
Fail
h3 Launch experiences l…1.08:13.0:1
#000000
#000D25
Fail
h3 Personal is powerful…1.08:13.0:1
#000000
#000D25
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 86/100 — 5 failing, 26 passed
REVIEW
86

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Slide 1 of 5 div.slider > nav.slider-pagination > div.slider-dots > button.slider-button

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
Python logo div.layout-column > div.logo-list > div.logo-list-item > span
C# logo div.layout-column > div.logo-list > div.logo-list-item > span
PHP logo div.layout-column > div.logo-list > div.logo-list-item > span
Ruby logo div.layout-column > div.logo-list > div.logo-list-item > span
Java logo div.layout-column > div.logo-list > div.logo-list-item > span
JavaScript logo div.layout-column > div.logo-list > div.logo-list-item > span
Curl logo div.layout-column > div.logo-list > div.logo-list-item > span
AI assistant body#base-page-bc527d2ac7 > q-focus-sentinel > div
After AI assistant body#base-page-bc527d2ac7 > 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.

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
Messaging div.layout-container > div.layout-column > div.richtext > h4
Make every interaction smarter with AI div.layout-container > div.layout-column > div.richtext > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img
div.layout-column > figure.media > div.media-image--mobile > img div.layout-column > figure.media > div.media-image--mobile > img

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
Messaging Send, receive, and manage multichannel text messages on our globally… div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
Email Trusted Email API for email delivery at scale that you can implement in … div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
Voice Build voice experiences that increase customer satisfaction and unlock R… div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
Authentication and identity Fight fraud and keep customer accounts secure with… div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
Customer Data Platform Bring together clean, consented customer data for real-… div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
        Twilio named a Leader in 2025 Gartner® Magic Quadrant™ for CPaaS* … div.layout-container > div.layout-column > div#products-grid-1 > a.layout-column
Twilio named a Leader in 2025 Gartner® Magic Quadrant™ for CPaaS*     Downlo… div.layout-container > div.layout-column > div#we-believe-in > a.layout-column
Download report div.layout-container > div.layout-column > div.button-container > a.button
Twilio named a CPaaS Leader in 2025 IDC MarketScape       Download excerpt div.layout-container > div.layout-column > div#we-believe-in > a.layout-column
Download excerpt div.layout-container > div.layout-column > div.button-container > a.button
Twilio named a Leader in 2024-2025 IDC MarketScape for Worldwide Customer Data … div.layout-container > div.layout-column > div#we-believe-in > a.layout-column
Download excerpt div.layout-container > div.layout-column > div.button-container > a.button
○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 are valid and not misspelled
●Buttons have an accessible name
●`[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
●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 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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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 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
○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
○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.
○`[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.
○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
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearcharia-label
inputsearchSearcharia-label
inputtextEnter your use case or requirementsaria-label
inputtext(How can I help?)placeholder only

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

<input type="text">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback