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 7 REVIEW 5 FIX

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

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://dhanukaenterprises.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://dhanukaenterprises.com/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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

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

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

20 headings, 2 skip(s)

REVIEW

20 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

H2 DHANUKA ENTERPRISES
H1 India's Trusted Supplier of Plywood, MDF & Laminates Since 1997
H2 Dhanuka Enterprises Pvt. Ltd.
H2 A Wide Range of Wood Panel Solutions
H4 Plywood & Block Boards skipped
H4 MDF & HDF
H4 Particle Boards
H4 PVC & WPC Boards
H4 Laminates & Veneers
H4 Decorative Panels
H4 Special Purpose Boards
H4 Accessories & Hardware
H2 Solutions for Every Professional
H2 Partnering with Industry Leaders
H2 Let's Discuss Your Requirement
H2 Frequently Asked Questions
H5 Quick Links skipped
H5 Products
H5 Contact Us
H4 Dhanuka Enterprises

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

4 issue(s) across 57 links and 6 buttons

REVIEW

4 issue(s) across 57 links and 6 buttons

4 link(s) with no accessible text

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

Got: https://www.facebook.com/dhanukaenterprises; http://instagram.com/dhanuka.enterprises/; https://www.linkedin.com/company/dhanuka-enterprises-pvt-ltd; https://www.youtube.com/@dhanukaenterprises

2 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/in/mamapriyadarshini/; https://wa.me/919886722877?text=Hello%20Dhanuka%20Enterprises!%20I%20am%20int…

51 link(s) with descriptive text

57 links

4 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/dhanukaenterpri…	(empty)	empty	Add link text or aria-label
http://instagram.com/dhanuka.enterprises…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/dhanuka…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@dhanukaenterpri…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/mamapriyadar…	Priyadarshini	new tab	Add '(opens in new tab)' to text
https://wa.me/919886722877?text=Hello%20…	Start Chat on WhatsApp	new tab	Add '(opens in new tab)' to text

57 links and buttons have descriptive text

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

https://www.facebook.com/dhanukaenterprises; http://instagram.com/dhanuka.enterprises/; https://www.linkedin.com/company/dhanuka-enterprises-pvt-ltd; https://www.youtube.com/@dhanukaenterprises

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.linkedin.com/in/mamapriyadarshini/; https://wa.me/919886722877?text=Hello%20Dhanuka%20Enterprises!%20I%20am%20int…

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

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (6 below threshold)

6 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <small> 10.0px ("ESTD. 1997"); <div> 11.0px ("ABOUT US"); <div> 11.0px ("OUR PRODUCTS"); <div> 11.0px ("BRANDS WE WORK WITH"); <div> 11.0px ("FAQ").

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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, 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

h1 India's Trusted Supplier of

1.97:1

#000000

#4C3B2E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Since 1997

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Dhanuka Enterprises Pvt. Ltd.

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A Wide Range of Wood Panel Solutions

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Solutions for Every Professional

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Partnering with Industry Leaders

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let's Discuss Your Requirement

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

2.06:1

#000000

#1A4A2E

needs 3.0:1 (large text)

24px · bottom of viewport

p Premium Wood Panel Solutions

1.32:1

#000000

#341C0B

needs 4.5:1 (normal text)

16px · top of page (header area)

strong DHANUKA

1.38:1

#000000

#391F0D

needs 3.0:1 (large text)

16px · top of page (header area)

strong ENTERPRISES PVT. LTD.

1.30:1

#000000

#321B0B

needs 3.0:1 (large text)

16px · above the fold

small ESTD. 1997

3.01:1

#000000

#6B5543

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a HOME

3.30:1

#000000

#725B45

needs 4.5:1 (normal text)

16px · above the fold

a ABOUT US

2.88:1

#000000

#6F5037

needs 4.5:1 (normal text)

16px · above the fold

a PRODUCTS

3.14:1

#000000

#715742

needs 4.5:1 (normal text)

16px · above the fold

a BLOG

1.48:1

#000000

#3B261C

needs 4.5:1 (normal text)

16px · above the fold

a APPLICATIONS

1.40:1

#000000

#3B2013

needs 4.5:1 (normal text)

16px · above the fold

a GALLERY

1.40:1

#000000

