Skip to content
https://www.sachinandbabi.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
9
REVIEW
3
PASS
12
INFO
0
Checks
24
12 PASS 3 REVIEW 9 FIX
F
Alt Text Quality
Action
6 of 771 images have issues
FIX
6 of 771 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
644 decorative image(s) correctly marked
Info::
120 image(s) with good alt text
771 images 120 good alt text 644 decorative 6 missing
IssueCount
missing6 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Tap Target Adequacy
Action
11 tap target(s) too small or too close together
FIX
11 tap target(s) too small or too close together
Warning::
11 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
D
Mobile-Readable Font Sizes
Action
50% of visible text renders at >= 12 CSS px (3 below threshold)
FIX
50% of visible text renders at >= 12 CSS px (3 below threshold)
Warning::
3 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: <span> 10.0px ("Previous"); <p> 10.0px ("FREE SHIPPING ON ALL ORDERS OVER $500"); <span> 10.0px ("Next").
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 Verifying your connection... ✓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
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::
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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
title Dresses and Gowns for Weddings & Special…
1.50:1
#000000
on
#1F2C42
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.50:1
#000000
on
#1F2C42
needs 4.5:1 (normal text)
16px · top of page (header area)
span Previous
1.50:1
#000000
on
#1F2C42
needs 4.5:1 (normal text)
16px · top of page (header area)
p FREE SHIPPING ON ALL ORDERS OVER $500
1.50:1
#000000
on
#1F2C42
needs 4.5:1 (normal text)
16px · top of page (header area)
p FREE RETURNS ON ALL ELIGIBLE ORDERS (EX…
2.29:1
#000000
on
#5F4226
needs 4.5:1 (normal text)
16px · above the fold
span Next
3.08:1
#000000
on
#755439
needs 4.5:1 (normal text)
16px · above the fold
span Sachin & Babi
2.78:1
#000000
on
#6C4E33
needs 4.5:1 (normal text)
16px · above the fold
span Open navigation menu
3.03:1
#000000
on
#765238
needs 4.5:1 (normal text)
16px · above the fold
summary NEW ARRIVALS
1.54:1
#000000
on
#432714
needs 4.5:1 (normal text)
16px · above the fold
a SHOP ALL
1.11:1
#000000
on
#131009
needs 4.5:1 (normal text)
16px · above the fold
a EXPLORE
1.08:1
#000000
on
#0E0C0A
needs 4.5:1 (normal text)
16px · above the fold
a Pre-Order
1.07:1
#000000
on
#0F0A05
needs 4.5:1 (normal text)
16px · above the fold
a Gowns
1.99:1
#000000
on
#4F3B2C
needs 4.5:1 (normal text)
16px · above the fold
a Dresses
3.73:1
#000000
on
#7D624E
needs 4.5:1 (normal text)
16px · mid-page
a Separates
1.88:1
#000000
on
#4B3728
needs 4.5:1 (normal text)
16px · mid-page
a Accessories
2.16:1
#000000
on
#593E32
needs 4.5:1 (normal text)
16px · mid-page
span Shop with AI
1.81:1
#000000
on
#4B3423
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 New Arrivals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Blog posts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Designer Dresses for…21.00:13.0:1
#000000
#FFFFFF
Pass
title Dresses and Gowns fo…1.50:14.5:1
#000000
#1F2C42
Fail
a Skip to content1.50:14.5:1
#000000
#1F2C42
Fail
span Previous1.50:14.5:1
#000000
#1F2C42
Fail
p FREE SHIPPING ON ALL…1.50:14.5:1
#000000
#1F2C42
Fail
p FREE RETURNS ON ALL …2.29:14.5:1
#000000
#5F4226
Fail
span Next3.08:14.5:1
#000000
#755439
Fail
span Sachin & Babi2.78:14.5:1
#000000
#6C4E33
Fail
span Open navigation menu3.03:14.5:1
#000000
#765238
Fail
summary NEW ARRIVALS1.54:14.5:1
#000000
#432714
Fail
a SHOP ALL1.11:14.5:1
#000000
#131009
Fail
a EXPLORE1.08:14.5:1
#000000
#0E0C0A
Fail
a Pre-Order1.07:14.5:1
#000000
#0F0A05
Fail
a Gowns1.99:14.5:1
#000000
#4F3B2C
Fail
a Dresses3.73:14.5:1
#000000
#7D624E
Fail
a Separates1.88:14.5:1
#000000
#4B3728
Fail
a Accessories2.16:14.5:1
#000000
#593E32
Fail
span Shop with AI1.81:14.5:1
#000000
#4B3423
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 84/100 — 6 failing, 26 passed
REVIEW
84

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MOTHER OF THE BRIDE DRESSES SHOP NOW KARIGAR SHOP NOW BLACK-TIE SHOP NOW … div.section-spacing > div.container > div.section-stack > div.collection-list

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
WE'RE HERE TO ENSURE YOU HAVE THE BEST EXPERIENCE POSSIBLE. WHETHER YOU HAVE QU… div.color-scheme > div.container > div.prose > h6.h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image
div.collection-list > a.collection-card > div.content-over-media > img.zoom-image div.collection-list > a.collection-card > div.content-over-media > img.zoom-image

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Use div#cookieconsent-desc > span.Xv6jG2pxegQjp5oQ_YmP > span.csm-native-text > a
Privacy Policy div#cookieconsent-desc > span.Xv6jG2pxegQjp5oQ_YmP > span.csm-native-expanded-links > a.kNH36PUaKEeaUwegZcvg

These are opportunities to improve the legibility of your content.

Best practices

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 2 slideshow-carousel#carousel-template--22349487046846__slideshow > div.slideshow__controls-wrapper > carousel-navigation.page-dots > button.tap-area
Go to item 3 slideshow-carousel#carousel-template--22349487046846__slideshow > div.slideshow__controls-wrapper > carousel-navigation.page-dots > button.tap-area
Go to item 4 slideshow-carousel#carousel-template--22349487046846__slideshow > div.slideshow__controls-wrapper > carousel-navigation.page-dots > button.tap-area
Go to item 5 slideshow-carousel#carousel-template--22349487046846__slideshow > div.slideshow__controls-wrapper > carousel-navigation.page-dots > button.tap-area
Go to item 6 slideshow-carousel#carousel-template--22349487046846__slideshow > div.slideshow__controls-wrapper > carousel-navigation.page-dots > button.tap-area
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link
SHOP NOW a.collection-card > div.content-over-media > div.collection-card__content > button.link

These items highlight common accessibility best practices.

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
MOTHER OF THE BRIDE DRESSES SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
KARIGAR SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
BLACK-TIE SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
DAY DRESSING SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
GOWNS UNDER $500 SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
COCKTAIL SHOP NOW div.container > div.section-stack > div.collection-list > a.collection-card
○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
●Buttons have an accessible name
●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
●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 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
●`[lang]` attributes have a valid value
●Skip links are focusable.
●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
○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
○`<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.
○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.
○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
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN ASIDE CONTENTINFO footer
A
Heading Hierarchy
6 headings, 1 skip(s)
PASS
6 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Sachin & Babi
  • H2 New Arrivals
  • H2 Blog posts
  • H2 Designer Dresses for Weddings, Black Tie & Special Occasions
  • H6 We're here to ensure you have the best experience possible. Whether you have questions, need assistance, or want to share feedback, we're ready to help. Your satisfaction is our top priority! skipped
  • H6 CONTACT US

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H6: 191 chars
Got: 1 >120-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
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
qsearchSearcharia-label
#input--sections--22349483016382__footer--contactemailemailE-mailfor/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
7 explicit tabindex attribute(s) checked, no anti-patterns
PASS
7 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 5 iframe(s) have descriptive titles
PASS
All 5 iframe(s) have descriptive titles
Info::
All 5 iframe(s) have title attributes
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::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback