Skip to content
https://peakhealthandfitness.co.uk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 FIX
D
Form Accessibility
Action
5 of 6 controls have issues
FIX
5 of 6 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="address[country]" id="AddressCountry_Shipping">; <select name="address[province]" id="AddressProvince_shipping">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="contact[email]">; <textarea name="note" id="cartNote">; <input type="text" id="ShippingAddressZip">
Info::
1 control(s) properly labeled
6 controls
1 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#Search-In-ModalsearchSearch our storefor/id
contact[email]email(Enter Email:)placeholder only
#cartNotetextarea(Order special instructions)placeholder only
#ShippingAddressZiptext(Postal/ZIP code)placeholder only
#AddressProvince_shippingselect(none)none
#AddressCountry_Shippingselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="address[country]" id="AddressCountry_Shipping">; <select name="address[province]" id="AddressProvince_shipping">

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="contact[email]">; <textarea name="note" id="cartNote">; <input type="text" id="ShippingAddressZip">

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

D
Iframe Accessibility
Action
6/6 iframe(s) missing title; 0 placeholder(s)
FIX
6/6 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://peakhealthandfitness.co.uk/web-pixels@7107b92aw4540d021pdd526a22md4e69a…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
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
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.
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("0 items").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Peak Health & Fitness -
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Ice Baths, Hot Tubs & Saunas UK
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 As featured in
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tested in the Real World. Not Chosen by …
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What I Use. What I Recommend.
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Simple. Flexible. Done.
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recovery Insights
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Men's Health
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ladbible
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 UniLad
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Mirror
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Daily Express
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wales Online
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Your cart is empty
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Subtotal
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
title Peak Health & Fitness | Ice Baths, Hot T…
1.05:1
#000000
on
#040A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.05:1
#000000
on
#030A0C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Facebook
1.05:1
#000000
on
#02090F
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Peak Health & Fitnes…1.26:13.0:1
#000000
#1E1E1E
Fail
h1 Ice Baths, Hot Tubs …1.26:13.0:1
#000000
#1E1E1E
Fail
h2 As featured in1.26:13.0:1
#000000
#1E1E1E
Fail
h2 Tested in the Real W…1.26:13.0:1
#000000
#1E1E1E
Fail
h2 What I Use. What I R…1.26:13.0:1
#000000
#1E1E1E
Fail
h2 Invest in Your Healt…16.67:13.0:1
#FFFFFF
#1E1E1E
Pass
h2 Simple. Flexible. Do…1.26:13.0:1
#000000
#1E1E1E
Fail
h2 Recovery Insights1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Men's Health1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Ladbible1.26:13.0:1
#000000
#1E1E1E
Fail
h3 UniLad1.26:13.0:1
#000000
#1E1E1E
Fail
h3 The Mirror1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Daily Express1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Wales Online1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Upgrade Your Recover…16.67:13.0:1
#FFFFFF
#1E1E1E
Pass
h3 Your cart is empty1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Subtotal1.26:13.0:1
#000000
#1E1E1E
Fail
title Peak Health & Fitnes…1.05:14.5:1
#000000
#040A0A
Fail
a Skip to content1.05:14.5:1
#000000
#030A0C
Fail
span Facebook1.05:14.5:1
#000000
#02090F
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 89/100 — 4 failing, 27 passed
REVIEW
89

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.

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.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn
div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn
div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn div.product-grid-item__content > div.product-grid-item__action-visibal-cartx > quick-view-modal > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn
div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn div.product-grid-item__action-visibal-cartxx > product-form > form#[object HTMLInputElement] > button.product-grid-item__actions__btn

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
div.blog__post > article.article-card > div.article-card__info > a.article-content div.blog__post > article.article-card > div.article-card__info > a.article-content
article.article-card > div.article-card__info > h3.post-title > a.article-content article.article-card > div.article-card__info > h3.post-title > a.article-content
div.blog__post > article.article-card > div.article-card__info > a.article-content div.blog__post > article.article-card > div.article-card__info > a.article-content
article.article-card > div.article-card__info > h3.post-title > a.article-content article.article-card > div.article-card__info > h3.post-title > a.article-content
div.blog__post > article.article-card > div.article-card__info > a.article-content div.blog__post > article.article-card > div.article-card__info > a.article-content
article.article-card > div.article-card__info > h3.post-title > a.article-content article.article-card > div.article-card__info > h3.post-title > a.article-content

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
The story behind Peak has been featured in leading UK publications press-features-adfdgd1frtnritktxnaigenblock451d75bvxjrt8.ai-press-features-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__container-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__header-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__subtitle-adfdgd1frtnritktxnaigenblock451d75bvxjrt8
£4,499.00 dl > div.price__sale > dd.price__compare > s.price-item

