Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Alt Text Quality

Action

4 of 70 images have issues

REVIEW

4 of 70 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

42 decorative image(s) correctly marked

24 image(s) with good alt text

70 images 24 good alt text 42 decorative 4 missing

Issue	Count
missing	4 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

Link & Button Quality

10 issue(s) across 85 links and 117 buttons

REVIEW

10 issue(s) across 85 links and 117 buttons

10 button(s) with no accessible text

85 link(s) with descriptive text

85 links

0 empty

0 generic text

0 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

192 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title This Page Does Not Exist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA

h1 The World’s Most  Experienced Driver

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Meet Waymo

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why they ride with Waymo

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Waymo Driver

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our commitment to safety

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our mission: Be the world’s most trust…

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Footnotes

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Serving Riders In

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Up Next

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet the technology behind it all

1.13:1

#000000

#06151C

needs 3.0:1 (large text)

19px · bottom of viewport

p Rides

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p The world’s first autonomous ride-hail…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Our service

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Where we operate

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

1 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)

Element	Ratio	Required	FG	BG	Result
h1 The World’s Most �…	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Meet Waymo	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Why they ride with W…	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Waymo Driver	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Our commitment to sa…	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Our mission: Be the …	1.13:1	3.0:1	#000000	#06151C	Fail
h2 Footnotes	1.13:1	3.0:1	#000000	#06151C	Fail
h3 Serving Riders In	1.13:1	3.0:1	#000000	#06151C	Fail
h3 Up Next	1.13:1	3.0:1	#000000	#06151C	Fail
h3 Meet the technology …	1.13:1	3.0:1	#000000	#06151C	Fail
title Waymo - Self-Driving…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Rides	7.37:1	4.5:1	#000000	#999999	Pass
p Rides	1.00:1	4.5:1	#000000	#000000	Fail
p The world’s first …	1.00:1	4.5:1	#000000	#000000	Fail
a Our service	1.00:1	4.5:1	#000000	#000000	Fail
a Where we operate	3.66:1	4.5:1	#000000	#666666	Fail
a How it works	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Technology	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Waymo Driver	21.00:1	4.5: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+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 The World’s Most  Experienced Driver
H2 Meet Waymo
H3 Features
H4 20M+ rides served
H4 An experience second to none
H4 Available24/7
H2 Where Waymo is driving
H3 Serving Riders In
H3 Up Next
H3 Serving Riders In
H3 Up Next
H2 Why they ride with Waymo
H2 Waymo Driver
H3 Meet the technology behind it all
H2 Why we’re here
H2 Our commitment to safety
H2 Our mission: Be the world’s most trusted driver
H2 Footnotes

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#P0-0-search-input	search	Search Waymo	for/id
#P0-0-search-input	search	Search Waymo	for/id
#language-picker	select	Select language	for/id

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 28 passed

PASS

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Rides Rides Our service Where we operate How it works Technology Waymo Drive… `w-safe-triangle > w-header > nav._nav_1iyry_118 > div#P0-0-main-nav`

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
Take a Waymo ride today `figure._lottie_16rnb_3 > svg > g > g`

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
Eva, San Francisco `div._tabpanels_1rli4_103 > div#P0-0-tabpanel-0 > blockquote._blockquote_1rli4_157 > cite._cite_1rli4_183`

These are opportunities to improve the legibility of your content.

○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 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

●Document has a `<title>` element

●`<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.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●No form fields have multiple labels

○`[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

○`<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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.

○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.