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

Accessibility

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
17 headings, 1 skip(s)
REVIEW
17 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The most advanced connected health station
  • H1 The first toilet embedded urine lab duplicate H1
  • H1 Restore your nights. Supercharge your days. duplicate H1
  • H3 Scales skipped
  • H3 Watches
  • H3 BP Monitors
  • H3 Sleep Analyzer
  • H3 U-Scan
  • H3 BeamO
  • H3 Heart, weight, progress—your health data in one score.
  • H3 Our built-in ECG powers your next Cardio Check-Up.
  • H3 Crucial patterns in your health, revealed.
  • H3 Stay energized. Spot early signals.
  • H3 We create technology that people love, to make better health part of daily life.
  • H3 We empower healthcare teams to transform patients’ lives, through our health monitoring solutions.
  • H2 Start your health journey
  • H2 Start your health journey

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 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::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="email">; <input type="email" name="email" id="email">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#emailemail(Enter your email)placeholder only
#emailemail(Enter your email)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" id="email">; <input type="email" name="email" id="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

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 Connected Health: Smart Scales, Watches and Health Monitors | Withings Europe Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
18 icon(s) detected
REVIEW
18 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 Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
p Discover our shops
2.74:1
#000000
on
#4F5458
needs 4.5:1 (normal text)
16px · top of page (header area)
p All our products
2.74:1
#000000
on
#4F5458
needs 4.5:1 (normal text)
16px · top of page (header area)
p Smart devices, empowering your health jo…
2.74:1
#000000
on
#4F5458
needs 4.5:1 (normal text)
16px · above the fold
p All our scale models
2.74:1
#000000
on
#4F5458
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Start your health jo…16.31:13.0:1
#000000
#E6E2DF
Pass
h2 Start your health jo…16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Scales16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Watches16.31:13.0:1
#000000
#E6E2DF
Pass
h3 BP Monitors16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Sleep Analyzer16.31:13.0:1
#000000
#E6E2DF
Pass
h3 U-Scan16.31:13.0:1
#000000
#E6E2DF
Pass
h3 BeamO16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Heart, weight, progr…16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Our built-in ECG pow…16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Crucial patterns in …16.31:13.0:1
#000000
#E6E2DF
Pass
h3 Stay energized. Spot…16.31:13.0:1
#000000
#E6E2DF
Pass
h3 We create technology…16.31:13.0:1
#000000
#E6E2DF
Pass
h3 We empower healthcar…16.31:13.0:1
#000000
#E6E2DF
Pass
title Withings | Withings …21.00:14.5:1
#000000
#FFFFFF
Pass
a Store21.00:14.5:1
#000000
#FFFFFF
Pass
p Discover our shops2.74:14.5:1
#000000
#4F5458
Fail
p All our products2.74:14.5:1
#000000
#4F5458
Fail
p Smart devices, empow…2.74:14.5:1
#000000
#4F5458
Fail
p All our scale models2.74:14.5:1
#000000
#4F5458
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 81/100 — 6 failing, 28 passed
REVIEW
81

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.

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
Explore Withings devices today. div.section_container > div.flex > p.txt_subtitle > span.opacity_50
Best seller aside.grid_container > div.grid_container > p > span.badge
Buy now div.swiper-slide > div > div.flex > a.margin_top_4
Learn more div.swiper-slide > div > div.flex > a.margin_top_4
Choose your language or country div.lang-mob > div.section_container > div.padding_top_8 > p.label_region
Legal notice div.corporate-container > ul.corporate > li > a.txt_caption
Privacy div.corporate-container > ul.corporate > li > a.txt_caption
Data Security div.corporate-container > ul.corporate > li > a.txt_caption
Conditions div.corporate-container > ul.corporate > li > a.txt_caption
Cookies policy div.corporate-container > ul.corporate > li > a.txt_caption
Set Cookies div.corporate-container > ul.corporate > li > a.txt_caption
© 2026 Withings All rights reserved. div.sub-footer > div.subfooter-bottom > div.corporate-container > p.txt_book

These are opportunities to improve the legibility of your content.

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
header.new_nav > nav > div.nav-leftBox > a.withings_logo header.new_nav > nav > div.nav-leftBox > a.withings_logo
div.padding_left_5 > article.email-kmi > form.input > input#email div.padding_left_5 > article.email-kmi > form.input > input#email
Register div.padding_left_5 > article.email-kmi > form.input > button.btn_primary

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
Scales div.grid_container > div.card > div.content > h3.txt_subtitle_large

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.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
div.texts > div.txt_caption > div.flex > img div.texts > div.txt_caption > div.flex > img
body.currency-eur > img body.currency-eur > img

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
header.new_nav > nav > div.nav-leftBox > a.withings_logo header.new_nav > nav > div.nav-leftBox > a.withings_logo
div.nav_links > div.categories > div.category_others > a.account-sidebar-link div.nav_links > div.categories > div.category_others > a.account-sidebar-link
div.categories > div.category_others > aside#headerMenuCart > a.headerMenuLink div.categories > div.category_others > aside#headerMenuCart > a.headerMenuLink
div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a
div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a
div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a div#swiper-wrapper-b1920c3bc5e861e10 > div.swiper-slide > aside.grid_container > a
div.padding_top_8 > div.sub-footer > div.subfooter-top > a.logo div.padding_top_8 > div.sub-footer > div.subfooter-top > a.logo
div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social
div.subfooter-bottom > ul.social > li.margin_right_4 > a.icon-social div.subfooter-bottom > ul.social > li.margin_right_4 > a.icon-social
div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social
div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social
div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social div.subfooter-bottom > ul.social > li.margin_right_6 > a.icon-social
div.subfooter-bottom > ul.social > li > a.icon-social div.subfooter-bottom > ul.social > li > a.icon-social

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.

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 section.swiper-heroes > div.swiper_hero > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 section.swiper-heroes > div.swiper_hero > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 section.swiper-heroes > div.swiper_hero > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

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
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.
`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
Elements use only permitted ARIA attributes
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
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
`<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
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.
Tables have different content in the summary attribute and `<caption>`.
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
Landmark Structure
24 landmarks
PASS
24 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV MAIN ASIDE 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

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

Send Feedback