Skip to content
https://cleobella.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Verifying your connection... ✓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.
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
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.
Got: <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="email" id="NewsletterForm--bd-footer">
C
Tabindex Anti-Patterns
Action
0 positive, 9 -1-on-focusable
REVIEW
0 positive, 9 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Iframe Accessibility
3/5 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/5 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://cleobella.com/web-pixels@212ce547w31cd49a8p9bec2579mf0e5c5ca/app/web-pi…")
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://cleobella.com/web-pixels@212ce547w31cd49a8p9bec2579mf0e5c5ca/custom/web…")
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://cleobella.com/web-pixels@212ce547w31cd49a8p9bec2579mf0e5c5ca/custom/web…")
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.
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
h2 Your cart is empty
1.81:1
#000000
on
#4D3322
needs 3.0:1 (large text)
24px · top of page (header area) · over background image/gradient
h2 Your cart
1.03:1
#000000
on
#03050F
needs 3.0:1 (large text)
24px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Art of Dressing19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Your cart is empty1.81:13.0:1
#000000
#4D3322
Fail
h2 Your cart1.03:13.0:1
#000000
#03050F
Fail
h2 Complete the Look19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Subtotal19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Featured Collections19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Lilah Midi Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Evan Top19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Lyra Ankle Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Emilia Mini Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Lilah Midi Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Emilia Mini Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Lyra Ankle Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Charisma Mini Dress19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Evan Top19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Jolie Top19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Theodora Top19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Theodora Top19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Azure Midi Skirt19.21:13.0:1
#000000
#F6F5EE
Pass
h2 Adelaide Mini Skirt19.21:13.0:1
#000000
#F6F5EE
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+
Landmark Structure
7 landmarks
PASS
7 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 CONTENTINFO footer
A+
Heading Hierarchy
92 headings
PASS
92 headings
Info::
Single H1 present
  • H2 Your cart is empty
  • H2 Your cart
  • H2 Complete the Look
  • H3 Saint Malo Weekender | Saint Malo
  • H4 Other Colors
  • H3 Bali Zodiac Bracelet
  • H3 Astrid Tote Bag | Black & Moccasin
  • H3 Gigi Cropped Sweater Vest | Cream
  • H4 Other Colors
  • H2 Subtotal
  • H1 The Art of Dressing
  • H2 Featured Collections
  • H2 Lilah Midi Dress
  • H3 Soir
  • H2 Evan Top
  • H3 Soir
  • H2 Lyra Ankle Dress
  • H3 Soir
  • H2 Emilia Mini Dress
  • H3 Soir
  • H2 Lilah Midi Dress
  • H3 Soir
  • H2 Emilia Mini Dress
  • H3 Soir
  • H2 Lyra Ankle Dress
  • H3 Soir
  • H2 Charisma Mini Dress
  • H3 Black Floral Anise
  • H2 Evan Top
  • H3 Soir
  • H2 Jolie Top
  • H3 Eclat
  • H2 Theodora Top
  • H3 Dusty Blue
  • H2 Theodora Top
  • H3 Ivory
  • H2 Azure Midi Skirt
  • H3 Surf the Web
  • H2 Adelaide Mini Skirt
  • H3 Skywriting
  • H2 Aylin Midi Skirt
  • H3 Ivory
  • H2 Wes Short
  • H3 Impala
  • H2 Hendrix Bag
  • H3 Black
  • H2 Mini Hendrix Bag
  • H3 Black
  • H2 Alia Tote
  • H3 Black Multi
  • H2 Casablanca Weekender
  • H3 Dark Tuscany
  • H2 Seraphine Triangle Top
  • H3 Paprika
  • H2 Esme Tie Side Bottom
  • H3 Paprika
  • H2 Fiorella One Piece
  • H3 Bleura
  • H2 Paloma Triangle Top
  • H3 Vecchio Stripe
  • H2 Sheenie Blouse
  • H3 Fiore Rosso
  • H2 Arden Mini Skirt
  • H3 Fiore Rosso
  • H2 Roxanne Ankle Dress
  • H3 Fiore Rosso
  • H2 Parvana Mini Dress
  • H3 White
  • H2 Loma Sweater
  • H3 Ivory
  • H2 Loma Sweater
  • H3 Black
  • H2 Lisa Sweater
  • H3 Black
  • H2 Maude Midi Dress
  • H3 Black
  • H2 Le Carre Trench Coat
  • H3 Black
  • H2 Charisma Mini Dress
  • H3 Black Floral Anise
  • H2 Ravenna Ankle Dress
  • H3 Black
  • H2 Colton Jacket
  • H3 Black
  • H2 Fawn Ankle Dress
  • H3 Black Floral Anise
  • H2 At Cleobella, sustainability and ethical practices are the core of our brand.
  • H3 Collections
  • H3 Discover
  • H3 Resources
  • H3 Social
  • H3 Newsletter
A+
Heading Text Quality
All 92 heading(s) have substantive, well-formed text
PASS
All 92 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
8 of 106 images have issues
PASS
8 of 106 images have issues
Warning::
8 image(s) with generic alt text
Info::
8 decorative image(s) correctly marked
Info::
90 image(s) with good alt text
106 images 90 good alt text 8 decorative 8 generic
IssueCount
generic8 image(s)
A+
Form Accessibility
All 19 controls labeled
PASS
All 19 controls labeled
Info::
19 control(s) properly labeled
19 controls
19 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#--5279775522981-1-0radioAriesfor/id
#--5279775522981-1-1radioTaurusfor/id
#--5279775522981-1-2radioGemini Variant sold out or unavailablefor/id
#--5279775522981-1-3radioCancerfor/id
#--5279775522981-1-4radioLeo Variant sold out or unavailablefor/id
#--5279775522981-1-5radioVirgofor/id
#--5279775522981-1-6radioLibrafor/id
#--5279775522981-1-7radioScorpiofor/id
#--5279775522981-1-8radioSagittariusfor/id
#--5279775522981-1-9radioCapricorn Variant sold out or unavailablefor/id
#--5279775522981-1-10radioAquariusfor/id
#--5279775522981-1-11radioPiscesfor/id
#--8018127061221-1-0radioXS Variant sold out or unavailablefor/id
#--8018127061221-1-1radioS Variant sold out or unavailablefor/id
#--8018127061221-1-2radioMfor/id
#--8018127061221-1-3radioLfor/id
#--8018127061221-1-4radioXLfor/id
#Search-In-ModalsearchSearchfor/id
#NewsletterForm--bd-footeremailEmailfor/id
A+
Form Input Types
19 form control(s) checked, no type mismatches
PASS
19 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
19 form control(s) checked, no input-semantic issues
PASS
19 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
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+
Mobile-Readable Font Sizes
All 6 visible text node(s) render at >= 12 CSS pixels
PASS
All 6 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 passed
PASS
94

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

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.user-nav-area > ul.user-nav > li > a.with-icon div.user-nav-area > ul.user-nav > li > a.with-icon
div.user-nav-area > ul.user-nav > li > a#cart-icon-bubble div.user-nav-area > ul.user-nav > li > a#cart-icon-bubble

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.

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
Facebook Instagram Pinterest Save 15% div.relative > div.wide-width > div.text-block > ul.footer-list

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]`s are contained by their required parent element
●`[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.
●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
●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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○Links are distinguishable without relying on color.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback