Accessibility

F

Heading Hierarchy

Action

44 headings, 6 skip(s)

FIX

44 headings, 6 skip(s)

Multiple H1 headings (7 found)

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Memberships
H1 This spring, get 10% off
H2 Choose a membership
H1 Save 10% duplicate H1
H1 Save 10% duplicate H1
H2 Get a complete picture of your health
H3 Quantify how your body is feeling
H3 Extend your prime for years to come
H3 Optimize your sleep
H3 Measure the impact of every step and rep
H3 Stay connected to your heart health
H3 Get daily Blood Pressure Insights
H3 Understand your unique cycle
H2 Backed by PHDs, worn by MVPs
H4 Cristiano Ronaldo skipped
H4 Aryna Sabalenka
H1 "WHOOP has been a huge motivator to a healthier lifestyle." duplicate H1
H4 Ashlynn P. skipped
H4 Stef Williams
H1 "WHOOP has helped me greatly improve my physical health and wellbeing" duplicate H1
H4 Samatha R. skipped
H4 Nelly Korda
H4 Sha'Carri Richardson
H4 Virgil van Dijk
H4 Diplo
H1 "WHOOP continues to transform my approach to health and wellness daily." duplicate H1
H4 Weilynn T. skipped
H4 Patrick Mahomes
H1 "Healthspan has helped me adjust my behaviors to help increase longevity." duplicate H1
H4 Ellie G. skipped
H2 Built to be worn 24/7
H3 Zero distractions
H3 Always on sensors
H3 14+ day battery life
H3 Completely customizable
H2 One device, endless ways to wear it
H3 Live in luxe
H5 No other wearable lets you try before you buy skipped
H2 Support
H2 Company
H2 Legal
H2 Partner
H2 Join WHOOP
H2 The Locker

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

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

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

D

Link & Button Quality

Action

15 issue(s) across 81 links and 36 buttons

FIX

15 issue(s) across 81 links and 36 buttons

5 link(s) with generic text

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

Got: /fr/en/one ("LEARN MORE"); /fr/en/peak/ ("LEARN MORE"); /fr/en/life/ ("LEARN MORE"); /fr/en/feature-availability/ ("here"); /fr/en/feature-availability/ ("here")

6 image-only link(s) without alt text

10 button(s) with no accessible text

70 link(s) with descriptive text

81 links

0 empty

5 generic text

0 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
/fr/en/one/	Professional-grade fitness ins…	img no alt	Add alt attribute to the image
/fr/en/peak/	Advanced health, fitness, & lo…	img no alt	Add alt attribute to the image
/fr/en/life/	The most powerful WHOOP ever, …	img no alt	Add alt attribute to the image
/fr/en/one/	Professional-grade fitness ins…	img no alt	Add alt attribute to the image
/fr/en/peak/	Advanced health, fitness, & lo…	img no alt	Add alt attribute to the image
/fr/en/life/	The most powerful WHOOP ever, …	img no alt	Add alt attribute to the image
/fr/en/one	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: One
/fr/en/peak/	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Peak
/fr/en/life/	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Life
/fr/en/feature-availability/	here	generic text	Replace with descriptive text
Before: here Suggested: Feature Availability
/fr/en/feature-availability/	here	generic text	Replace with descriptive text
Before: here Suggested: Feature Availability
<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

96 links and buttons have descriptive text

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

