Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

4/5 eligible field(s) missing autocomplete or inputmode

FIX

4/5 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.

Got: <input type="tel" id="customerMobile">

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, tel.

Got: <input type="search" id="searchInput">, <input type="tel" id="trackingMobile">, <input type="tel" id="customerMobile">

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-bs7bo9

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.dhiveennatural.in/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.dhiveennatural.in/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark 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

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

Heading Hierarchy

4 headings

REVIEW

4 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Our Products
H2 Your Cart
H2 Track Your Order
H2 Checkout

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

Action

9 of 11 controls have issues

REVIEW

9 of 11 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" id="customerState">

8 control(s) rely on placeholder only

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

Got: <input type="search" id="searchInput">; <input type="text" id="trackingOrderId">; <input type="tel" id="trackingMobile">; <input type="text" id="customerName">; <input type="tel" id="customerMobile">; <textarea id="customerAddress">; <input type="text" id="customerCity">; <input type="text" id="customerPincode">

2 control(s) properly labeled

11 controls

2 labeled

8 placeholder only

1 unlabeled

Control	Type	Label	Method
payment	radio		none
payment	radio		none
#trackingMobile	tel	(10 digit mobile number)	placeholder only
#customerName	text	(Enter your name)	placeholder only
#customerMobile	tel	(10 digit mobile number)	placeholder only
#customerAddress	textarea	(House / Street / Area)	placeholder only
#customerCity	text	(City)	placeholder only
#customerPincode	text	(Pincode)	placeholder only
#searchInput	search	(Search products...)	placeholder only
#trackingOrderId	text	(Example: DN12345678)	placeholder only
#customerState	text	(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

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (29 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (29 below threshold)

29 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: <div> 11.0px ("HOMEMADE SOAP"); <div> 11.0px ("HOMEMADE SOAP"); <div> 11.0px ("HOMEMADE SOAP"); <div> 11.0px ("HOMEMADE SOAP"); <div> 11.0px ("HOMEMADE SOAP").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Our Products

1.18:1

#000000

#051C15

needs 3.0:1 (large text)

24px · above the fold

h2 Your Cart

1.19:1

#000000

#041D15

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Track Your Order

1.19:1

#000000

#041D15

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Checkout

1.19:1

#000000

#041D15

needs 3.0:1 (large text)

24px · bottom of viewport

title DHIVEEN NATURAL

1.14:1

#000000

#031811

needs 4.5:1 (normal text)

16px · top of page (header area)

button 👤 My Account

1.14:1

#000000

#031811

needs 4.5:1 (normal text)

16px · top of page (header area)

button 📦 Track Order

1.15:1

#000000

#031912

needs 4.5:1 (normal text)

16px · top of page (header area)

button 🛒 Cart

1.17:1

#000000

#041B14

needs 4.5:1 (normal text)

16px · top of page (header area)

button ALL

1.16:1

#000000

#041A13

needs 4.5:1 (normal text)

16px · above the fold

button HOMEMADE SOAP

1.16:1

#000000

#041A13

needs 4.5:1 (normal text)

16px · above the fold

button HAIR CARE

1.16:1

#000000

#041A13

needs 4.5:1 (normal text)

16px · above the fold

button HOUSEHOLD LIQUID

1.16:1

#000000

#041A13

needs 4.5:1 (normal text)

16px · above the fold

button PERSONAL CARE

1.16:1

#000000

#041A13

needs 4.5:1 (normal text)

16px · above the fold

button HOME & KITCHEN

1.17:1

#000000

#041B14

needs 4.5:1 (normal text)

16px · above the fold

button ART& CRAFT

1.18:1

#000000

#041C15

needs 4.5:1 (normal text)

16px · above the fold

button HOME DECOR

1.18:1

#000000

#051C15

needs 4.5:1 (normal text)

16px · above the fold

div HOMEMADE SOAP

1.18:1

#000000

#051C15

needs 4.5:1 (normal text)

16px · mid-page

div DHIVEEN NATURAL Avarampoo Soap

1.19:1

#000000

#051D15

needs 4.5:1 (normal text)

16px · mid-page

div Avarampoo Handmade Soap for a refreshing…

1.18:1

#000000

#041C14

needs 4.5:1 (normal text)

16px · mid-page

span ₹79

1.18:1

#000000

#041C14

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Our Products	1.18:1	3.0:1	#000000	#051C15	Fail
h2 Your Cart	1.19:1	3.0:1	#000000	#041D15	Fail
h2 Track Your Order	1.19:1	3.0:1	#000000	#041D15	Fail
h2 Checkout	1.19:1	3.0:1	#000000	#041D15	Fail
title DHIVEEN NATURAL	1.14:1	4.5:1	#000000	#031811	Fail
button 👤 My Account	1.14:1	4.5:1	#000000	#031811	Fail
button 📦 Track Order	1.15:1	4.5:1	#000000	#031912	Fail
button 🛒 Cart	1.17:1	4.5:1	#000000	#041B14	Fail
button ALL	1.16:1	4.5:1	#000000	#041A13	Fail
button HOMEMADE SOAP	1.16:1	4.5:1	#000000	#041A13	Fail
button HAIR CARE	1.16:1	4.5:1	#000000	#041A13	Fail
button HOUSEHOLD LIQUID	1.16:1	4.5:1	#000000	#041A13	Fail
button PERSONAL CARE	1.16:1	4.5:1	#000000	#041A13	Fail
button HOME & KITCHEN	1.17:1	4.5:1	#000000	#041B14	Fail
button ART& CRAFT	1.18:1	4.5:1	#000000	#041C15	Fail
button HOME DECOR	1.18:1	4.5:1	#000000	#051C15	Fail
div HOMEMADE SOAP	1.18:1	4.5:1	#000000	#051C15	Fail
div DHIVEEN NATURAL Avar…	1.19:1	4.5:1	#000000	#051D15	Fail
div Avarampoo Handmade S…	1.18:1	4.5:1	#000000	#041C14	Fail
span ₹79	1.18:1	4.5:1	#000000	#041C14	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.

A+

Heading Text Quality

All 4 heading(s) have substantive, well-formed text

PASS

All 4 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 31 images OK

PASS

All 31 images OK

31 image(s) with good alt text

31 images 31 good alt text

All images have appropriate alt text.

A+

Link & Button Quality

7 links, 48 buttons — all OK

PASS

7 links, 48 buttons — all OK

7 link(s) with descriptive text

7 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

55 links and buttons have descriptive 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+

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 13 passed

PASS

100

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.

○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-hidden="true"]` is not present on the document `<body>`

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

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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