Skip to content
https://www.shreekalyan.com/shreekalyan/index

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, email.
Got: <input type="text" name="name">, <input type="email" name="email">
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.
Got: <input type="tel" name="phone">, <input type="email" name="email">
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-a4yua9
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.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.shreekalyan.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.shreekalyan.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

C
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="service">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="tel" name="phone">; <input type="email" name="email">; <textarea name="message">
5 controls
0 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
nametext(Your Name)placeholder only
phonetel(Phone Number)placeholder only
emailemail(Email Address)placeholder only
messagetextarea(Your Project Details)placeholder only
serviceselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="service">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="name">; <input type="tel" name="phone">; <input type="email" name="email">; <textarea name="message">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile-Readable Font Sizes
Action
85% of visible text renders at >= 12 CSS px (26 below threshold)
REVIEW
85% of visible text renders at >= 12 CSS px (26 below threshold)
Warning::
26 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.0px ("Approvals"); <span> 10.0px ("Solar"); <span> 10.0px ("Safety"); <span> 10.0px ("Consultancy"); <span> 10.0px ("Liaisoning").
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 17 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Rajasthan's Leading …8.17:13.0:1
#FFFFFF
#3B5071
Pass
h2 Engineering Excellen…4.33:13.0:1
#000000
#60738D
Pass
h2 Engineering & Consul…4.33:13.0:1
#000000
#60738D
Pass
h2 Trusted Engineering …4.33:13.0:1
#000000
#60738D
Pass
h2 Executive Credential…4.85:13.0:1
#FFFFFF
#60738D
Pass
h2 Serving Diverse Indu…4.33:13.0:1
#000000
#60738D
Pass
h2 Featured Engineering…4.33:13.0:1
#000000
#60738D
Pass
h2 What Our Clients Say4.33:13.0:1
#000000
#60738D
Pass
h2 Latest Articles & Up…4.33:13.0:1
#000000
#60738D
Pass
h2 Need Engineering Con…4.85:13.0:1
#FFFFFF
#60738D
Pass
h3 18+4.33:13.0:1
#000000
#60738D
Pass
h3 560+4.33:13.0:1
#000000
#60738D
Pass
h3 129+4.33:13.0:1
#000000
#60738D
Pass
h3 893+4.33:13.0:1
#000000
#60738D
Pass
h3 98%4.33:13.0:1
#000000
#60738D
Pass
h3 7314.33:13.0:1
#000000
#60738D
Pass
h3 55244.33:13.0:1
#000000
#60738D
Pass
h3 431+4.33:13.0:1
#000000
#60738D
Pass
h3 CEIG Approval Consul…4.33:13.0:1
#000000
#60738D
Pass
h3 PM Surya Ghar Vendor…4.33:13.0:1
#000000
#60738D
Pass

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 80/100 — 5 failing, 17 passed
REVIEW
80

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header-main > nav.navbar > div.container > button.navbar-toggler header.header-main > nav.navbar > div.container > button.navbar-toggler

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select Service CEIG Approval Energy Audit Electrical Safety Audit HT Consumer G… div.cta-form-wrapper > form > div.mb-3 > select.form-select

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.

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
Join Community div.bottom-compact-row > div.bottom-compact-wrapper > div.whatsapp-compact-box > a.wcb-join-btn
© 2026 Shree Kalyan Enterprises. All rights reserved. div.bottom-compact-row > div.footer-bottom > div.container > p
Privacy Policy div.footer-bottom > div.container > div.footer-legal > a
Terms & Conditions div.footer-bottom > div.container > div.footer-legal > a
Disclaimer div.footer-bottom > div.container > div.footer-legal > a
Sitemap div.footer-bottom > div.container > div.footer-legal > a
Made in Rajasthan div.bottom-compact-row > div.footer-bottom > div.container > span.made-in-rajasthan

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
Rajesh Sharma div.testimonial-card-premium > div.testimonial-author > div > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Image elements have `[alt]` attributes
●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
●Touch targets have sufficient size and spacing.
●Identical links have the same purpose.
○`[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-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
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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 Hierarchy
55 headings, 1 skip(s)
PASS
55 headings, 1 skip(s)
Info::
Single H1 present
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 Rajasthan's Leading Electrical Engineering Consultancy & Regulatory Experts
  • H2 Engineering Excellence in Numbers
  • H3 18+
  • H3 560+
  • H3 129+
  • H3 893+
  • H3 98%
  • H3 731
  • H3 5524
  • H3 431+
  • H2 Engineering & Consultancy Services
  • H3 CEIG Approval Consultancy
  • H3 PM Surya Ghar Vendor Reg. & Solar Consultancy
  • H3 Electrical Contractor License Consultancy
  • H3 Electrical Consultancy
  • H3 Government Liaisoning
  • H3 Energy Audit
  • H3 Electrical Safety Audit
  • H3 Fire Safety Audit
  • H3 Electrical Testing & Inspection
  • H3 Third Party Inspection
  • H3 Chartered Engineer Certification
  • H3 Plant Capacity Certificate
  • H2 Trusted Engineering Consultancy
  • H3 BEE Authorised Energy Auditors
  • H3 18+ Years of Engineering Excellence
  • H3 Government Approved & Recognised
  • H3 CEIG Approvals & Regulatory Liaisoning
  • H3 Electrical Consultancy & Compliance
  • H3 1000+ Industrial Consultancy Projects
  • H3 Inspection • Testing • Certification Experts
  • H3 Industrial HT Consumer Grievance Specialists
  • H2 Executive Credentials & Registrations
  • H2 Serving Diverse Industries
  • H2 Featured Engineering Projects
  • H3 252 MW Solar + BESS Project
  • H3 CEIG Approval - Chemical Plant
  • H3 Energy Audit - Textile Plant
  • H3 PM Surya Ghar - 500 kW Rooftop
  • H2 What Our Clients Say
  • H4 Rajesh Sharma skipped
  • H4 Dr. Suresh Mehta
  • H4 Vikram Singh
  • H2 Latest Articles & Updates
  • H3 Key Changes in Rajasthan Rooftop Solar Regulations 2024-2025
  • H3 Case Study: CEIG Approval for 33 kV HT Installation
  • H3 Electricity Consumer Rights in Rajasthan
  • H2 Need Engineering Consultancy or Approval Assistance?
  • H3 Submit Your Enquiry
  • H4 Shree Kalyan Enterprises
  • H5 Our Services
  • H5 Solutions
  • H5 Knowledge Centre
  • H5 Contact Us
  • H4 Join Rajasthan'sElectrical WhatsApp

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

A+
Heading Text Quality
All 55 heading(s) have substantive, well-formed text
PASS
All 55 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
4 image(s) with good alt text
4 images 4 good alt text
All images have appropriate alt text.
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.

Send Feedback