Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

9 PASS 7 REVIEW 8 FIX

Form Accessibility

Action

7 of 11 controls have issues

FIX

7 of 11 controls have issues

5 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="number" name="quantity">; <input type="submit" name="shopsmart-submit">; <input type="submit" name="shopsmart-submit">; <input type="number" name="shopsmart-redeemable-amt">; <input type="submit" name="shopsmart-submit">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="golootlo-code-ASW9kVSttdGxBRXZna__golootlo_ecommerce_plugin_star_rating_4mC77F">; <input type="text" name="shopsmart-pin">

4 control(s) properly labeled

11 controls

4 labeled

2 placeholder only

5 unlabeled

Control	Type	Label	Method
#CartGiftWrappingMessage	textarea	Gift message	for/id
#Search	search	Search our store...	aria-label
#CartSpecialInstructions	textarea	Order notes	for/id
shopsmart-phone	number	Phone number...	aria-label
#golootlo-code-ASW9kVSttdGxBRXZna__golootlo_ecommerce_plugin_star_rating_4mC77F	text	(Enter voucher code)	placeholder only
shopsmart-pin	text	(PIN)	placeholder only
shopsmart-submit	submit	(none)	none
quantity	number	(none)	none
shopsmart-submit	submit	(none)	none
shopsmart-redeemable-amt	number	(none)	none
shopsmart-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

66 issue(s) across 266 links and 71 buttons

FIX

66 issue(s) across 266 links and 71 buttons

63 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /account/login; https://www.darimooch.com/collections/charcoal-line; /collections/ice-blast; /collections/glow-line; https://www.darimooch.com/collections/de-tan; https://www.darimooch.com/collections/charcoal-line; https://www.darimooch.com/collections/beard; a.spro-snap-previous (#802 on page); a.spro-snap-link (#804 on page); a.spro-snap-link (#806 on page) (+53 more)

9 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/Darimooch/; https://www.instagram.com/darimooch/; https://www.tiktok.com/@darimooch; https://www.youtube.com/@darimooch5071; https://www.facebook.com/Darimooch/; https://www.instagram.com/darimooch/; https://www.tiktok.com/@darimooch; https://www.youtube.com/@darimooch5071; https://www.instagram.com/han_an.dev/

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.slick-prev (#902 on page); button.slick-next (#977 on page); input[type="submit"].button (#3729 on page)

194 link(s) with descriptive text

266 links

63 empty

0 generic text

9 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
/account/login	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Darimooch/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/darimooch/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@darimooch	Tiktok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@darimooch5071	Youtube	new tab	Add '(opens in new tab)' to text
https://www.darimooch.com/collections/ch…	(empty)	empty	Add link text or aria-label
/collections/ice-blast	(empty)	empty	Add link text or aria-label
/collections/glow-line	(empty)	empty	Add link text or aria-label
https://www.darimooch.com/collections/de…	(empty)	empty	Add link text or aria-label
https://www.darimooch.com/collections/ch…	(empty)	empty	Add link text or aria-label
https://www.darimooch.com/collections/be…	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/collections/fragrance	(empty)	empty	Add link text or aria-label
/collections/ice-blast	(empty)	empty	Add link text or aria-label
https://www.darimooch.com/collections/de…	(empty)	empty	Add link text or aria-label
/collections/beard-growth	(empty)	empty	Add link text or aria-label
/collections/glow-line	(empty)	empty	Add link text or aria-label
/collections/de-tan	(empty)	empty	Add link text or aria-label
/collections/hair-care	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/products/hair-color-cream	(empty)	empty	Add link text or aria-label
/products/surge-perfume	(empty)	empty	Add link text or aria-label
/products/copy-of-anti-hairfall-bundle-c…	(empty)	empty	Add link text or aria-label
/products/charcoal-facewash-charcoal-fac…	(empty)	empty	Add link text or aria-label
/products/bundle-lip-lightener-balm-unde…	(empty)	empty	Add link text or aria-label
/products/copy-of-charcoal-facewash-char…	(empty)	empty	Add link text or aria-label
/products/new-hydro-gel-moisturizer	(empty)	empty	Add link text or aria-label
/products/de-tan-sunscreen-spf-50-by-dar…	(empty)	empty	Add link text or aria-label
/products/new-lip-lightener-balm	(empty)	empty	Add link text or aria-label
/products/lip-balm-copy-1	(empty)	empty	Add link text or aria-label
/products/ice-blast-shampoo	(empty)	empty	Add link text or aria-label
/products/keratin-shampoo	(empty)	empty	Add link text or aria-label
/products/anti-dandruff-shampoo-clear-sc…	(empty)	empty	Add link text or aria-label
/products/2-in-1-shampoo-conditioner	(empty)	empty	Add link text or aria-label
/products/hair-clay-wax	(empty)	empty	Add link text or aria-label
/products/new-hair-wax	(empty)	empty	Add link text or aria-label
/products/hair-clay-wax-hair-wax	(empty)	empty	Add link text or aria-label
/products/glow-bundle-hair-clay-wax	(empty)	empty	Add link text or aria-label
/products/growth-kit	(empty)	empty	Add link text or aria-label
/products/new-beard-growth-oil	(empty)	empty	Add link text or aria-label
/products/new-beard-growth-biotin-spray	(empty)	empty	Add link text or aria-label
/products/new-beard-growth-shampoo	(empty)	empty	Add link text or aria-label
/products/beard-shampoo-copy-1	(empty)	empty	Add link text or aria-label
/products/new-moustache-wax	(empty)	empty	Add link text or aria-label
/products/new-beard-balm	(empty)	empty	Add link text or aria-label
/products/new-dune-perfumed-body-spray	(empty)	empty	Add link text or aria-label
/products/de-tan-body-wash-by-dari-mooch…	(empty)	empty	Add link text or aria-label
/products/new-charcoal-body-wash	(empty)	empty	Add link text or aria-label
/products/glow-body-wash	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Darimooch/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/darimooch/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@darimooch	Tiktok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@darimooch5071	Youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/han_an.dev/	Hanan	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

262 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/account/login; https://www.darimooch.com/collections/charcoal-line; /collections/ice-blast; /collections/glow-line; https://www.darimooch.com/collections/de-tan; https://www.darimooch.com/collections/charcoal-line; https://www.darimooch.com/collections/beard; a.spro-snap-previous (#802 on page); a.spro-snap-link (#804 on page); a.spro-snap-link (#806 on page) (+53 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/Darimooch/; https://www.instagram.com/darimooch/; https://www.tiktok.com/@darimooch; https://www.youtube.com/@darimooch5071; https://www.facebook.com/Darimooch/; https://www.instagram.com/darimooch/; https://www.tiktok.com/@darimooch; https://www.youtube.com/@darimooch5071; https://www.instagram.com/han_an.dev/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.slick-prev (#902 on page); button.slick-next (#977 on page); input[type="submit"].button (#3729 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Tabindex Anti-Patterns

Action

0 positive, 124 -1-on-focusable

FIX

0 positive, 124 -1-on-focusable

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.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button id="slick-slide-control01">

tabindex="-1" on naturally-focusable <button id="slick-slide-control02">

tabindex="-1" on naturally-focusable <button id="slick-slide-control03">

tabindex="-1" on naturally-focusable <button id="slick-slide-control04">

tabindex="-1" on naturally-focusable <button id="slick-slide-control05">

tabindex="-1" on naturally-focusable <button id="slick-slide-control06">

tabindex="-1" on naturally-focusable <button id="slick-slide-control07">

tabindex="-1" on naturally-focusable <button id="slick-slide-control08">

tabindex="-1" on naturally-focusable <button id="slick-slide-control09">

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button id="tab-collection_XWgcBh">

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button id="tab-collection_AUQLN4">

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button>

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #030303

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

Action

5 landmarks

REVIEW

5 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Skip link target(s) don't exist on page: #main

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

Action

47 headings, 1 skip(s)

REVIEW

47 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

3 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Dari Mooch | Pakistan's #1 Men's Grooming Brand
H1 (empty)
H3 Hair Color Cream skipped
H3 Surge Perfume
H2 Best Price
H3 Ultimate Skin and Hair Care Bundle
H3 Ultimate Charcoal Care Bundle
H3 Bundle: Lip Lightener Balm + Under Eye Balm
H3 Charcoal Face Wash + Charcoal Body Wash
H2 Face
H3 Hydro-Gel Moisturizer
H3 De-Tan Sunscreen SPF 50+ by Dari Mooch (110ml)
H3 Lip Lightener Balm
H3 Lip Balm
H2 Hair
H3 Ice Blast Shampoo
H3 New Keratin Shampoo
H3 Anti-Dandruff Shampoo – Clear Scalp & Healthy Hair
H3 2-in-1 Shampoo + Conditioner
H3 Hair Clay Wax
H3 Hair Wax
H3 Hair Clay Wax + Hair Wax
H3 Glow Bundle + Hair Clay Wax
H2 Beard
H3 Beard Growth Kit
H3 Beard Growth Oil
H3 Beard Growth Biotin Spray
H3 Beard Growth Shampoo
H3 Beard Shampoo
H3 Beard Brush
H3 Moustache Wax
H3 Beard Balm
H2 Body
H3 Dune - Perfumed Body Spray
H3 De-Tan Body Wash by Dari Mooch – Tan Removal & Skin Brightening (300ml)
H3 Charcoal Body Wash
H3 Glow Body Wash
H3 Menu
H3 Menu
H3 MINI BIO
H3 Contact
H4 Recent searches
H4 Main menu
H3 (empty)
H3 (empty)
H3 Shopping Cart
H2 Loyalty Points

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

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

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

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

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.

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.

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (3 below threshold)

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: <button> 0.0px ("10"); <p> 10.4px ("Save 29%"); <p> 10.4px ("Save 11%").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Dari Mooch ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 Best Price

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Face

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hair

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Beard

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Body

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Loyalty Points

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Menu

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Menu

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 MINI BIO

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Contact

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shopping Cart

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

19px · bottom of viewport

title Dari Mooch | Pakistan's #1 Men's Groomin…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p Deliveries to the North Region may be de…

3.73:1

#000000

#686768

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

p Deliveries to the North Region may be de…

1.15:1

#000000

#171513

needs 4.5:1 (normal text)

16px · above the fold

p Deliveries to the North Region may be de…

1.14:1

#000000

#161413

needs 4.5:1 (normal text)

16px · above the fold

p Deliveries to the North Region may be de…

1.12:1

#000000

#131211

needs 4.5:1 (normal text)

16px · above the fold

p Deliveries to the North Region may be de…

1.12:1

#000000

#141211

needs 4.5:1 (normal text)

16px · above the fold

p Deliveries to the North Region may be de…

1.11:1

#000000

#12110F

needs 4.5:1 (normal text)

16px · 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)

Element	Ratio	Required	FG	BG	Result
h1 Dari Mooch \| Pakista…	5.94:1	3.0:1	#000000	#88888B	Pass
h2 Best Price	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Face	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Hair	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Beard	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Body	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Loyalty Points	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h3 Menu	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h3 Menu	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h3 MINI BIO	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h3 Contact	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h3 Shopping Cart	1.07:1	3.0:1	#000000	#0B0B0B	Fail
title Dari Mooch \| Pakista…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	16.38:1	4.5:1	#000000	#E2E3E7	Pass
p Deliveries to the No…	3.73:1	4.5:1	#000000	#686768	Fail
p Deliveries to the No…	1.15:1	4.5:1	#000000	#171513	Fail
p Deliveries to the No…	1.14:1	4.5:1	#000000	#161413	Fail
p Deliveries to the No…	1.12:1	4.5:1	#000000	#131211	Fail
p Deliveries to the No…	1.12:1	4.5:1	#000000	#141211	Fail
p Deliveries to the No…	1.11:1	4.5:1	#000000	#12110F	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.

Lighthouse Accessibility Audits

Action

Score 71/100 — 10 failing, 22 passed

REVIEW

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 child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
2 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
1 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
2 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
1 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
2 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
1 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
2 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
1 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`
2 `div.page-navigation-wrapper > ul.page-navigation > li.page-navigation__item > button.page-navigation__button`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#main > div#shopify-section-template--25949681451255__cat_slider_i6wEfF > div.custom-cat-slider-2 > button.slick-prev `div#main > div#shopify-section-template--25949681451255__cat_slider_i6wEfF > div.custom-cat-slider-2 > button.slick-prev`
div#main > div#shopify-section-template--25949681451255__cat_slider_i6wEfF > div.custom-cat-slider-2 > button.slick-next `div#main > div#shopify-section-template--25949681451255__cat_slider_i6wEfF > div.custom-cat-slider-2 > button.slick-next`

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 > div > div > img `div > div > div > img`

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.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link `div.spro-col > div#spro-carousel-template--25949681451255__sp_slideshow_PLkVEx > div.spro-slide > a.spro-slide-link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`
div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link `div.product-card-top > div.o-ratio > div.o-ratio__content > a.product-card__link`

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(13) `product-card-reviews.review-wrapper > div.review-text-wrapper > p.rating-count > span`
(25) `product-card-reviews.review-wrapper > div.review-text-wrapper > p.rating-count > span`
Rs.4,097.00 `product-card-price.price > span.price > span.price__compare > span.money`
(528) `product-card-reviews.review-wrapper > div.review-text-wrapper > p.rating-count > span`
(27) `product-card-reviews.review-wrapper > div.review-text-wrapper > p.rating-count > span`

These are opportunities to improve the legibility of your content.

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
Hair Color Cream `product-card.product-card > div.product-card__details > a.product-card__link > h3.product-card__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
1 2 `div.container > items-scroll.ratio-navigation > div.page-navigation-wrapper > ul.page-navigation`
1 2 `div.container > items-scroll.ratio-navigation > div.page-navigation-wrapper > ul.page-navigation`
1 2 `div.container > items-scroll.ratio-navigation > div.page-navigation-wrapper > ul.page-navigation`
1 2 `div.container > items-scroll.ratio-navigation > div.page-navigation-wrapper > ul.page-navigation`
1 2 `div.container > items-scroll.ratio-navigation > div.page-navigation-wrapper > ul.page-navigation`

These are opportunities to improve the experience of reading tabular or list data using 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`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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
support@darimooch.com `div.o-layout__item > div.footer-nav > p.footer-nav__text > a.footer-nav__text-link`
+92 316 1115556 `div.o-layout__item > div.footer-nav > p.footer-nav__text > a.footer-nav__text-link`

○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

●Form elements have associated labels

●`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 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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○`<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.

○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.

○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+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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+

Alt Text Quality

All 96 images OK

PASS

All 96 images OK

68 decorative image(s) correctly marked

28 image(s) with good alt text

96 images 28 good alt text 68 decorative

All images have appropriate alt text.

A+

Form Input Types

11 form control(s) checked, no type mismatches

PASS

11 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

11 form control(s) checked, no input-semantic issues

PASS

11 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.