Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

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-5aisu6

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://inspireinfosol.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://inspireinfosol.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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.

Heading Hierarchy

26 headings, 2 skip(s)

REVIEW

26 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 We transform how industries run
H2 Seven industry groups · Equal depth
H4 Travel, aviation & transportation skipped
H4 Retail, commerce & consumer
H4 Financial services & fintech
H4 Manufacturing & industrial
H4 Healthcare & life sciences
H4 Education
H4 Government & public sector
H2 Six capabilities One engineering standard
H3 AI & Data Engineering
H3 Application Modernisation
H3 Cloud Transformation
H3 Customer Experience & Commerce
H3 Product Engineering
H3 Enterprise Systems (CRM & ERP)
H2 Built different · Proven in production
H3 Product engineers, not just consultants
H3 Delivery in weeks, not quarters
H3 Compliance-first architecture
H3 India-engineered, globally trusted
H2 Ready to build something exceptional?
H4 What we do skipped
H4 Industries
H4 Company
H4 Connect

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 We transform how industries run

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

32px · mid-page

h2 Seven industry groups · Equal depth

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Six capabilities

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One engineering standard

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built different · Proven in production

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to build something exceptional?

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

24px · bottom of viewport

h3 AI & Data Engineering

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Application Modernisation

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cloud Transformation

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Customer Experience & Commerce

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Product Engineering

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enterprise Systems (CRM & ERP)

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Product engineers, not just consultants

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Delivery in weeks, not quarters

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Compliance-first architecture

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

h3 India-engineered, globally trusted

1.15:1

#000000

#0D1526

needs 3.0:1 (large text)

19px · bottom of viewport

title Inspire Infosol | Engineering excellence…

1.29:1

#000000

#1B202C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Solutions

1.29:1

#000000

#1B202C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Services

1.17:1

#000000

#0C1728

needs 4.5:1 (normal text)

16px · top of page (header area)

a Industries

1.17:1

#000000

#0D1729

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 We transform how ind…	1.15:1	3.0:1	#000000	#0D1526	Fail
h2 Seven industry group…	1.15:1	3.0:1	#000000	#0D1526	Fail
h2 Six capabilities	1.15:1	3.0:1	#000000	#0D1526	Fail
h2 One engineering stan…	1.15:1	3.0:1	#000000	#0D1526	Fail
h2 Built different · P…	1.15:1	3.0:1	#000000	#0D1526	Fail
h2 Ready to build somet…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 AI & Data Engineerin…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Application Modernis…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Cloud Transformation	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Customer Experience …	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Product Engineering	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Enterprise Systems (…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Product engineers, n…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Delivery in weeks, n…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 Compliance-first arc…	1.15:1	3.0:1	#000000	#0D1526	Fail
h3 India-engineered, gl…	1.15:1	3.0:1	#000000	#0D1526	Fail
title Inspire Infosol \| En…	1.29:1	4.5:1	#000000	#1B202C	Fail
a Solutions	1.29:1	4.5:1	#000000	#1B202C	Fail
a Services	1.17:1	4.5:1	#000000	#0C1728	Fail
a Industries	1.17:1	4.5:1	#000000	#0D1729	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

A+

Heading Text Quality

All 26 heading(s) have substantive, well-formed text

PASS

All 26 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 37 images OK

PASS

All 37 images OK

37 image(s) with good alt text

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

A+

Link & Button Quality

48 links, 1 buttons — all OK

PASS

48 links, 1 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://in.linkedin.com/company/inspire-infosol-pvt-ltd

47 link(s) with descriptive text

48 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://in.linkedin.com/company/inspire-…	LinkedIn	new tab	Add '(opens in new tab)' to text

48 links and buttons have descriptive text

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

https://in.linkedin.com/company/inspire-infosol-pvt-ltd

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+

Mobile-Readable Font Sizes

All 151 visible text node(s) render at >= 12 CSS pixels

PASS

All 151 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

Lighthouse Accessibility Audits

Score 93/100 — 2 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
ENGINEERING EXCELLENCE · INDUSTRY DEPTH · GLOBAL DELIVERY `app-home > section.hero > div.hero-content > p.hero-badge`
Explore our work `section.hero > div.hero-content > div.hero-actions > a.btn`
India · GCC · EU · APAC · Americas `app-home > section.stats-bar > div.container > p.region-badges`
We work with the stack you already run. `app-home > section.tech-strip > div.container > p.tech-note`
Book a discovery call → `section.cta-banner > div.container > div.actions > a.btn`

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
Travel, aviation & transportation `div.container > div.industry-grid > a.industry-card > h4`
WHAT WE DO `div.container > div.footer-grid > div.footer-col > h4`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Document has a main landmark.

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

○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

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

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