Skip to content
https://www.kalpanika.art

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: rgb(246 240 225)
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark 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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
19 headings, 2 skip(s)
REVIEW
19 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Kalpanika.art
  • H2 TO GLOBAL BRANDS.
  • H2 Slideshow
  • H2 your passion, our Dream
  • H2 From the Village to the world
  • H2 Strategy To Market
  • H2 Latest stories
  • H3 National Startup Awards 6.0: India Opens New Opportunities for Emerging Entrepreneurs and Innovators
  • H3 Indian Artisans Generate ₹88.36 Lakh in Sales at Shilp Samagam 2026: Traditional Products Find New Markets
  • H3 India Puts the Creative Economy in Focus: New Opportunities for Creators, Designers and Entrepreneurs
  • H3 India's Merchandise Exports Surge 45% in October: What the Growth Means for Indian Businesses
  • H3 India Looks to Make Global E-commerce Easier for Small Businesses
  • H3 Build a Brand That’s Ready for the World
  • H6 Whether you have a product, a story, a business idea or simply a conversation in mind - we're always open to new possibilities. skipped
  • H6 (empty)
  • H2 Your cart is empty
  • H2 Your cart is empty
  • H2 Search
  • H4 Products skipped

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 ▾

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

B
Alt Text Quality
3 of 52 images have issues
REVIEW
3 of 52 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
31 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
52 images 18 good alt text 31 decorative 3 missing
IssueCount
missing3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Kalpanika.art ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
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
h1 Kalpanika.art
1.07:1
#000000
on
#130902
needs 3.0:1 (large text)
32px · top of page (header area)
h2 TO GLOBAL BRANDS.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · mid-page
h2 Slideshow
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 your passion, our Dream
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From the Village to the world
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Strategy To Market
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest stories
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your cart is empty
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Search
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 National Startup Awards 6.0: India Opens…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Indian Artisans Generate ₹88.36 Lakh i…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 India Puts the Creative Economy in Focus…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 India's Merchandise Exports Surge 45% in…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 India Looks to Make Global E-commerce Ea…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Build a Brand That’s Ready for the Wor…
1.41:1
#000000
on
#3B210B
needs 3.0:1 (large text)
19px · bottom of viewport
title Kalpanika.art
1.53:1
#000000
on
#3E2912
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.06:1
#000000
on
#100903
needs 4.5:1 (normal text)
16px · top of page (header area)
span Home
1.17:1
#000000
on
#241307
needs 4.5:1 (normal text)
16px · top of page (header area)
span Catalog
1.19:1
#000000
on
#25150E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Contact
1.03:1
#000000
on
#070503
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)
ElementRatioRequiredFGBGResult
h1 Kalpanika.art1.07:13.0:1
#000000
#130902
Fail
h2 TO GLOBAL BRANDS.1.00:13.0:1
#000000
#000000
Fail
h2 Slideshow1.41:13.0:1
#000000
#3B210B
Fail
h2 your passion, our Dr…1.41:13.0:1
#000000
#3B210B
Fail
h2 From the Village to …1.41:13.0:1
#000000
#3B210B
Fail
h2 Strategy To Market1.41:13.0:1
#000000
#3B210B
Fail
h2 Latest stories1.41:13.0:1
#000000
#3B210B
Fail
h2 Your cart is empty1.41:13.0:1
#000000
#3B210B
Fail
h2 Search1.41:13.0:1
#000000
#3B210B
Fail
h3 National Startup Awa…1.41:13.0:1
#000000
#3B210B
Fail
h3 Indian Artisans Gene…1.41:13.0:1
#000000
#3B210B
Fail
h3 India Puts the Creat…1.41:13.0:1
#000000
#3B210B
Fail
h3 India's Merchandise …1.41:13.0:1
#000000
#3B210B
Fail
h3 India Looks to Make …1.41:13.0:1
#000000
#3B210B
Fail
h3 Build a Brand That 1.41:13.0:1
#000000
#3B210B
Fail
title Kalpanika.art1.53:14.5:1
#000000
#3E2912
Fail
a Skip to content1.06:14.5:1
#000000
#100903
Fail
span Home1.17:14.5:1
#000000
#241307
Fail
span Catalog1.19:14.5:1
#000000
#25150E
Fail
span Contact1.03:14.5:1
#000000
#070503
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 23 passed
REVIEW
86

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
FROM THE VILLAGE TO THE WORLD Our clients receive hands-on assistance with onl… slideshow-component.slideshow--content-below-media > slideshow-container > slideshow-slides > slideshow-slide

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.

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
Kalpanika.art div.utilities > div.footer-utilities__group-copyright > span.footer-utilities__text > a

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
WHETHER YOU HAVE A PRODUCT, A STORY, A BUSINESS IDEA OR SIMPLY A CONVERSATION I… div.border-style > div.spacing-style > rte-formatter.spacing-style > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media
div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media
div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media

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
NOVEMBER 14, 2026 INDIA PUTS THE CREATIVE ECONOMY IN FOCUS: NEW OPPORTUNITIES F… blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw > div.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__viewport > div.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__track > a.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__card
NOVEMBER 14, 2026 INDIA'S MERCHANDISE EXPORTS SURGE 45% IN OCTOBER: WHAT THE GR… blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw > div.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__viewport > div.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__track > a.ai-blog-carousel-amer1zlhju0kwzm8xoaigenblock5cd8192ecrpbw__card
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements 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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
○`[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
○Links are distinguishable without relying on color.
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" SEARCH MAIN CONTENTINFO footer

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H6: 127 chars
Got: 1 >120-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ContactForm-nametextNamefor/id
#ContactForm-emailemailEmail*for/id
#ContactForm-phonetelPhonefor/id
#ContactForm-bodytextareaCommentfor/id
#EmailInput-AU3ZvV24zR3k5blh1c__email_signup_t3aAfiemailEmailfor/id
#cmdk-inputsearchSearchfor/id
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
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.)
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.kalpanika.art/web-pixels@7c8e7afaw45178ba9pf12000acme993a4d3/custom…")
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 71 visible text node(s) render at >= 12 CSS pixels
PASS
All 71 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback