Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CHeading HierarchyAction19 headings, 2 skip(s)REVIEW
- 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.
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.
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.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
BAlt Text Quality3 of 52 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 3 image(s) |
Images without alt text are invisible to screen readers.
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
BLink & Button Quality1 issue(s) across 57 links and 16 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /collections/frontpage | (empty) | empty | Add link text or aria-label |
| https://www.facebook.com/profile.php?id=… | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/kalpanika.art/ | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
/collections/frontpage
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/profile.php?id=61593651787052; https://www.instagram.com/kalpanika.art/
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
C404 Error PageActionHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
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 Kalpanika.art | 1.07:1 | 3.0:1 | #000000 | #130902 | Fail |
| h2 TO GLOBAL BRANDS. | 1.00:1 | 3.0:1 | #000000 | #000000 | Fail |
| h2 Slideshow | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 your passion, our Dr… | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 From the Village to … | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 Strategy To Market | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 Latest stories | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 Your cart is empty | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h2 Search | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 National Startup Awa… | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 Indian Artisans Gene… | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 India Puts the Creat… | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 India's Merchandise … | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 India Looks to Make … | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| h3 Build a Brand That  | 1.41:1 | 3.0:1 | #000000 | #3B210B | Fail |
| title Kalpanika.art | 1.53:1 | 4.5:1 | #000000 | #3E2912 | Fail |
| a Skip to content | 1.06:1 | 4.5:1 | #000000 | #100903 | Fail |
| span Home | 1.17:1 | 4.5:1 | #000000 | #241307 | Fail |
| span Catalog | 1.19:1 | 4.5:1 | #000000 | #25150E | Fail |
| span Contact | 1.03:1 | 4.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.
BLighthouse Accessibility AuditsScore 86/100 — 5 failing, 23 passedREVIEW
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.
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.
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.
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.
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.
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 |
ALandmark Structure10 landmarksPASS
Multiple navigations need aria-label to distinguish them for screen readers.
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
AHeading Text Quality2 heading-text-quality issue(s) detectedPASS
A+Form AccessibilityAll 6 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #ContactForm-name | text | Name | for/id |
| #ContactForm-email | Email* | for/id | |
| #ContactForm-phone | tel | Phone | for/id |
| #ContactForm-body | textarea | Comment | for/id |
| #EmailInput-AU3ZvV24zR3k5blh1c__email_signup_t3aAfi | for/id | ||
| #cmdk-input | search | Search | for/id |