Skip to content
https://morphe.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
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: transparent
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.
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 – Morphe US ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
23 landmarks
PASS
23 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 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 menu" 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
Heading Hierarchy
39 headings
PASS
39 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H3 Popular Searches
  • H3 Popular Products
  • H3 Ready, Set, Pro 16-Piece Face & Eye Brush Set
  • H3 Dripglass Glazed High Shine Lip Gloss
  • H3 Micro Manager Gripping Brow Gel
  • H1 Your Bag
  • H1 WELCOME TO CHEEK ISLAND duplicate H1
  • H2 NEW ARRIVALS
  • H3 Cheek Thrills Bronze & Tone Duos
  • H3 Cheek Thrills Multi-Finish Face Trio
  • H3 M240 Dual-Ended Cream & Powder Sculpt Brush
  • H3 M200 Dual-Ended Cream & Powder Blush Brush
  • H3 Lifeproof 16-Hour Continuous Setting Mist
  • H3 Dazzling Metallics Eyeshadow Trio
  • H3 Cheek Thrills Multi-Finish Face Trio - Yacht Day
  • H3 Dreamlight Gelée Highlighter Stick
  • H3 Dripglass Dazzled High Shimmer Lip Gloss
  • H3 Mixed Signals Dual-Ended Cream & Liquid Shadow Stick
  • H3 Nano Brow Pencil
  • H3 Micro Manager Gripping Brow Gel
  • H3 Buttery Blends M106 Flat-Topped Foundation Brush
  • H3 Buttery Blends M104 Domed Foundation Brush
  • H3 Buttery Blends M108 Slanted Foundation Brush
  • H3 Buttery Blends Tool Duo
  • H2 Limited-Edition Merch
  • H2 lifeproof
  • H2 Dare to Dazzle
  • H3 Dazzling Metallics Eyeshadow Trio
  • H3 Dreamlight Gelée Highlighter Stick
  • H3 Dripglass Dazzled High Shimmer Lip Gloss
  • H2 CRUELTY-FREE
  • H2 Satisfaction
  • H2 REWARDS
  • H2 Join Waitlist
  • H2 Sign up to our newsletter
  • H2 About Us Accordion Arrow
  • H2 My Morphe Accordion Arrow
  • H2 Help Accordion Arrow
  • H2 Follow Us Accordion Arrow

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

A+
Alt Text Quality
All 111 images OK
PASS
All 111 images OK
Info::
32 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
111 images 79 good alt text 32 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextSearcharia-label
region-search-inputtextSearch for a countryaria-label
#newsletter-emailemailEmailaria-label
#newsletter-emailemailEmailaria-label
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
h1 WELCOME TO CHEEK ISL…6.58:13.0:1
#000000
#909090
Pass
h2 NEW ARRIVALS6.58:13.0:1
#000000
#909090
Pass
h2 Limited-Edition Merc…6.58:13.0:1
#000000
#909090
Pass
h2 lifeproof6.58:13.0:1
#000000
#909090
Pass
h2 Dare to Dazzle6.58:13.0:1
#000000
#909090
Pass
h2 CRUELTY-FREE6.58:13.0:1
#000000
#909090
Pass
h2 Satisfaction6.58:13.0:1
#000000
#909090
Pass
h2 REWARDS6.58:13.0:1
#000000
#909090
Pass
h2 Join Waitlist6.58:13.0:1
#000000
#909090
Pass
h2 Sign up to our newsl…6.58:13.0:1
#000000
#909090
Pass
h3 Popular Searches6.58:13.0:1
#000000
#909090
Pass
h3 Popular Products6.58:13.0:1
#000000
#909090
Pass
h3 Ready, Set, Pro 16-P…6.58:13.0:1
#000000
#909090
Pass
h3 Dripglass Glazed Hig…6.58:13.0:1
#000000
#909090
Pass
h3 Micro Manager Grippi…6.58:13.0:1
#000000
#909090
Pass
h3 Cheek Thrills Bronze…6.58:13.0:1
#000000
#909090
Pass
h3 Cheek Thrills Multi-…6.58:13.0:1
#000000
#909090
Pass
h3 M240 Dual-Ended Crea…6.58:13.0:1
#000000
#909090
Pass
h3 M200 Dual-Ended Crea…6.58:13.0:1
#000000
#909090
Pass
h3 Lifeproof 16-Hour Co…6.58:13.0:1
#000000
#909090
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.

