https://www.globalmaritimecontainers.com

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 8 REVIEW 8 FIX

Form Accessibility

Action

47 of 47 controls have issues

FIX

47 of 47 controls have issues

46 control(s) without accessible label

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

Got: <input type="text" name="customerName">; <input type="text" name="companyName">; <input type="email" name="email">; <input type="text" name="phone">; <input type="text" name="region">; <input type="text" name="serviceType">; <input type="text" name="equipmentType">; <input type="number" name="quantity">; <input type="text" name="pickupPort">; <textarea name="notes"> (+36 more)

1 control(s) rely on placeholder only

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

Got: <input type="email" name="email">

47 controls

0 labeled

1 placeholder only

46 unlabeled

Control	Type	Label	Method
email	email	(Corporate email...)	placeholder only
customerName	text	(none)	none
companyName	text	(none)	none
email	email	(none)	none
phone	text	(none)	none
region	text	(none)	none
serviceType	text	(none)	none
equipmentType	text	(none)	none
quantity	number	(none)	none
pickupPort	text	(none)	none
notes	textarea	(none)	none
customerName	text	(none)	none
companyName	text	(none)	none
email	email	(none)	none
phone	text	(none)	none
serviceType	text	(none)	none
equipmentType	text	(none)	none
quantity	number	(none)	none
pickupPort	text	(none)	none
destinationPort	text	(none)	none
notes	textarea	(none)	none
email	email	(none)	none
containerId	text	(none)	none
transporterName	text	(none)	none
driverName	text	(none)	none
fullName	text	(none)	none
companyName	text	(none)	none
email	email	(none)	none
phone	text	(none)	none
password	password	(none)	none
containerId	text	(none)	none
name	text	(none)	none
type	text	(none)	none
location	text	(none)	none
rentalRate	number	(none)	none
jobId	text	(none)	none
jobTitle	text	(none)	none
department	text	(none)	none
applicantName	text	(none)	none
applicantEmail	email	(none)	none
applicantPhone	text	(none)	none
applicantCity	text	(none)	none
applicantExperience	text	(none)	none
applicantResumeUrl	text	(none)	none
applicantCoverNote	textarea	(none)	none
refCode	text	(none)	none
submittedAt	text	(none)	none

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

<input type="text" name="customerName">; <input type="text" name="companyName">; <input type="email" name="email">; <input type="text" name="phone">; <input type="text" name="region">; <input type="text" name="serviceType">; <input type="text" name="equipmentType">; <input type="number" name="quantity">; <input type="text" name="pickupPort">; <textarea name="notes"> (+36 more)

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.

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

Mobile Keyboard & Autofill

Action

16/16 eligible field(s) missing autocomplete or inputmode

FIX

16/16 eligible field(s) missing autocomplete or inputmode

7 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: email, current-password, name.

Got: <input type="email" name="email">, <input type="email" name="email">, <input type="email" name="email">, <input type="email" name="email">, <input type="email" name="email">

9 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: email, numeric.

Got: <input type="email" name="email">, <input type="email" name="email">, <input type="number" name="quantity">, <input type="email" name="email">, <input type="number" name="quantity">

Mobile-Readable Font Sizes

Action

64% of visible text renders at >= 12 CSS px (89 below threshold)

FIX

64% of visible text renders at >= 12 CSS px (89 below threshold)

89 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: <p> 11.0px ("Dubai HQ & India Commercial Facilitation..."); <span> 11.0px ("CLIENT BUYS CONTAINERS & LEASES BACK TO ..."); <span> 11.0px ("GMC ACTS SOLELY AS COMMERCIAL FACILITATO..."); <span> 11.0px ("FIXED GUARANTEED MONTHLY RENTAL PAYOUTS"); <span> 11.0px ("100% CLIENT ASSET OWNERSHIP & LEGAL SECU...").

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-82xyl0

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://www.globalmaritimecontainers.com/manifest.json

Manifest contains invalid JSON.

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: #07162c

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.

Heading Hierarchy

40 headings, 2 skip(s)

REVIEW