These are opportunities to improve the legibility of your content.

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
Men's Health div.ai-press-features__carousel-wrapper-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__carousel-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__item-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > a.ai-press-features__link-adfdgd1frtnritktxnaigenblock451d75bvxjrt8
Ladbible div.ai-press-features__carousel-wrapper-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__carousel-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__item-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > a.ai-press-features__link-adfdgd1frtnritktxnaigenblock451d75bvxjrt8
UniLad div.ai-press-features__carousel-wrapper-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__carousel-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > div.ai-press-features__item-adfdgd1frtnritktxnaigenblock451d75bvxjrt8 > a.ai-press-features__link-adfdgd1frtnritktxnaigenblock451d75bvxjrt8
○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
●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.
●`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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○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
○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
○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
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN 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

A
Heading Hierarchy
46 headings, 1 skip(s)
PASS
46 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Best Sellers
  • H4 Hot Tubs & Swim Spas
  • H1 Peak Health & Fitness - Ice Baths, Hot Tubs & Saunas UK
  • H2 As featured in
  • H3 Men's Health
  • H3 Ladbible
  • H3 UniLad
  • H3 The Mirror
  • H3 Daily Express
  • H3 Wales Online
  • H2 Tested in the Real World. Not Chosen by Marketing.
  • H2 What I Use. What I Recommend.
  • H3 H2O 2500 Series 13A Plug & Play Hot Tub
  • H3 WaveSpa Ontario Round Drop Stitch Hot Tub | Herringbone
  • H3 MITO LIGHT Expert 4.0
  • H3 Infraredi LED Light Therapy Mask
  • H3 MITO LIGHT Starter 4.0
  • H3 Fonteyn Barrel Sauna Rustic Red Cedar – 4ft to 7ft
  • H3 Wave Antarctic | Drop Stitch Ice Bath | Black
  • H3 H2O 6000 Series 6-Seater (Twin-Pump) 32A Plug & Play Hot Tub
  • H3 Infraredi Body Wrap Red Light Therapy
  • H3 Fonteyn Infrared Cabin Bella
  • H3 H2O 2500 Series 13A Plug & Play Hot Tub
  • H3 WaveSpa Ontario Round Drop Stitch Hot Tub | Herringbone
  • H3 MITO LIGHT Expert 4.0
  • H3 Infraredi LED Light Therapy Mask
  • H3 MITO LIGHT Starter 4.0
  • H3 Fonteyn Barrel Sauna Rustic Red Cedar – 4ft to 7ft
  • H3 Wave Antarctic | Drop Stitch Ice Bath | Black
  • H3 H2O 6000 Series 6-Seater (Twin-Pump) 32A Plug & Play Hot Tub
  • H2 What You are Looking to Improve
  • H2 Invest in Your Health - Without the Upfront Cost
  • H2 Simple. Flexible. Done.
  • H2 Recovery Insights
  • H3 My Cancer Recovery Protocol: How Red Light Therapy, Infrared Saunas, Ice Baths and Exercise Support My Treatment
  • H3 Infrared Sauna vs Traditional Sauna: Which Is Actually Better?
  • H3 Hot Tub Prices UK (2026): Average Jacuzzi, Swim Spa & Cold Plunge Tub Costs
  • H3 Upgrade Your Recovery Routine
  • H3 Top Collections
  • H3 Customer Support
  • H3 Legal
  • H3 Contact Information
  • H3 Your cart is empty
  • H3 Subtotal
  • H6 Add note for seller skipped
  • H6 Estimate shipping rates

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

A+
Heading Text Quality
All 46 heading(s) have substantive, well-formed text
PASS
All 46 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 71 images OK
PASS
All 71 images OK
Info::
2 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
71 images 69 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
17 explicit tabindex attribute(s) checked, no anti-patterns
PASS
17 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback