Skip to content
https://thebeautychef.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
29
GRADE
F
FIX
10
REVIEW
3
PASS
0
INFO
0
Checks
13
3 REVIEW 10 FIX
F
Heading Hierarchy
Action
136 headings, 5 skip(s)
FIX
136 headings, 5 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
13 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H2 SHOP OUR BESTSELLERS
  • H1 What's Trending
  • H1 Collagen duplicate H1
  • H1 Body Balance duplicate H1
  • H1 Digestion & Gut Health duplicate H1
  • H1 Hair, Skin & Nails duplicate H1
  • H1 Menopause support duplicate H1
  • H2 GLOWING SKIN. IT'S A GUT THING.
  • H4 THE POWDER THAT STARTED IT ALL skipped
  • H2 16 Years of Glow
  • H2 16 Years of Glow
  • H3 Not sure where to start? Find your perfect match & save 20%
  • H4 “I am passionate about empowering people to think differently about beauty by shedding light on the importance of nutrition and gut health for beauty and wellbeing.”
  • H2 CARLA OATES
  • H4 “I am passionate about empowering people to think differently about beauty by shedding light on the importance of nutrition and gut health for beauty and wellbeing.” skipped
  • H2 CARLA OATES
  • H4 “I am passionate about empowering people to think differently about beauty by shedding light on the importance of nutrition and gut health for beauty and wellbeing.” skipped
  • H2 CARLA OATES
  • H4 “I am passionate about empowering people to think differently about beauty by shedding light on the importance of nutrition and gut health for beauty and wellbeing.” skipped
  • H2 CARLA OATES
  • H2 Tried & Tested
  • H3 "Have felt amazing since taking Glow® everyday for 30 days. The results speak for themselves: better sleep, improved skin texture and overall complexion, and improvement in digestive issues."
  • H3 "GLOW F.A.C.E oil improved my dryness and redness on my face. It absorbed really well into my skin… and a little goes a long way."
  • H2 Innovating ingestible beauty and wellness through gut health
  • H2 OUR TEAM OF EXPERTS
  • H2 OUR TEAM OF EXPERTS
  • H2 On The Digest
  • H3 Chocolate Protein Brownies
  • H3 Carla's energising smoothie
  • H3 Raw Chocolate Protein Balls
  • H3 Energising electrolyte slushie
  • H3 Muddled strawberry mocktail
  • H3 Hey Beauty Chef, do I need Body Electric™️?
  • H3 Behind-the-formula of Body Electric™️ with Carla
  • H3 Choc-caramel pecan smoothie
  • H3 Dreamy chocolate pudding
  • H3 Carla’s favourite festive recipes
  • H3 Rainbow Chard, Tomato and Goat’s Cheese Tart
  • H3 Roasted Carrot, Radicchio & Toasted Walnut Salad with Orange & Umeboshi Dressing
  • H3 Chocolate Protein Brownies
  • H3 Carla's energising smoothie
  • H3 Raw Chocolate Protein Balls
  • H3 Energising electrolyte slushie
  • H3 Muddled strawberry mocktail
  • H3 Hey Beauty Chef, do I need Body Electric™️?
  • H3 Behind-the-formula of Body Electric™️ with Carla
  • H3 Choc-caramel pecan smoothie
  • H3 Dreamy chocolate pudding
  • H3 Carla’s favourite festive recipes
  • H3 Rainbow Chard, Tomato and Goat’s Cheese Tart
  • H3 Roasted Carrot, Radicchio & Toasted Walnut Salad with Orange & Umeboshi Dressing
  • H3 Chocolate Protein Brownies
  • H3 Carla's energising smoothie
  • H2 Join our community @thebeautychef
  • H2 BODY PROTEIN+ Inner Beauty Support - Vanilla
  • H2 PLUMPERS™ Two Pack
  • H2 PLUMPERS™ Kakadu Plum & Berry
  • H2 PLUMPERS™ Chocolate
  • H2 PLUMPERS™ Orange & Turmeric
  • H2 PLUMPERS™ Flavour Trio
  • H2 PLUMPERS™ Flavour Trio
  • H2 PLUMPERS™ Two Pack
  • H2 PLUMPERS™ Kakadu Plum & Berry
  • H2 PLUMPERS™ Chocolate
  • H2 PLUMPERS™ Orange
  • H2 PLUMP & GLOW DUO
  • H2 PLUMP & GLOW 50+ DUO
  • H2 ULTIMATE PLUMPING PAIR
  • H2 PLUMPERS™ Three Pack
  • H2 PLUMPERS™ Vanilla Bean
  • H2 PLUMPERS™ Strawberry
  • H2 PLUMPERS TRIO
  • H3 Other tagged products
  • H2 PLUMPERS™ Three Pack
  • H2 PLUMPERS TRIO
  • H3 Other tagged products
  • H2 PLUMPERS™ Vanilla Bean
  • H2 GLOW® Inner Beauty Essential
  • H2 COLLAGEN BOOST™
  • H3 Other tagged products
  • H2 GLOW® Inner Beauty Essential
  • H2 GLOW® Inner Beauty Essential
  • H2 HYDRATION BOOST™
  • H2 COLLAGEN BOOST™
  • H2 ANTIOXIDANT BOOST™
  • H2 RECHARGE Inner Beauty Boost
  • H3 Other tagged products
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 GLOW AGELESS™ Two Pack
  • H2 AGELESS & GLOWING SET 50+
  • H3 Other tagged products
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 AGELESS & GLOWING SET 50+
  • H3 Other tagged products
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 GLOW AGELESS™ Two Pack
  • H2 AGELESS & GLOWING SET 50+
  • H3 Other tagged products
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 GLOW AGELESS™ Two Pack
  • H2 AGELESS & GLOWING SET 50+
  • H3 Other tagged products
  • H2 GLOW AGELESS™ Inner Beauty Essential
  • H2 GLOW AGELESS™ Two Pack
  • H2 AGELESS & GLOWING SET 50+
  • H3 Other tagged products
  • H2 GLOW F.A.C.E™ Intensive Rejuvenating Oil
  • H2 GLOW F.A.C.E™ Intensive Rejuvenating Oil
  • H2 FATIGUE FIGHTERS KIT
  • H2 GLOW F.A.C.E™ Intensive Rejuvenating Oil
  • H2 SUPER GLOW KIT
  • H3 Other tagged products
  • H2 OUR DIFFERENCE
  • H3 BORN IN BONDI
  • H3 ORGANIC & NATURAL
  • H3 BIO-FERMENTED
  • H3 BACKED BY SCIENCE
  • H2 Be the first to know
  • H4 Support skipped
  • H4 Explore
  • H4 Legal
  • H3 Your Bag (0)

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
19 of 232 images have issues
FIX
19 of 232 images have issues
Critical::
19 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
8 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
112 decorative image(s) correctly marked
Info::
101 image(s) with good alt text
232 images 101 good alt text 112 decorative 19 missing
IssueCount
missing19 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

