Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 21 -1-on-focusable

FIX

0 positive, 21 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t1">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t2">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t3">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t4">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t5">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t6">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="apjx0o-t7">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t1">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t2">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t3">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t4">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t5">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="ixqq4f-t6">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 7 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

C

Mobile-Readable Font Sizes

Action

78% of visible text renders at >= 12 CSS px (37 below threshold)

REVIEW

78% of visible text renders at >= 12 CSS px (37 below threshold)

37 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: <b> 8.0px ("Shipment Tracking"); <b> 8.0px ("Transportation"); <b> 8.0px ("Customs Clearance"); <b> 8.0px ("Freight Management"); <b> 8.0px ("Warehouse (WMS)").

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | NXT Orbit ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #001824 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

h2 Grow Your Business. Not Your Complexity.

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One connected flow, from booking to deli…

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One Platform. Nine Products.

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI That Drives Real Business Impact

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How We Deliver

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Industry knowledge that sharpens every b…

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Knowledge That Drives Better Business De…

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to Transform Your Business?

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We value your privacy

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Disconnected systems

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Manual Processes

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Limited Visibility

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Legacy Technology

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Step 1: Freight Management System

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shipment Tracking

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Freight Management System

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shipment Tracking

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Customs Clearance

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Transportation Management

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Warehouse Management System (WMS)

1.14:1

#000000

on

#001621

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Grow Your Business. …	1.14:1	3.0:1	#000000	#001621	Fail
h2 One connected flow, …	1.14:1	3.0:1	#000000	#001621	Fail
h2 One Platform. Nine P…	1.14:1	3.0:1	#000000	#001621	Fail
h2 AI That Drives Real …	1.14:1	3.0:1	#000000	#001621	Fail
h2 How We Deliver	1.14:1	3.0:1	#000000	#001621	Fail
h2 Industry knowledge t…	1.14:1	3.0:1	#000000	#001621	Fail
h2 Knowledge That Drive…	1.14:1	3.0:1	#000000	#001621	Fail
h2 Ready to Transform Y…	1.14:1	3.0:1	#000000	#001621	Fail
h2 We value your privac…	1.14:1	3.0:1	#000000	#001621	Fail
h3 Disconnected systems	1.14:1	3.0:1	#000000	#001621	Fail
h3 Manual Processes	1.14:1	3.0:1	#000000	#001621	Fail
h3 Limited Visibility	1.14:1	3.0:1	#000000	#001621	Fail
h3 Legacy Technology	1.14:1	3.0:1	#000000	#001621	Fail
h3 Step 1: Freight Mana…	1.14:1	3.0:1	#000000	#001621	Fail
h3 Shipment Tracking	1.14:1	3.0:1	#000000	#001621	Fail
h3 Freight Management S…	1.14:1	3.0:1	#000000	#001621	Fail
h3 Shipment Tracking	1.14:1	3.0:1	#000000	#001621	Fail
h3 Customs Clearance	1.14:1	3.0:1	#000000	#001621	Fail
h3 Transportation Manag…	1.14:1	3.0:1	#000000	#001621	Fail
h3 Warehouse Management…	1.14:1	3.0:1	#000000	#001621	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.

A

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A

Heading Hierarchy

41 headings, 1 skip(s)

PASS

41 headings, 1 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.

H1 TurningComplexBusinessOperationsintoConnectedEnterpriseSystems.
H2 Grow Your Business. Not Your Complexity.
H3 Disconnected systems
H3 Manual Processes
H3 Limited Visibility
H3 Legacy Technology
H2 One connected flow, from booking to delivery
H3 Step 1: Freight Management System → Shipment Tracking
H2 One Platform. Nine Products.
H3 Freight Management System
H3 Shipment Tracking
H3 Customs Clearance
H3 Transportation Management
H3 Warehouse Management System (WMS)
H3 Material Tracking System (MTS)
H3 Manufacturing Execution Solution (MES)
H3 Courier Express
H3 Integrated Sales, Finance & HRM
H2 AI That Drives Real Business Impact
H3 Operations copilots
H2 How We Deliver
H3 Discovery
H3 Architecture & Design
H3 Development & Implementation
H3 Deployment & Continuous Improvement
H2 Industry knowledge that sharpens every build
H3 Shop-floor execution, BOM accuracy and plant systems built for production realities.
H2 Knowledge That Drives Better Business Decisions
H3 From Manual Processes to Intelligent Operations
H3 Cutting Return-to-Origin Losses in E-Commerce
H3 Seeing Job Margin Before You Invoice
H2 Ready to Transform Your Business?
H4 Products skipped
H4 Products
H4 Industries
H4 Industries
H4 Services
H4 Services
H4 Company
H4 Company
H2 We value your privacy

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 41 heading(s) have substantive, well-formed text

PASS

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

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

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

2 decorative image(s) correctly marked

5 image(s) with good alt text

7 images 5 good alt text 2 decorative

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

100 links, 51 buttons — all OK

PASS

100 links, 51 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://www.linkedin.com/company/nxt-orbit-it-solutions-pvt-ltd

99 link(s) with descriptive text

100 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	NXTorbit home	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/nxt-orb…	linkedin	new tab	Add '(opens in new tab)' to text

150 links and buttons have descriptive text

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

https://www.linkedin.com/company/nxt-orbit-it-solutions-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+

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+

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 passed

PASS

100

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.

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

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

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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