Skip to content
https://beautybakerie.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
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
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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: #ffffff
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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 1 pass AA only
title Beauty Bakerie Cosmetics Brand | Clean V…
4.37:1
#000000
on
#727272
needs 4.5:1 (normal text)
16px · top of page (header area)
p We use cookies and other technologies to…
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy.
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Manage preferences
4.11:1
#000000
on
#6D6E6E
needs 4.5:1 (normal text)
16px · above the fold
button Accept
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · above the fold
button Decline
4.17:1
#000000
on
#6E6F70
needs 4.5:1 (normal text)
16px · above the fold
a Skip to content
4.11:1
#000000
on
#6D6E6E
needs 4.5:1 (normal text)
16px · above the fold
span Open navigation menu
1.79:1
#000000
on
#373838
needs 4.5:1 (normal text)
16px · above the fold
span Open search
1.74:1
#000000
on
#363636
needs 4.5:1 (normal text)
16px · above the fold
summary Shop
1.74:1
#000000
on
#363636
needs 4.5:1 (normal text)
16px · above the fold
span Lip
1.73:1
#000000
on
#353636
needs 4.5:1 (normal text)
16px · above the fold
span Lip Whips
1.74:1
#000000
on
#363637
needs 4.5:1 (normal text)
16px · above the fold
span Lip Whip Remover
1.74:1
#000000
on
#363636
needs 4.5:1 (normal text)
16px · mid-page
span Lip Bundles
1.74:1
#000000
on
#363636
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 We value your privac…4.37:13.0:1
#000000
#727272
Pass
h2 the recipe for a bak…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 the recipe for a bak…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AS SEEN IN21.00:13.0:1
#000000
#FFFFFF
Pass
h2 good things come to …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 our community is ser…21.00:13.0:1
#000000
#FFFFFF
Pass
title Beauty Bakerie Cosme…4.37:14.5:1
#000000
#727272
Fail
p We use cookies and o…4.06:14.5:1
#000000
#6D6D6D
Fail
a Privacy Policy.4.06:14.5:1
#000000
#6D6D6D
Fail
span Manage preferences4.11:14.5:1
#000000
#6D6E6E
Fail
button Accept4.06:14.5:1
#000000
#6D6D6D
Fail
button Decline4.17:14.5:1
#000000
#6E6F70
Fail
a Skip to content4.11:14.5:1
#000000
#6D6E6E
Fail
span Open navigation menu1.79:14.5:1
#000000
#373838
Fail
span Open search1.74:14.5:1
#000000
#363636
Fail
summary Shop1.74:14.5:1
#000000
#363636
Fail
span Lip1.73:14.5:1
#000000
#353636
Fail
span Lip Whips1.74:14.5:1
#000000
#363637
Fail
span Lip Whip Remover1.74:14.5:1
#000000
#363636
Fail
span Lip Bundles1.74:14.5:1
#000000
#363636
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 85/100 — 4 failing, 24 passed
REVIEW
85

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.

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
I'm ready div.section-stack > div.section-header > div.prose > a.button
E-mail form#newsletter-form-newsletter > div.fieldset-with-submit > div.form-control > label.floating-label
By completing this form you are signing up to receive our emails and can unsubs… div.newsletter-box > div.newsletter-content > form#newsletter-form-newsletter > p.text-xs
E-mail div.v-stack > form#footer-newsletter > div.form-control > label.floating-label
Founded in 2011, learn more here. div.footer__block-list > div.footer__block > div.prose > p
Customer Care div.footer__block > ul.v-stack > li > a.inline-block
Shipping Policy div.footer__block > ul.v-stack > li > a.inline-block
Opt Out div.footer__block > ul.v-stack > li > a.inline-block
Privacy Policy div.footer__block > ul.v-stack > li > a.inline-block
Careers div.footer__block > ul.v-stack > li > a.inline-block
High Contrast Mode div.footer__wrapper > div.footer__aside > div.footer__aside-bottom > label.footer__contrastInput
Accept div.privacy-bar__inner > div.v-stack > div.h-stack > button.button
15% Off div.needsclick > div#rich-text-016JB91TTR00000000003P14QS > h1 > span.ql-font-poppins
Your Next Purchase div.needsclick > div#rich-text-016JB91TTR00000000003P14QS > p > span.ql-font-poppins

These are opportunities to improve the legibility of your content.

Names and labels

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
section#shopify-section-template--19819837030590__slideshow > x-slideshow.slideshow > slideshow-carousel#slideshow-template--19819837030590__slideshow > a#block-image_DELpyf section#shopify-section-template--19819837030590__slideshow > x-slideshow.slideshow > slideshow-carousel#slideshow-template--19819837030590__slideshow > a#block-image_DELpyf
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item

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.

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to item 1 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 2 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 3 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 4 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area

These items highlight common accessibility best practices.

○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
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer
A
Heading Hierarchy
11 headings
PASS
11 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 We value your privacy
  • H1 Beauty Bakerie Cosmetics Brand
  • H2 what the girls love
  • H2 the recipe for a baked beat
  • H2 the recipe for a baked beat
  • H2 AS SEEN IN
  • H2 craving sweets now? pull up on us!
  • H2 follow us on social
  • H3 our community is serving
  • H2 good things come to those who bake
  • H1 15% Off duplicate H1

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 58 images OK
PASS
All 58 images OK
Info::
47 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
58 images 11 good alt text 47 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearcharia-label
#input-newsletter-482858725emailE-mailfor/id
#input-footer-486220522emailE-mailfor/id
#contrastSwitchcheckboxnone
#email_016JB91TTR00000000003P14QVemailEmailfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback