https://murti-hub-neon.vercel.app/?page=shop-all&category=Gajanan+Maharaj

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

65% of visible text renders at >= 12 CSS px (24 below threshold)

FIX

65% of visible text renders at >= 12 CSS px (24 below threshold)

24 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> 11.0px ("SIGN IN"); <span> 10.0px ("RELEVANT COLLECTIONS"); <span> 11.0px ("Deity:"); <span> 11.0px ("Gajanan Maharaj"); <button> 11.0px ("Reset All").

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-2mmzmi

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://murti-hub-neon.vercel.app/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://murti-hub-neon.vercel.app/manifest.json

Manifest contains invalid JSON.

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Link & Button Quality

3 issue(s) across 5 links and 54 buttons

REVIEW

3 issue(s) across 5 links and 54 buttons

1 link(s) open in new tab without warning

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

Got: https://maps.app.goo.gl/Ekzz1e5eooC5WbEg6

3 button(s) with no accessible text

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

Got: button.p-1 (#172 on page); button.p-1 (#178 on page); button.p-1 (#185 on page)

4 link(s) with descriptive text

5 links

0 empty

0 generic text

1 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.app.goo.gl/Ekzz1e5eooC5WbEg…	Showroom on Google Maps	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

55 links and buttons have descriptive text

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

https://maps.app.goo.gl/Ekzz1e5eooC5WbEg6

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.p-1 (#172 on page); button.p-1 (#178 on page); button.p-1 (#185 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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 4 pass AA only

title Gajanan Maharaj Murtis | Amol Marble Mur…

1.21:1

#000000

#2B1408

needs 4.5:1 (normal text)

16px · top of page (header area)

span प्रवेश करा • Enter S…

1.51:1

#000000

#432511

needs 4.5:1 (normal text)

16px · top of page (header area)

span क्लिक करा • Click anyw…

1.80:1

#000000

#552F15

needs 4.5:1 (normal text)

16px · top of page (header area)

button HOME

2.13:1

#000000

#683618

needs 4.5:1 (normal text)

16px · top of page (header area)

button ABOUT

2.44:1

#000000

#773C18

needs 4.5:1 (normal text)

16px · above the fold

button SHOP

3.17:1

#000000

#8A4D24

needs 4.5:1 (normal text)

16px · above the fold

button CONTACT

3.57:1

#000000

#985223

needs 4.5:1 (normal text)

16px · above the fold

span SIGN IN

4.24:1

#000000

#9E622D

needs 4.5:1 (normal text)

16px · above the fold

span RELEVANT COLLECTIONS

3.07:1

#000000

#7F501B

needs 4.5:1 (normal text)

16px · above the fold

span Gajanan Maharaj

2.95:1

#000000

#794F1C

needs 4.5:1 (normal text)

16px · above the fold

span Navratri Festive Drop 2026

2.93:1

#000000

#7A4E16

needs 4.5:1 (normal text)

16px · above the fold

span Shiva

3.18:1

#000000

#835214

needs 4.5:1 (normal text)

16px · mid-page

span Hanuman

3.99:1

#000000

#92621F

needs 4.5:1 (normal text)

16px · mid-page

span Durga & Shakti

4.20:1

#000000

#A1601A

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Gajanan Maharaj Murt…	3.99:1	3.0:1	#000000	#93612B	Pass
h3 Sant Shiromani Shri …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Shri Gajanan Maharaj…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Gajanan Maharaj Murt…	1.21:1	4.5:1	#000000	#2B1408	Fail
span प्रवेश �…	1.51:1	4.5:1	#000000	#432511	Fail
span क्लिक क�…	1.80:1	4.5:1	#000000	#552F15	Fail
button HOME	2.13:1	4.5:1	#000000	#683618	Fail
button ABOUT	2.44:1	4.5:1	#000000	#773C18	Fail
button SHOP	3.17:1	4.5:1	#000000	#8A4D24	Fail
button CONTACT	3.57:1	4.5:1	#000000	#985223	Fail
span SIGN IN	4.24:1	4.5:1	#000000	#9E622D	Fail
span RELEVANT COLLECTIONS	3.07:1	4.5:1	#000000	#7F501B	Fail
span Gajanan Maharaj	2.95:1	4.5:1	#000000	#794F1C	Fail
span Navratri Festive Dro…	2.93:1	4.5:1	#000000	#7A4E16	Fail
span Shiva	3.18:1	4.5:1	#000000	#835214	Fail
span Hanuman	3.99:1	4.5:1	#000000	#92621F	Fail
span Krishna	5.23:1	4.5:1	#000000	#A7752D	Pass
span Ganpati	5.78:1	4.5:1	#000000	#B57A2B	Pass
span Ram	5.37:1	4.5:1	#000000	#B27324	Pass
span Durga & Shakti	4.20:1	4.5:1	#000000	#A1601A	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.

Heading Hierarchy

6 headings, 1 skip(s)

PASS

6 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Gajanan Maharaj Murtis – Amol Marble Murti Bhandar Shegaon
H3 Sant Shiromani Shri Gajanan Maharaj Seated Idol in White Makrana Marble skipped
H3 Shri Gajanan Maharaj Shegaon Avatar with Marigold Garland - Hand-Finished Marble
H4 • HELP & INFO
H4 • SHOPPING POLICIES
H4 • OUR COLLECTION

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

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 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: 3 all-caps heading(s)

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

2 image(s) with alt text over 125 characters

15 image(s) with good alt text

17 images 15 good alt text

Issue	Count
too long	2 image(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <select>

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
select	select	(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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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.

Lighthouse Accessibility Audits

Score 90/100 — 4 failing, 23 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reset All `main#main-content > div.min-h-screen > div.max-w-[1400px] > button.text-[11px]`
GAJANAN MAHARAJ `article.catalog-grid-card > div > div.flex > span.truncate`
₹1,999 `article.catalog-grid-card > div > div.flex > span.text-[10px]`
GAJANAN MAHARAJ `article.catalog-grid-card > div > div.flex > span.truncate`
₹2,299 `article.catalog-grid-card > div > div.flex > span.text-[10px]`

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
Sant Shiromani Shri Gajanan Maharaj Seated Idol in White Makrana Marble `div.grid > article.catalog-grid-card > div > h3.text-[11.5px]`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Featured A to Z Price: Low to High Price: High to Low `div.max-w-[1400px] > div.flex > div.flex > select.border`

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.

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
प्रवेश करा • ENTER STORE `div.min-h-screen > div.fixed > div.absolute > button.group`
क्लिक करा • CLICK ANYWHERE TO ENTER `div.fixed > footer.relative > div.transition-all > button.text-xs`

○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

●Image elements have `[alt]` attributes

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

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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

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