Skip to content
https://kabellaboutique.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile-Readable Font Sizes
Action
84% of visible text renders at >= 12 CSS px (8 below threshold)
REVIEW
84% of visible text renders at >= 12 CSS px (8 below threshold)
Warning::
8 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <small> 11.0px ("© 2026,"); <a> 11.0px ("Kabella Boutique"); <a> 11.0px ("Powered by Shopify"); <a> 11.0px ("Privacy policy"); <a> 11.0px ("Refund policy").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Kabella Boutique ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
title Kabella Boutique
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Envío gratuito en órdenes de $130+
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Te recomendamos leer nuestra política d…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Compra ahora, paga después. 4 pagos sin…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a New Arrivals
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
summary Catalog
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
button Catalog
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
a All Products
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
a Pre-Orden
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
a Dresses
1.51:1
#000000
on
#2D2B38
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Item added to your c…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Colecciones20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Deja tu email y entÃ…20.29:13.0:1
#000000
#FBFBFB
Pass
title Kabella Boutique1.00:14.5:1
#000000
#000000
Fail
a Skip to content1.00:14.5:1
#000000
#000000
Fail
span Envío gratuito en Ã…1.00:14.5:1
#000000
#000000
Fail
span Te recomendamos leer…1.00:14.5:1
#000000
#000000
Fail
span Compra ahora, paga d…1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a New Arrivals1.51:14.5:1
#000000
#2D2B38
Fail
summary Catalog1.51:14.5:1
#000000
#2D2B38
Fail
button Catalog1.51:14.5:1
#000000
#2D2B38
Fail
a All Products1.51:14.5:1
#000000
#2D2B38
Fail
a Pre-Orden1.51:14.5:1
#000000
#2D2B38
Fail
a Dresses1.51:14.5:1
#000000
#2D2B38
Fail
a Rompers8.18:14.5:1
#000000
#A2A1A6
Pass
a Sets18.43:14.5:1
#000000
#F0F0F0
Pass
a Tops18.43:14.5:1
#000000
#F0F0F0
Pass
a Jewelry18.43:14.5:1
#000000
#F0F0F0
Pass
a Exercise Clothing18.43:14.5:1
#000000
#F0F0F0
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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 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 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
33 headings
PASS
33 headings
Info::
Single H1 present
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Item added to your cart
  • H2 (empty)
  • H3 Aurelia Satin Halter Mini Dress
  • H3 Aurelia Satin Halter Mini Dress
  • H3 Colette Polka Dot Peplum Set
  • H3 Colette Polka Dot Peplum Set
  • H3 Soleil Halter Maxi Skirt Set
  • H3 Soleil Halter Maxi Skirt Set
  • H3 Yes al Amor Blazer
  • H3 Yes al Amor Blazer
  • H3 Valencia Sport Mini Skirt Set (Ordenes seran enviadas en Noviembre 3 Approx.)
  • H3 Valencia Sport Mini Skirt Set (Ordenes seran enviadas en Noviembre 3 Approx.)
  • H3 Celeste Polka Dot Halter Top (Se estara enviando la camisa en Noviembre 3 Approx.)
  • H3 Celeste Polka Dot Halter Top (Se estara enviando la camisa en Noviembre 3 Approx.)
  • H3 Alessia Striped Halter Maxi Set (Ordenes seran enviadas en Noviembre 7 approx.)
  • H3 Alessia Striped Halter Maxi Set (Ordenes seran enviadas en Noviembre 7 approx.)
  • H3 Vivienne Halter Drop Waist Mini Dress
  • H3 Vivienne Halter Drop Waist Mini Dress
  • H2 Colecciones
  • H3 New Arrivals
  • H3 New Arrivals
  • H3 Tops
  • H3 Tops
  • H3 Dresses
  • H3 Dresses
  • H3 Romper
  • H3 Romper
  • H3 Sets
  • H3 Sets
  • H3 All Products
  • H3 All Products
  • H2 Deja tu email y entérate de nuestras ofertas y lanzamientos.

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

A+
Heading Text Quality
All 33 heading(s) have substantive, well-formed text
PASS
All 33 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
1 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
22 images 21 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#Search-In-ModalsearchSearchfor/id
#NewsletterForm--sections--20173174341876__footeremailEmailfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://kabellaboutique.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cust…")
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.
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+
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 93/100 — 2 failing, 29 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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
10% off entire order Suscríbete y recibe tu código exclusivo para tu primera o… div#app-embed > div._container_3eyaa_70 > div#form-container-ref > section.withImage

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.

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
Deja tu email y entérate de nuestras ofertas y lanzamientos. div.footer__content-top > div.footer-block--newsletter > div.footer-block__newsletter > h2.footer-block__heading
form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--20173174341876__footer form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--20173174341876__footer
Email form#ContactFooter > div.newsletter-form__field-wrapper > div.field > label.field__label
First and Last Name div._gridItem_29s4r_176 > form._formFieldset_48bzm_110 > div._formFieldContainer_1mxsl_5 > label#label-first_name
Email div._gridItem_29s4r_176 > form._formFieldset_48bzm_110 > div._formFieldContainer_1mxsl_5 > label#label-email

These are opportunities to improve the legibility of your content.

○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
●`[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 have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○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
○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>`.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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