Skip to content
https://www.manikarnikaevents.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
D
Mobile-Readable Font Sizes
Action
40% of visible text renders at >= 12 CSS px (230 below threshold)
FIX
40% of visible text renders at >= 12 CSS px (230 below threshold)
Warning::
230 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> 10.5px ("Events • Media • Entertainment"); <span> 11.0px ("EST. VARANASI • PAN INDIA"); <span> 9.0px ("EXPLORE DOWN"); <span> 10.0px ("Live Concert Footage"); <span> 11.0px ("Floorplans").
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-ci0q1y
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.

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: #060606
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
50 headings, 1 skip(s)
REVIEW
50 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 MANIKARNIKA
  • H2 "Every event deserves its own identity."
  • H1 MANIKARNIKA duplicate H1
  • H2 TURNINGREALSTORIESINTOUNFORGETTABLELIFELONGMOMENTS.
  • H2 BASED IN VARANASI AND WORKING PAN-INDIA, WE PLAN, BUILD, AND RUN EVENTS THAT PEOPLE TALK ABOUT YEARS LATER.
  • H3 NO SHORTCUTS, NO COOKIE-CUTTER TEMPLATES,
  • H3 JUST HONEST BUDGETS, DIRECT ARTIST TIE-UPS, AND METICULOUS EXECUTION THAT LETS YOU ENJOY YOUR OWN BIG DAY.
  • H2 WHAT WE create
  • H3 EVENT PLANNING & MANAGEMENT↗
  • H3 CORPORATE EVENTS & SUMMITS↗
  • H3 BRAND PROMOTIONS & ACTIVATIONS↗
  • H3 ARTIST & CELEBRITY MANAGEMENT↗
  • H3 INFLUENCER & CREATOR EVENTS↗
  • H3 LIVE ENTERTAINMENT & SHOWS↗
  • H3 CULTURAL & SOCIAL CELEBRATIONS↗
  • H3 AWARDS & RECOGNITION CEREMONIES↗
  • H3 WEDDINGS & BESPOKE CELEBRATIONS↗
  • H2 BUILT BY manikarnika
  • H3 Ruby Mishra Live @ Aagman 2026
  • H3 Laqshay Kapoor Live @ HIMS Fest
  • H3 5 Years of Hack 2 Skills ft. Anand Raaj Anand
  • H3 Sudhanshu Raj Khare Wedding Celebration
  • H3 Shahzad Ali @ Chetak Screen Awards
  • H3 Delhi Events
  • H3 Dandiya Events
  • H3 Sfx category
  • H3 Ruby Mishra Live @ Aagman 2026
  • H3 Laqshay Kapoor Live @ HIMS Fest
  • H3 5 Years of Hack 2 Skills ft. Anand Raaj Anand
  • H3 Sudhanshu Raj Khare Wedding Celebration
  • H3 Shahzad Ali @ Chetak Screen Awards
  • H3 Delhi Events
  • H3 Dandiya Events
  • H3 Sfx category
  • H3 Ruby Mishra Live @ Aagman 2026
  • H3 Laqshay Kapoor Live @ HIMS Fest
  • H3 5 Years of Hack 2 Skills ft. Anand Raaj Anand
  • H3 Sudhanshu Raj Khare Wedding Celebration
  • H3 Shahzad Ali @ Chetak Screen Awards
  • H3 Delhi Events
  • H3 Dandiya Events
  • H3 Sfx category
  • H2 WHY CHOOSE our team
  • H4 Custom Concepts Only skipped
  • H4 Roots in Kashi, Active Pan-India
  • H4 Direct Artist Bookings
  • H4 Our Own Sound & Trussing
  • H2 Words Of trust
  • H2 Get In Touchwork with us, build with us, celebrate with us, but first…
  • H3 MANIKARNIKA

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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 MANIKARNIKA
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · top of page (header area)
h2 "Every event deserves its own identity."
1.01:1
#000000
on
#030202
needs 3.0:1 (large text)
24px · mid-page
h2 BASED IN VARANASI AND WORKING PAN-INDIA,…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 WHAT WE
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 BUILT BY
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 WHY CHOOSE
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Words Of
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get In Touch
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 NO SHORTCUTS, NO COOKIE-CUTTER TEMPLATES…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 JUST HONEST BUDGETS, DIRECT ARTIST TIE-U…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EVENT PLANNING & MANAGEMENT
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CORPORATE EVENTS & SUMMITS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 BRAND PROMOTIONS & ACTIVATIONS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ARTIST & CELEBRITY MANAGEMENT
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 INFLUENCER & CREATOR EVENTS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 LIVE ENTERTAINMENT & SHOWS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CULTURAL & SOCIAL CELEBRATIONS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AWARDS & RECOGNITION CEREMONIES
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 WEDDINGS & BESPOKE CELEBRATIONS
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ruby Mishra Live @ Aagman 2026
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 MANIKARNIKA1.00:13.0:1
#000000
#000000
Fail
h2 "Every event deserve…1.01:13.0:1
#000000
#030202
Fail
h2 BASED IN VARANASI AN…1.00:13.0:1
#000000
#000000
Fail
h2 WHAT WE1.00:13.0:1
#000000
#000000
Fail
h2 BUILT BY1.00:13.0:1
#000000
#000000
Fail
h2 WHY CHOOSE1.00:13.0:1
#000000
#000000
Fail
h2 Words Of1.00:13.0:1
#000000
#000000
Fail
h2 Get In Touch1.00:13.0:1
#000000
#000000
Fail
h3 NO SHORTCUTS, NO COO…1.00:13.0:1
#000000
#000000
Fail
h3 JUST HONEST BUDGETS,…1.00:13.0:1
#000000
#000000
Fail
h3 EVENT PLANNING & MAN…1.00:13.0:1
#000000
#000000
Fail
h3 CORPORATE EVENTS & S…1.00:13.0:1
#000000
#000000
Fail
h3 BRAND PROMOTIONS & A…1.00:13.0:1
#000000
#000000
Fail
h3 ARTIST & CELEBRITY M…1.00:13.0:1
#000000
#000000
Fail
h3 INFLUENCER & CREATOR…1.00:13.0:1
#000000
#000000
Fail
h3 LIVE ENTERTAINMENT &…1.00:13.0:1
#000000
#000000
Fail
h3 CULTURAL & SOCIAL CE…1.00:13.0:1
#000000
#000000
Fail
h3 AWARDS & RECOGNITION…1.00:13.0:1
#000000
#000000
Fail
h3 WEDDINGS & BESPOKE C…1.00:13.0:1
#000000
#000000
Fail
h3 Ruby Mishra Live @ A…1.00:13.0:1
#000000
#000000
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 — 3 failing, 16 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.

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
© 2026 MANIKARNIKA EVENTS. ALL RIGHTS RESERVED. div.relative > footer.w-full > div.w-full > span
CRAFTED FOR EXTRAORDINARY EXPERIENCES • VARANASI • PAN INDIA footer.w-full > div.w-full > div.flex > span

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
div.grid > div.reveal-on-scroll > div > h4.text-xl div.grid > div.reveal-on-scroll > div > h4.text-xl

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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 have a discernible name
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
16 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: 16 all-caps heading(s)
A
Alt Text Quality
24 of 28 images have issues
PASS
24 of 28 images have issues
Warning::
24 image(s) with generic alt text
Info::
4 image(s) with good alt text
28 images 4 good alt text 24 generic
IssueCount
generic24 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Manikarnika Events - Premier Event Management & Entertainment
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Manikarnika Events - Premier Event Management & Entertainment ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Manikarnika Events - Premier Event Management & Entertainment Display Mode standalone Theme Color #060606 Background Color #060606 Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
3 mobile-depth signal(s) detected
PASS
3 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::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
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