Skip to content
https://cheekbonebeauty.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
F
Heading Hierarchy
Action
62 headings, 3 skip(s)
FIX
62 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
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::
7 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Language
  • H2 Currency
  • H1 (empty)
  • H4 FEATURED skipped
  • H4 LIPS
  • H4 EYES
  • H4 FACE
  • H4 MAKE UP KITS
  • H4 Merch
  • H3 READY IN MINUTES TRIO
  • H1 (empty)
  • H2 Your cart
  • H3 Your cart is empty
  • H2 Illuminating Primer Stick
  • H3 FINALLY BACK IN STOCK
  • H2 SHOP BY
  • H3 Lips
  • H3 Eyes
  • H3 Face
  • H2 Featured Looks
  • H4 Busy Mom Basics Makeup Bundle skipped
  • H4 Cheekbone Essentials Kit
  • H4 All You Need Face Bundle
  • H4 Set & Stay Eye Kit
  • H3 shop the spring 2026 jilly box add-on
  • H4 Perfect Red and Nude in our iconic OG packaging
  • H3 Our Indigenous Roots
  • H3 Sustainable by Nature
  • H3 CHEEKBONE ESSENTIALS KIT
  • H3 Essentials Eye Trio
  • H3 Bold Clean Colour
  • H4 Sustain Lipstick
  • H4 Illuminating Primer Stick
  • H4 Empower Eyeliner
  • H4 Sustain Lipstick
  • H4 Illuminating Primer Stick
  • H2 FIND YOUR MATCH
  • H2 From the blog
  • H3 Lavender Rock: The Eye Shadow Pencil That Makes Colour Feel Easy
  • H3 CHEEKBONE x IPSY GIVEAWAY
  • H2 HOW OUR WARRIORS WEAR IT
  • H3 Media from our community
  • H4 Favorites
  • H4 Support
  • H4 Let's Keep In Touch
  • H2 Language
  • H2 Currency
  • H4 Availability skipped
  • H3 (empty)
  • H3 Alert
  • H4 (empty)
  • H3 (empty)
  • H3 No rePete Products
  • H3 (empty)
  • H2 Reorder Details
  • H3 Product Details
  • H3 Shipping Address
  • H2 There was an error
  • H2 Reorder unsuccessful!
  • H2 Success!
  • H2 Congrats! Your Reorder was successful!
  • H3 (empty)

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

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
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="search">; <textarea>
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#footer-subscribe-emailemailYour emailfor/id
#searchtext(What are you looking for?)placeholder only
textareatextarea(Ask anything)placeholder only

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

<input type="text" name="q" id="search">; <textarea>

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
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 26 passed
REVIEW
88

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
body.template-index > div > button.react-modal-sheet-backdrop body.template-index > div > button.react-modal-sheet-backdrop

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.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item
div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9 div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9

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

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
div > div.react-modal-sheet-container > div.react-modal-sheet-content > iframe.Giftbox-Popup-Iframe-3082023 div > div.react-modal-sheet-container > div.react-modal-sheet-content > iframe.Giftbox-Popup-Iframe-3082023

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
BUSY MOM BASICS MAKEUP BUNDLE div.product-item__inner > div.product-item__meta > div.product-item__text > h4.ff-body
LET'S KEEP IN TOUCH div.footer__inner > div.footer__groups > div.footer__group > h4.footer__header

These are opportunities to improve keyboard navigation in your application.

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
  0 div.header__inner > div.header__row > div.header__row-segment > a.header__icon-touch
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
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
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
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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
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 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
`<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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 ASIDE 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+
Alt Text Quality
All 96 images OK
PASS
All 96 images OK
Info::
41 decorative image(s) correctly marked
Info::
55 image(s) with good alt text
96 images 55 good alt text 41 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Language10.30:13.0:1
#000000
#C8B29B
Pass
h2 Currency11.39:13.0:1
#000000
#CEBCA9
Pass
h2 Your cart19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Illuminating Primer …19.60:13.0:1
#000000
#FFF5F2
Pass
h2 SHOP BY19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Featured Looks19.60:13.0:1
#000000
#FFF5F2
Pass
h2 FIND YOUR MATCH19.60:13.0:1
#000000
#FFF5F2
Pass
h2 From the blog19.60:13.0:1
#000000
#FFF5F2
Pass
h2 HOW OUR WARRIORS WEA…19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Language19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Currency19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Reorder Details19.60:13.0:1
#000000
#FFF5F2
Pass
h2 There was an error19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Reorder unsuccessful…19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Success!19.60:13.0:1
#000000
#FFF5F2
Pass
h2 Congrats! Your Reord…19.60:13.0:1
#000000
#FFF5F2
Pass
h3 READY IN MINUTES TRI…19.60:13.0:1
#000000
#FFF5F2
Pass
h3 Your cart is empty19.60:13.0:1
#000000
#FFF5F2
Pass
h3 FINALLY BACK IN STOC…19.60:13.0:1
#000000
#FFF5F2
Pass
h3 Lips19.60:13.0:1
#000000
#FFF5F2
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.

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

Send Feedback