Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

Mobile-Readable Font Sizes

Action

68% of visible text renders at >= 12 CSS px (16 below threshold)

FIX

68% of visible text renders at >= 12 CSS px (16 below threshold)

16 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"); <p> 10.0px ("Events • Media • Entertainment").

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-21v8ot

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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

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

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

Hamburger menu detected (responsive design)

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)

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

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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.03:1

#000000

#02050A

needs 3.0:1 (large text)

32px · top of page (header area)

h2 "Every event deserves its own identity."

1.86:1

#000000

#37394E

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 BASED IN VARANASI AND WORKING PAN-INDIA,…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 NO SHORTCUTS, NO COOKIE-CUTTER TEMPLATES…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 JUST HONEST BUDGETS, DIRECT ARTIST TIE-U…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 MANIKARNIKA

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Manikarnika Events | Event Management & …

1.02:1

#000000

#010407

needs 4.5:1 (normal text)

16px · top of page (header area)

p ARCHITECTS OF EXPERIENCES

1.03:1

#000000

#02060E

needs 4.5:1 (normal text)

16px · top of page (header area)

span INITIALIZING

1.04:1

#000000

#030711

needs 4.5:1 (normal text)

16px · top of page (header area)

span MANIKARNIKA

1.05:1

#000000

#030813

needs 4.5:1 (normal text)

16px · above the fold

span Events • Media • Entertainment

1.05:1

#000000

#030915

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.27:1

#000000

#231A35

needs 4.5:1 (normal text)

16px · above the fold

a About

1.38:1

#000000

#1A224C

needs 4.5:1 (normal text)

16px · above the fold

a Services

1.13:1

#000000

#080F36

needs 4.5:1 (normal text)

16px · above the fold

a Blog

1.16:1

#000000

#10142E

needs 4.5:1 (normal text)

16px · above the fold

a Contact

1.25:1

#000000

#171B3A

needs 4.5:1 (normal text)

16px · above the fold

a +91 8887519449

1.28:1

#000000

#1A1D3C

needs 4.5:1 (normal text)

16px · above the fold

button Talk to us

1.22:1

#000000

#181834

needs 4.5:1 (normal text)

16px · mid-page

span ●

1.17:1

#000000

#16142E

needs 4.5:1 (normal text)

16px · mid-page

p Creating Experiences. Celebrating Moment…

2.23:1

#000000

#3F4847

needs 4.5:1 (normal text)

16px · mid-page

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 MANIKARNIKA	1.03:1	3.0:1	#000000	#02050A	Fail
h2 "Every event deserve…	1.86:1	3.0:1	#000000	#37394E	Fail
h2 BASED IN VARANASI AN…	1.00:1	3.0:1	#000000	#000000	Fail
h3 NO SHORTCUTS, NO COO…	1.00:1	3.0:1	#000000	#000000	Fail
h3 JUST HONEST BUDGETS,…	1.00:1	3.0:1	#000000	#000000	Fail
h3 MANIKARNIKA	1.00:1	3.0:1	#000000	#000000	Fail
title Manikarnika Events \|…	1.02:1	4.5:1	#000000	#010407	Fail
p ARCHITECTS OF EXPERI…	1.03:1	4.5:1	#000000	#02060E	Fail
span INITIALIZING	1.04:1	4.5:1	#000000	#030711	Fail
span MANIKARNIKA	1.05:1	4.5:1	#000000	#030813	Fail
span Events • Media •…	1.05:1	4.5:1	#000000	#030915	Fail
a Home	1.27:1	4.5:1	#000000	#231A35	Fail
a About	1.38:1	4.5:1	#000000	#1A224C	Fail
a Services	1.13:1	4.5:1	#000000	#080F36	Fail
a Blog	1.16:1	4.5:1	#000000	#10142E	Fail
a Contact	1.25:1	4.5:1	#000000	#171B3A	Fail
a +91 8887519449	1.28:1	4.5:1	#000000	#1A1D3C	Fail
button Talk to us	1.22:1	4.5:1	#000000	#181834	Fail
span ●	1.17:1	4.5:1	#000000	#16142E	Fail
p Creating Experiences…	2.23:1	4.5:1	#000000	#3F4847	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) 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

8 headings

PASS

8 headings

Multiple H1 headings (2 found)

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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

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

Link & Button Quality

23 links, 3 buttons — all OK

PASS

23 links, 3 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://www.instagram.com/manikarnikaa.events/; https://wa.me/919889602261?text=Hello%20Manikarnika%20Events,%20I%20would%20l…; https://www.instagram.com/p/DYZRKgVxmPT/; https://wa.me/919889602261?text=Hello%20Manikarnika%20Events,%20I%20would%20l…; https://www.instagram.com/manikarnikaa.events/

18 link(s) with descriptive text

23 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/manikarnikaa.e…	Instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/919889602261?text=Hello%20…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/p/DYZRKgVxmPT/	Live Concert Footage↗	new tab	Add '(opens in new tab)' to text
https://wa.me/919889602261?text=Hello%20…	Business WhatsApp+91 988960226…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/manikarnikaa.e…	Instagram@manikarnikaa.events	new tab	Add '(opens in new tab)' to text

21 links and buttons have descriptive text

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

https://www.instagram.com/manikarnikaa.events/; https://wa.me/919889602261?text=Hello%20Manikarnika%20Events,%20I%20would%20l…; https://www.instagram.com/p/DYZRKgVxmPT/; https://wa.me/919889602261?text=Hello%20Manikarnika%20Events,%20I%20would%20l…; https://www.instagram.com/manikarnikaa.events/

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

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

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Manikarnika Events - Premier Event Management & Entertainment

192x192 icon present

512x512 icon present

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

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

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 18 passed

PASS

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.

○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

●`[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

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

●Heading elements appear in a sequentially-descending order

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

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