F
Form Accessibility
Action
7 of 13 controls have issues
FIX
7 of 13 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <input type="submit">; <input type="submit" name="checkout">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="customer[first_name]" id="FirstName_footer">; <input type="text" name="customer[last_name]" id="LastName_footer">; <input type="email" name="customer[email]" id="Email_footer">; <input type="password" name="customer[password]" id="CreatePassword_footer">
Info::
6 control(s) properly labeled
13 controls
6 labeled
4 placeholder only
3 unlabeled
ControlTypeLabelMethod
pref_1checkboxnone
pref_2checkboxnone
pref_4checkboxnone
#Search-In-Modal-1searchSearchfor/id
#first_name_01JRA6C9P7AV82SBT82VY6B2RFtextFIRST NAMEaria-label
#email_01JRA6C9PDWGZJJYH2V2YRFY75emailEmailfor/id
#FirstName_footertext(First name)placeholder only
#LastName_footertext(Last name)placeholder only
#Email_footeremail(Email)placeholder only
#CreatePassword_footerpassword(Password)placeholder only
selectselect(none)none
inputsubmit(none)none
checkoutsubmit(none)none

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

<select>; <input type="submit">; <input type="submit" name="checkout">

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="text" name="customer[first_name]" id="FirstName_footer">; <input type="text" name="customer[last_name]" id="LastName_footer">; <input type="email" name="customer[email]" id="Email_footer">; <input type="password" name="customer[password]" id="CreatePassword_footer">

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

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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.
Got: #c4cdd5
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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 MAIN 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 18 pass AA only
h2 16 Years of Glow
1.42:1
#AB1F24
on
#6F6F6F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 16 Years of Glow
1.42:1
#AB1F24
on
#6F6F6F
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 What's Trending4.18:13.0:1
#000000
#6F6F6F
Pass
h1 Collagen4.18:13.0:1
#000000
#6F6F6F
Pass
h1 Body Balance4.18:13.0:1
#000000
#6F6F6F
Pass
h1 Digestion & Gut Heal…4.18:13.0:1
#000000
#6F6F6F
Pass
h1 Hair, Skin & Nails4.18:13.0:1
#000000
#6F6F6F
Pass
h1 Menopause support4.18:13.0:1
#000000
#6F6F6F
Pass
h2 GLOWING SKIN. IT'S A…4.18:13.0:1
#000000
#6F6F6F
Pass
h2 16 Years of Glow1.42:13.0:1
#AB1F24
#6F6F6F
Fail
h2 16 Years of Glow1.42:13.0:1
#AB1F24
#6F6F6F
Fail
h2 CARLA OATES3.07:13.0:1
#212529
#6F6F6F
Pass
h2 CARLA OATES3.07:13.0:1
#212529
#6F6F6F
Pass
h2 CARLA OATES3.07:13.0:1
#212529
#6F6F6F
Pass
h2 CARLA OATES3.07:13.0:1
#212529
#6F6F6F
Pass
h2 Innovating ingestibl…4.18:13.0:1
#000000
#6F6F6F
Pass
h2 OUR TEAM OF EXPERTS4.18:13.0:1
#000000
#6F6F6F
Pass
h2 OUR TEAM OF EXPERTS4.18:13.0:1
#000000
#6F6F6F
Pass
h2 BODY PROTEIN+ Inner …4.18:13.0:1
#000000
#6F6F6F
Pass
h2 PLUMPERS™ Two Pack4.18:13.0:1
#000000
#6F6F6F
Pass
h2 PLUMPERS™ Kakadu P…4.18:13.0:1
#000000
#6F6F6F
Pass
h2 PLUMPERS™ Chocolat…4.18:13.0:1
#000000
#6F6F6F
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 80/100 — 7 failing, 29 passed
REVIEW
80

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
predictive-search.search-modal__form > form.search > div.predictive-search__input-field > button.predictive-search__close predictive-search.search-modal__form > form.search > div.predictive-search__input-field > button.predictive-search__close

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.mobile-menu-nav > div.mobile-menu--icon > a.logo-mini-link > img.logo-mini div.mobile-menu-nav > div.mobile-menu--icon > a.logo-mini-link > img.logo-mini
div#slick-slide130 > div.row > div.col-lg-6 > img.lazy div#slick-slide130 > div.row > div.col-lg-6 > img.lazy
div.col-md-8 > div.testi-container > div.testi-image-wrapper > img.testi-image div.col-md-8 > div.testi-container > div.testi-image-wrapper > img.testi-image
section.c-science-section > div.c-science-section__featured-image-container > picture > img.c-science-section__featured-image section.c-science-section > div.c-science-section__featured-image-container > picture > img.c-science-section__featured-image
div.slick-list > div.slick-track > div.col-6 > img.lazy div.slick-list > div.slick-track > div.col-6 > img.lazy
div.col-image > a > div.feature-row__image-wrapper > img div.col-image > a > div.feature-row__image-wrapper > img
div.col-image > a > div.feature-row__image-wrapper > img div.col-image > a > div.feature-row__image-wrapper > img
div.col-image > a > div.feature-row__image-wrapper > img div.col-image > a > div.feature-row__image-wrapper > img
div.col-image > a > div.feature-row__image-wrapper > img div.col-image > a > div.feature-row__image-wrapper > img

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AU US ul > li.mobile-store-option > div.mobile-flag > select.store-option

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.col-md-4 > div.header-icons > div.mobile-cart > a.search-trigger div.col-md-4 > div.header-icons > div.mobile-cart > a.search-trigger
div.col-md-4 > div.header-icons > div.mobile-cart > a.cart-toggle div.col-md-4 > div.header-icons > div.mobile-cart > a.cart-toggle
section > div.mobile-menu-nav > div.mobile-menu--icon > a.logo-mini-link section > div.mobile-menu-nav > div.mobile-menu--icon > a.logo-mini-link
div.mobile-menu--inner > div.menu-image-box > div.mega-menu-image > a div.mobile-menu--inner > div.menu-image-box > div.mega-menu-image > a
div.image-content > div.container > div.row > a.position-absolute div.image-content > div.container > div.row > a.position-absolute
div.slick-list > div.slick-track > div.slider_content > a div.slick-list > div.slick-track > div.slider_content > a
div.image-content > div.container > div.row > a.position-absolute div.image-content > div.container > div.row > a.position-absolute
div.slick-track > div.col-md-4 > div.blog-box-inner > a.article-image-link div.slick-track > div.col-md-4 > div.blog-box-inner > a.article-image-link
div.col-item > div.ingredients-column-inner > div.col-image > a div.col-item > div.ingredients-column-inner > div.col-image > a
div.col-item > div.ingredients-column-inner > div.col-image > a div.col-item > div.ingredients-column-inner > div.col-image > a
div.col-item > div.ingredients-column-inner > div.col-image > a div.col-item > div.ingredients-column-inner > div.col-image > a
div.col-item > div.ingredients-column-inner > div.col-image > a div.col-item > div.ingredients-column-inner > div.col-image > a
div.pr-0 > div.klaviyo_field_group > div.social-media > a div.pr-0 > div.klaviyo_field_group > div.social-media > a
div.pr-0 > div.klaviyo_field_group > div.social-media > a div.pr-0 > div.klaviyo_field_group > div.social-media > a
div.pr-0 > div.klaviyo_field_group > div.social-media > a.yt-icon-link div.pr-0 > div.klaviyo_field_group > div.social-media > a.yt-icon-link
div.pr-0 > div.klaviyo_field_group > div.social-media > a div.pr-0 > div.klaviyo_field_group > div.social-media > a
div.pr-0 > div.klaviyo_field_group > div.social-media > a.yt-icon-link div.pr-0 > div.klaviyo_field_group > div.social-media > a.yt-icon-link

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.

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
SUPPORT div.footer-col > div.row > div.footer-nav > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
MORE OPTIONS div#pandectes-banner > div.pd-cookie-banner-window > div.cc-compliance > button.cc-btn
ACCEPT div#pandectes-banner > div.pd-cookie-banner-window > div.cc-compliance > button.cc-btn
○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
●Input buttons have discernible text.
●Form elements have associated labels
●`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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●ARIA IDs are unique
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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>`.
○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.

Send Feedback