40 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 Your Container Our CommitmentYou earn →GUARANTEED RENTALS
H2 HOW IT WORKS
H3 YOU OWN
H3 YOU HAND IT TO US
H3 WE LEASE GLOBALLY
H3 YOU EARN
H2 WHY IT WORKS FOR YOU
H3 PASSIVE INCOME
H3 GLOBAL REACH
H3 MANAGED BY EXPERTS
H3 GROWING DEMAND
H3 SECURE & RELIABLE
H2 Explore Container Categories
H3 Dry Freight Containers
H3 Refrigerated Reefers
H3 Dry Freight Specials
H3 Double Door Units
H2 Connecting Global Container Assets Across Dubai & India
H4 100% Asset Ownership skipped
H4 Fixed Commercial Returns
H2 Container Specifications & Availability
H3 20ft Standard Dry hc Container
H2 Global Container Asset Leasing& Management Program
H2 Verified Client Reviews & Testimonials
H4 Dr. Anita Desai skipped
H4 Captain Khalid Al-Hassani
H4 Sunil Mehta
H4 Share Your Review
H2 Frequently Asked Questions
H2 WATCH GMC OPERATIONS IN ACTION
H3 GMC Fleet Operations & Container Logistics
H3 GMC Cold Chain & Container Depot Operations
H2 Industry Analysis & Executive Blog
H3 Understanding the Commercial Container Leaseback Program
H3 Cold Chain Excellence: How IoT Telemetry & PTI Testing Prevent Spoilage
H3 ISO Container Selection Guide: 20ft vs 40ft High Cube vs Double Door Units
H4 Container Catalog
H4 Navigation & Program
H4 Corporate Offices
H5 Subscribe to Program Updates

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

Link & Button Quality

Action

4 issue(s) across 19 links and 68 buttons

REVIEW

4 issue(s) across 19 links and 68 buttons

15 link(s) open in new tab without warning

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

Got: https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B; https://www.linkedin.com/in/global-containers-5ab5ba42b?utm_source=share_via&…; https://www.instagram.com/globalmaritimecontainers/; https://wa.me/971585797023?text=Hello%20GMC%20Operations,%20I%20need%20a%20co…; https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B; https://www.instagram.com/globalmaritimecontainers/; https://www.linkedin.com/in/global-containers-5ab5ba42b?utm_source=share_via&…; https://www.instagram.com/reel/Db1U1QStG8A/; https://www.instagram.com/reel/DbsLEtht85P/; https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B (+5 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.p-2 (#153 on page); button.w-16 (#831 on page); button.w-16 (#857 on page); button.btn-seaco-emerald (#1059 on page)

4 link(s) with descriptive text

19 links

0 empty

0 generic text

15 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://youtube.com/@best_container_leas…	Official YouTube Channel (@bes…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/global-conta…	Official LinkedIn Profile (Glo…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/globalmaritime…	Official Instagram @globalmari…	new tab	Add '(opens in new tab)' to text
https://wa.me/971585797023?text=Hello%20…	WhatsApp Dispatch Desk	new tab	Add '(opens in new tab)' to text
https://youtube.com/@best_container_leas…	YOUTUBE CHANNEL	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/globalmaritime…	INSTAGRAM	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/global-conta…	LINKEDIN	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/reel/Db1U1QStG…	VIEW ON INSTAGRAM	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/reel/DbsLEtht8…	VIEW ON INSTAGRAM	new tab	Add '(opens in new tab)' to text
https://youtube.com/@best_container_leas…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/global-conta…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/globalmaritime…	Instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/971585797023?text=Hello%20…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://kashipixel.in/	Gurudeep Verma	new tab	Add '(opens in new tab)' to text
https://wa.me/919681237921?text=Hello%20…	Direct WhatsApp Message to GMC…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

68 links and buttons have descriptive text

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

https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B; https://www.linkedin.com/in/global-containers-5ab5ba42b?utm_source=share_via&…; https://www.instagram.com/globalmaritimecontainers/; https://wa.me/971585797023?text=Hello%20GMC%20Operations,%20I%20need%20a%20co…; https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B; https://www.instagram.com/globalmaritimecontainers/; https://www.linkedin.com/in/global-containers-5ab5ba42b?utm_source=share_via&…; https://www.instagram.com/reel/Db1U1QStG8A/; https://www.instagram.com/reel/DbsLEtht85P/; https://youtube.com/@best_container_leasing_company?si=cIj23prnZDMOjy3B (+5 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.p-2 (#153 on page); button.w-16 (#831 on page); button.w-16 (#857 on page); button.btn-seaco-emerald (#1059 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Form Input Types

4 input(s) using type=text where a specific type would help

REVIEW

4 input(s) using type=text where a specific type would help

Input "phone" should use type="tel" (currently type="text")

Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

Input "phone" should use type="tel" (currently type="text")

Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