#3B2012

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 India's Trusted Supp…	1.97:1	3.0:1	#000000	#4C3B2E	Fail
h1 Since 1997	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 DHANUKA ENTERPRISES	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Dhanuka Enterprises …	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 A Wide Range of Wood…	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 Solutions for Every …	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 Partnering with Indu…	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 Let's Discuss Your R…	2.06:1	3.0:1	#000000	#1A4A2E	Fail
h2 Frequently Asked Que…	2.06:1	3.0:1	#000000	#1A4A2E	Fail
title Dhanuka Enterprises …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Premium Wood Panel S…	1.32:1	4.5:1	#000000	#341C0B	Fail
strong DHANUKA	1.38:1	3.0:1	#000000	#391F0D	Fail
strong ENTERPRISES PVT. LTD…	1.30:1	3.0:1	#000000	#321B0B	Fail
small ESTD. 1997	3.01:1	4.5:1	#000000	#6B5543	Fail
a HOME	3.30:1	4.5:1	#000000	#725B45	Fail
a ABOUT US	2.88:1	4.5:1	#000000	#6F5037	Fail
a PRODUCTS	3.14:1	4.5:1	#000000	#715742	Fail
a BLOG	1.48:1	4.5:1	#000000	#3B261C	Fail
a APPLICATIONS	1.40:1	4.5:1	#000000	#3B2013	Fail
a GALLERY	1.40:1	4.5:1	#000000	#3B2012	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 76/100 — 4 failing, 10 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.

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
Premium Wood Panel Solutions `body > div#loader > p`
ESTD. 1997 `div.logo > div.logo > div.logo-text > small`
Explore Products → `div.hero-inner > div.hero-content > div.hero-btns > a.btn-primary`
ABOUT US `div.about-content > div.about-grid > div.about-content > div.section-label`
We cater to a wide range of customers including furniture manufacturers, OEMs, … `div.about-content > div.about-grid > div.about-content > p`
Read More About Us → `div.about-content > div.about-grid > div.about-content > a.btn-primary`
OUR PRODUCTS `section > div.section-inner > div.text-center > div.section-label`
High-quality plywood suitable for furniture, interiors and construction. `div.products-grid > a.product-card > div.product-info > p`
Smooth, uniform boards for modern furniture and interior applications. `div.products-grid > a.product-card > div.product-info > p`
Economical and versatile boards for a wide range of applications. `div.products-grid > a.product-card > div.product-info > p`
Waterproof and durable boards for modern construction needs. `div.products-grid > a.product-card > div.product-info > p`
Elegant surface solutions to enhance the beauty of your spaces. `div.products-grid > a.product-card > div.product-info > p`
Stylish panels to add character and beauty to any interior. `div.products-grid > a.product-card > div.product-info > p`
Boards engineered for specific industrial and technical needs. `div.products-grid > a.product-card > div.product-info > p`
Adhesives, hardware and all accessories for complete solutions. `div.products-grid > a.product-card > div.product-info > p`
View All Products → `section > div.section-inner > div > a.btn-primary`
BRANDS WE WORK WITH `section.brands-section > div.section-inner > div.text-center > div.section-label`
Send Enquiry → `body > section.cta-strip > div.cta-container > a.cta-btn`
FAQ `section.faq-section > div.section-inner > div.text-center > div.section-label`
Find answers to common questions about plywood, MDF boards, laminates, veneers … `section.faq-section > div.section-inner > div.text-center > p.section-sub`
© 2024 Dhanuka Enterprises Pvt. Ltd. All Rights Reserved. `footer > div.footer-inner > div.footer-bottom > span`
Designed & Developed by Priyadarshini `footer > div.footer-inner > div.footer-bottom > div`
Priyadarshini `div.footer-inner > div.footer-bottom > div > a.designer-link`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-inner > div.footer-col > div.footer-map > iframe `div.footer-inner > div.footer-col > div.footer-map > iframe`

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.footer-inner > div.footer-brand > div.footer-socials > a.social-btn `div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn`
div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn `div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn`
div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn `div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn`
div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn `div.footer-inner > div.footer-brand > div.footer-socials > a.social-btn`

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.

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
Plywood & Block Boards `div.products-grid > a.product-card > div.product-info > h4`
QUICK LINKS `footer > div.footer-inner > div.footer-col > h5`

These are opportunities to improve keyboard navigation in your application.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●Touch targets have sufficient size and spacing.

●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

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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

20 image(s) with good alt text

20 images 20 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

Iframe Accessibility

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

PASS

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

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.

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