/fr/en/one ("LEARN MORE"); /fr/en/peak/ ("LEARN MORE"); /fr/en/life/ ("LEARN MORE"); /fr/en/feature-availability/ ("here"); /fr/en/feature-availability/ ("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

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

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

F

Favicon & Branding

Action

2 icon(s) detected

FIX

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

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

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

B

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 20 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 This spring, get 10%…	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 Save 10%	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 Save 10%	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 WHOOP has been a hug…	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 WHOOP has helped me …	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 WHOOP continues to t…	3.79:1	3.0:1	#000000	#3468B4	Pass
h1 Healthspan has helpe…	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Choose a membership	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Get a complete pictu…	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Backed by PHDs, worn…	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Built to be worn 24/…	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 One device, endless …	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Support	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Company	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Legal	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Partner	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 Join WHOOP	3.79:1	3.0:1	#000000	#3468B4	Pass
h2 The Locker	3.79:1	3.0:1	#000000	#3468B4	Pass
h3 Quantify how your bo…	3.79:1	3.0:1	#000000	#3468B4	Pass
h3 Extend your prime fo…	3.79:1	3.0:1	#000000	#3468B4	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.

B

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 28 passed

REVIEW

87

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Quantify how your body is feeling with WHOOP `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
Person wearing a WHOOP device resting at the edge of a pool; a WHOOP Age orb di… `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
Optimize sleep with WHOOP `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
WHOOP Core Product app ui. `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
Stay connected with your heart health. `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
Blood pressure monitor app ui with WHOOP `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`
menstrual cycle insights app ui. `div.image-carousel-features_keen-slider__1uyme > div.keen-slider__slide > section.module-wrapper_module-wrapper__ONmYZ > a.image-carousel-card-features_image-carousel-card-features__KTn1H`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.default-layout_layout__header__DiRAG > header.module-wrapper_module-wrapper__ONmYZ > div.mega-menu_header__content__DTwOP > button.icon-button_icon-button__cnqXV `div.default-layout_layout__header__DiRAG > header.module-wrapper_module-wrapper__ONmYZ > div.mega-menu_header__content__DTwOP > button.icon-button_icon-button__cnqXV`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn `section.module-wrapper_module-wrapper__ONmYZ > div.card-item__contents > div.image-over-btn > button.plus-btn`
div.footer_footer-bottom-bar__legal__lR_n9 > div.footer_footer-bottom-bar__legal-items-container__Bn5iw > div.footer_footer-bottom-bar__country-selector__PUqxQ > button.flex `div.footer_footer-bottom-bar__legal__lR_n9 > div.footer_footer-bottom-bar__legal-items-container__Bn5iw > div.footer_footer-bottom-bar__country-selector__PUqxQ > button.flex`

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.

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
SPORTFLEX `div.fifty-fifty-learn_fifty-fifty-learn__column-text__xw36F > div.pill-toggle_pill-toggle__toggle-buttons__6m68_ > button.primary-button_primary-cta__DzHjl > span.primary-button_primary-cta__label__b6BiV`
CLOUDKNIT `div.fifty-fifty-learn_fifty-fifty-learn__column-text__xw36F > div.pill-toggle_pill-toggle__toggle-buttons__6m68_ > button.primary-button_primary-cta__DzHjl > span.primary-button_primary-cta__label__b6BiV`
SUPERKNIT `div.fifty-fifty-learn_fifty-fifty-learn__column-text__xw36F > div.pill-toggle_pill-toggle__toggle-buttons__6m68_ > button.primary-button_primary-cta__DzHjl > span.primary-button_primary-cta__label__b6BiV`
COREKNIT `div.fifty-fifty-learn_fifty-fifty-learn__column-text__xw36F > div.pill-toggle_pill-toggle__toggle-buttons__6m68_ > button.primary-button_primary-cta__DzHjl > span.primary-button_primary-cta__label__b6BiV`
WHOOP BODY `div.fifty-fifty-learn_fifty-fifty-learn__column-text__xw36F > div.pill-toggle_pill-toggle__toggle-buttons__6m68_ > button.primary-button_primary-cta__DzHjl > span.primary-button_primary-cta__label__b6BiV`

These are opportunities to improve the legibility of your content.

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
Cristiano Ronaldo `div.athletes-video-card_card-content__IhPtF > div.athletes-video-card_card-bottom-content-row___I6LY > div.card-bottom-content > h4.athletes-video-card_card-heading__QBDN2`
Ashlynn P. `div.athletes-small-card_card-content__offkE > div.athletes-small-card_card-text-wrapper__Ev0nW > div.card-text-wrapper-inner > h4.athletes-small-card_card-heading___Uuun`
Samatha R. `div.athletes-small-card_card-content__offkE > div.athletes-small-card_card-text-wrapper__Ev0nW > div.card-text-wrapper-inner > h4.athletes-small-card_card-heading___Uuun`
Weilynn T. `div.athletes-small-card_card-content__offkE > div.athletes-small-card_card-text-wrapper__Ev0nW > div.card-text-wrapper-inner > h4.athletes-small-card_card-heading___Uuun`
Ellie G. `div.athletes-small-card_card-content__offkE > div.athletes-small-card_card-text-wrapper__Ev0nW > div.card-text-wrapper-inner > h4.athletes-small-card_card-heading___Uuun`
No other wearable lets you try before you buy `div.module-content_module-content__JtNA_ > div.module-two-column-image-and-text_two-column-image-text__wrapper__XKT4s > div.module-two-column-image-and-text_two-column-image-text__text__4y_MN > h5.heading_heading__Gh8z9`

These are opportunities to improve keyboard navigation in your application.

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

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

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

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

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

2 image(s) with alt text over 125 characters

24 decorative image(s) correctly marked

9 image(s) with good alt text

35 images 9 good alt text 24 decorative

Issue	Count
too long	2 image(s)

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(Enter your email)	placeholder only

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

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