Input "phone" should use type="tel" (currently type="text")

Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

Input "applicantPhone" should use type="tel" (currently type="text")

Field name "applicantPhone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

Form Input Quality

2 input-semantic issue(s) across 47 form control(s)

REVIEW

2 input-semantic issue(s) across 47 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password">.

6 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="email">, <input type="email" name="email">, <input type="email" name="email"> (+3 more).

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 HOW IT WORKS

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WHY IT WORKS FOR YOU

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Explore Container Categories

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connecting Global Container Assets Acros…

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Container Specifications & Availability

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Global Container Asset Leasing

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 & Management Program

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Verified Client Reviews & Testimonials

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WATCH GMC OPERATIONS IN ACTION

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Industry Analysis & Executive Blog

1.17:1

#000000

#031928

needs 3.0:1 (large text)

24px · bottom of viewport

h3 YOU OWN

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YOU HAND IT TO US

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 WE LEASE GLOBALLY

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YOU EARN

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 PASSIVE INCOME

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 GLOBAL REACH

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 MANAGED BY EXPERTS

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 GROWING DEMAND

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SECURE & RELIABLE

1.17:1

#000000

#031928

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 HOW IT WORKS	1.17:1	3.0:1	#000000	#031928	Fail
h2 WHY IT WORKS FOR YOU	1.17:1	3.0:1	#000000	#031928	Fail
h2 Explore Container Ca…	1.17:1	3.0:1	#000000	#031928	Fail
h2 Connecting Global Co…	1.17:1	3.0:1	#000000	#031928	Fail
h2 Container Specificat…	1.17:1	3.0:1	#000000	#031928	Fail
h2 Global Container Ass…	1.17:1	3.0:1	#000000	#031928	Fail
h2 & Management Program	1.17:1	3.0:1	#000000	#031928	Fail
h2 Verified Client Revi…	1.17:1	3.0:1	#000000	#031928	Fail
h2 Frequently Asked Que…	1.17:1	3.0:1	#000000	#031928	Fail
h2 WATCH GMC OPERATIONS…	1.17:1	3.0:1	#000000	#031928	Fail
h2 Industry Analysis & …	1.17:1	3.0:1	#000000	#031928	Fail
h3 YOU OWN	1.17:1	3.0:1	#000000	#031928	Fail
h3 YOU HAND IT TO US	1.17:1	3.0:1	#000000	#031928	Fail
h3 WE LEASE GLOBALLY	1.17:1	3.0:1	#000000	#031928	Fail
h3 YOU EARN	1.17:1	3.0:1	#000000	#031928	Fail
h3 PASSIVE INCOME	1.17:1	3.0:1	#000000	#031928	Fail
h3 GLOBAL REACH	1.17:1	3.0:1	#000000	#031928	Fail
h3 MANAGED BY EXPERTS	1.17:1	3.0:1	#000000	#031928	Fail
h3 GROWING DEMAND	1.17:1	3.0:1	#000000	#031928	Fail
h3 SECURE & RELIABLE	1.17:1	3.0:1	#000000	#031928	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 19 passed

REVIEW

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
div.group > div.h-64 > div.absolute > button.w-16 `div.group > div.h-64 > div.absolute > button.w-16`
div.group > div.h-64 > div.absolute > button.w-16 `div.group > div.h-64 > div.absolute > button.w-16`
div.lg:col-span-3 > div.pt-2 > form.flex > button.btn-seaco-emerald `div.lg:col-span-3 > div.pt-2 > form.flex > button.btn-seaco-emerald`

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.

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
100% ASSET OWNERSHIP `div.scroll-reveal-item > div.bg-slate-900/90 > div.flex > h4.font-heading`
DR. ANITA DESAI `div.scroll-reveal-item > div.bg-slate-950/80 > div.pt-4 > h4.font-heading`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Slide 2 `div.relative > div.w-full > div.flex > button.rounded-full`
Slide 3 `div.relative > div.w-full > div.flex > button.rounded-full`
Slide 4 `div.relative > div.w-full > div.flex > button.rounded-full`
+91 79058 08199 `footer.bg-[#07162c] > div.w-full > div.mt-6 > a.text-slate-300`

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

●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 are distinguishable without relying on color.

●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

●Document has a main landmark.

●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

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

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

Landmark Structure

5 landmarks

PASS

5 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

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

14 image(s) with good alt text

14 images 14 good alt text

All images have appropriate alt text.

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+

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.

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