Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Link & Button Quality

2 issue(s) across 409 links and 36 buttons

REVIEW

2 issue(s) across 409 links and 36 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /magazine/google_fitbit ("here"); https://support.google.com/store/answer/2411741?sjid=8998094188717530883-NC ("here")

17 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://home.nest.com/en/US; https://support.google.com/fitbit/answer/14236710; https://support.google.com/store/answer/12436460; https://support.google.com/store/answer/12436460; https://g.co/pixelwatch/specs; https://g.co/pixelwatch/fitbitpremium-tos; https://store.google.com/intl/en-US_us/about/device-trade-in.html; https://twitter.com/madebygoogle; https://instagram.com/madebygoogle; https://facebook.com/madebygoogle (+7 more)

390 link(s) with descriptive text

409 links

0 empty

2 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://home.nest.com/en/US	My Nest Home	new tab	Add '(opens in new tab)' to text
/magazine/google_fitbit	here	generic text	Replace with descriptive text
Before: here Suggested: Google Fitbit
https://support.google.com/fitbit/answer…	Learn more about daily readine…	new tab	Add '(opens in new tab)' to text
https://support.google.com/store/answer/…	Learn more about free shipping…	new tab	Add '(opens in new tab)' to text
https://support.google.com/store/answer/…	Learn more about free shipping…	new tab	Add '(opens in new tab)' to text
https://g.co/pixelwatch/specs	g.co/pixelwatch/specs	new tab	Add '(opens in new tab)' to text
https://g.co/pixelwatch/fitbitpremium-to…	g.co/pixelwatch/fitbitpremium-…	new tab	Add '(opens in new tab)' to text
https://store.google.com/intl/en-US_us/a…	store.google.com/intl/en-US_us…	new tab	Add '(opens in new tab)' to text
https://support.google.com/store/answer/…	here	generic text	Replace with descriptive text
Before: here Suggested: 2411741?Sjid=8998094188717530883 Nc
https://twitter.com/madebygoogle	Twitter	new tab	Add '(opens in new tab)' to text
https://instagram.com/madebygoogle	Instagram	new tab	Add '(opens in new tab)' to text
https://facebook.com/madebygoogle	Facebook	new tab	Add '(opens in new tab)' to text
https://youtube.com/madebygoogle	YouTube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@googlepixel	Tiktok	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	link to Privacy	new tab	Add '(opens in new tab)' to text
https://safety.google/intl/en_US/nest/	link to Google Nest Commitment…	new tab	Add '(opens in new tab)' to text
https://store.google.com/intl/en-US_us/a…	link to Sales Terms	new tab	Add '(opens in new tab)' to text
https://www.google.com/intl/en-US_us/pol…	link to Terms of Service	new tab	Add '(opens in new tab)' to text
https://careers.google.com/hardware/?&sr…	link to Careers	new tab	Add '(opens in new tab)' to text

426 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/magazine/google_fitbit ("here"); https://support.google.com/store/answer/2411741?sjid=8998094188717530883-NC ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://home.nest.com/en/US; https://support.google.com/fitbit/answer/14236710; https://support.google.com/store/answer/12436460; https://support.google.com/store/answer/12436460; https://g.co/pixelwatch/specs; https://g.co/pixelwatch/fitbitpremium-tos; https://store.google.com/intl/en-US_us/about/device-trade-in.html; https://twitter.com/madebygoogle; https://instagram.com/madebygoogle; https://facebook.com/madebygoogle (+7 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

255 landmarks

PASS

255 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Hierarchy

102 headings

PASS

102 headings

Single H1 present

H3 Phones
H3 Explore more
H3 Discover
H3 Fi Wireless
H3 Watches & Trackers
H3 Explore more
H3 Discover
H3 Earbuds
H3 Explore more
H3 Discover
H3 Smart Home
H3 Cameras
H3 Explore more
H3 Discover
H3 Doorbells
H3 Explore more
H3 Discover
H3 Speakers
H3 Explore more
H3 Discover
H3 Thermostats
H3 Explore more
H3 Discover
H3 Streaming
H3 Explore more
H3 Discover
H3 Displays
H3 Explore more
H3 Discover
H3 Door Lock
H3 Explore more
H3 Discover
H3 WiFi
H3 Explore more
H3 Discover
H3 Smoke & CO Alarm
H3 Discover
H3 Explore more
H3 Discover
H3 Tablets
H3 Explore more
H3 Discover
H3 Accessories
H3 Offers
H3 Discover
H3 Support
H3 Phones
H3 Explore more
H3 Discover
H3 Fi Wireless
H3 Watches & Trackers
H3 Explore more
H3 Discover
H3 Earbuds
H3 Explore more
H3 Discover
H3 Smart Home
H3 Explore more
H3 Discover
H3 Tablets
H3 Explore more
H3 Discover
H3 Accessories
H3 Offers
H3 Discover
H3 Support
H1 Fitbit Official Site for Activity Trackers & Smartwatches
H2 The Google Store is the home for all things Fitbit.
H2 Google Pixel and Fitbit keep you moving.
H2 Google Pixel Watch 41
H2 Google Pixel Watch 41
H2 Fitbit Charge 62
H2 Fitbit Charge 62
H2 Fitbit Ace LTE3
H2 Fitbit Ace LTE3
H2 Fitbit Sense 2
H2 Fitbit Sense 2
H2 Fitbit Versa 4
H2 Fitbit Versa 4
H2 Which is right for you?
H2 Which is right for you?
H2 Technology to help transform your health.
H3 Fitbit app
H3 Google apps
H3 Daily readiness score
H2 The Pixel Watch 4 is your most advanced fitness watch yet.1
H2 The Pixel Watch 4 is your most advanced fitness watch yet.1
H2 The full force of Fitbit at your fingertips.
H2 The full force of Fitbit at your fingertips.
H3 Restore the feeling of newness for your devices with the latest features.
H2 Style and power your watch or tracker.
H2 Wait, there’s even more to love.
H3 Power your population health programs with Fitbit Enterprise.
H2 There’s no better place to buy a Pixel Watch.
H2 Trade in your old watch and save.Δ
H2 Trade in your old watch and save.Δ
H2 Pixel Care+ for added protection.
H2 Pixel Care+ for added protection.
H2 Finance your watch or tracker.
H2 Finance your watch or tracker.
H2 Free shipping and returns.†
H2 Free shipping and returns.†

Alt Text Quality

All 203 images OK

PASS

All 203 images OK

9 image(s) with alt text over 125 characters

13 decorative image(s) correctly marked

181 image(s) with good alt text

203 images 181 good alt text 13 decorative

Issue	Count
too long	9 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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)

Element	Ratio	Required	FG	BG	Result
h1 Fitbit Official Site…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Phones	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Explore more	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Discover	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Fi Wireless	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Watches & Trackers	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Explore more	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Discover	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Earbuds	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Explore more	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Discover	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Smart Home	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Cameras	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Explore more	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Discover	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Doorbells	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Explore more	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Discover	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Speakers	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Explore more	19.95:1	3.0:1	#000000	#F9F9F9	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 100/100 — 1 failing, 29 passed

PASS

100

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.

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
Shop now `section.r4IXed > div.IhIbQd > div.HCQo4d > a.pdGIZc`
Explore Pixel Drops `div > div > div.ryTcJb > a.IvQv9b`
Browse all accessories `div.qny8z > div > div.ryTcJb > a.IvQv9b`

○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

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

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