A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 31 passed
PASS
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CRUELTY-FREE div.tvg_usp_section_DuUVOa_USPSection__grid > div.swiper-wrapper > div.tvg_usp_section_DuUVOa_USPSection__item > div.tvg_usp_section_DuUVOa_USPSection__icon
Satisfaction div.tvg_usp_section_DuUVOa_USPSection__grid > div.swiper-wrapper > div.tvg_usp_section_DuUVOa_USPSection__item > div.tvg_usp_section_DuUVOa_USPSection__icon
REWARDS div.tvg_usp_section_DuUVOa_USPSection__grid > div.swiper-wrapper > div.tvg_usp_section_DuUVOa_USPSection__item > div.tvg_usp_section_DuUVOa_USPSection__icon

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.

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
Cheek Thrills Bronze & Tone Duos div.tvg_featured_products_UbFoKG_FeaturedProducts__slide > div.tvg_product_card_h_wIOG_ProductCard > a.tvg_product_card_h_wIOG_ProductCard__content > h3.tvg_product_card_h_wIOG_ProductCard__title

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
New Brushes & Tools Brushes & Tools Shop All Brushes & Tools Face Brushes Eye B… header#shopify-section-sections--16356153163848__header > aside.tvg_menu_mobile_ZzCowq_MenuMobile > nav.tvg_menu_mobile_ZzCowq_Navigation > ul.tvg_menu_mobile_ZzCowq_Navigation__list
Face Brushes Eye Brushes Brush Sets Sponges & Applicators li > div.tvg_menu_mobile_ZzCowq_Submenu > div > ul.tvg_menu_mobile_ZzCowq_Dropdown__menu
BUTTERY BLENDS SHOP NOW READY, SET, PRO SHOP NOW SPONGES & APPLICATORS SHO… ul.tvg_menu_mobile_ZzCowq_Navigation__list > li > div.tvg_menu_mobile_ZzCowq_Submenu > ul.tvg_menu_mobile_ZzCowq_Thumbs
Complexion Setting Powders & Mists Cheek li > div.tvg_menu_mobile_ZzCowq_Submenu > div > ul.tvg_menu_mobile_ZzCowq_Dropdown__menu
CHEEK THRILLS SHOP NOW BAKE & SET SHOP NOW LIFEPROOF SHOP NOW ul.tvg_menu_mobile_ZzCowq_Navigation__list > li > div.tvg_menu_mobile_ZzCowq_Submenu > ul.tvg_menu_mobile_ZzCowq_Thumbs
Eyeshadow & Palettes Eyeliner Brows Mascara Primers li > div.tvg_menu_mobile_ZzCowq_Submenu > div > ul.tvg_menu_mobile_ZzCowq_Dropdown__menu
NANO BROW SHOP NOW CHROMAPLUS SHOP NOW SOLO ARTIST SHOP NOW ul.tvg_menu_mobile_ZzCowq_Navigation__list > li > div.tvg_menu_mobile_ZzCowq_Submenu > ul.tvg_menu_mobile_ZzCowq_Thumbs
Shop All Lip Lipstick Lip Gloss & Oils Lip Liner li > div.tvg_menu_mobile_ZzCowq_Submenu > div > ul.tvg_menu_mobile_ZzCowq_Dropdown__menu
DRIPGLASS SHOP NOW LIP FILTER SHOP NOW LIP PENCIL SHOP NOW ul.tvg_menu_mobile_ZzCowq_Navigation__list > li > div.tvg_menu_mobile_ZzCowq_Submenu > ul.tvg_menu_mobile_ZzCowq_Thumbs
CHEEK THRILLS SHOP NOW LIFEPROOF SHOP NOW BUTTERY BLENDS SHOP NOW body.template-index > header#shopify-section-sections--16356153163848__header > aside.tvg_menu_mobile_ZzCowq_MenuMobile > ul.tvg_menu_mobile_ZzCowq_Thumbs
Morphe Rewards Education Hub Account USD$ header#shopify-section-sections--16356153163848__header > aside.tvg_menu_mobile_ZzCowq_MenuMobile > div.tvg_menu_mobile_ZzCowq_MenuMobile__footer > ul.tvg_menu_mobile_ZzCowq_MenuMobile__footerList

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
○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