Skip to content
https://vantor.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
6
PASS
14
INFO
0
Checks
24
14 PASS 6 REVIEW 4 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
5 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 5 <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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Heading Hierarchy
Action
34 headings, 3 skip(s)
REVIEW
34 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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 Total clarity from space to ground
  • H2 Vantor gives you the tools to unify your intelligence
  • H6 The Vantor Advantage skipped
  • H5 Own the ground truth with the most trusted intelligence products, fueled by the Vantor imaging constellation
  • H5 Fuse all your sensors across space, air, and ground by anchoring them to an accurate spatial foundation
  • H5 Keep pace with change by automating the intelligence cycle, from tasking and production to fusion and AI-powered analysis
  • H6 Industries We Serve
  • H2 Delivering results for the world’s toughest missions
  • H5 Defense skipped
  • H5 Intelligence
  • H5 Commercial
  • H6 Our Products
  • H2 Fueling every part of the spatial intelligence cycle
  • H4 Gain operational clarity with software that integrates Vantor tasking, content, and platform capabilities skipped
  • H5 Raptor™
  • H5 Sentry™
  • H4 Model and interact with the world at the speed of change
  • H5 Vivid™
  • H5 Vivid™ Mosaic
  • H5 Vivid™ Terrain
  • H5 Vivid™ Features
  • H4 Understand what’s happening anywhere on Earth and in orbit
  • H5 WorldView™
  • H5 WorldView™ 2D
  • H5 WorldView™ Radar
  • H5 WorldView™ Space
  • H5 Access Programs
  • H4 Build your own AI-ready living globe
  • H5 Tensorglobe™ Platform
  • H5 Cortex™
  • H5 Forge™
  • H5 Nexus™
  • H5 The Vantor™ Hub
  • H6 By The numbers

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 ▾

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 ▾

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

B
Alt Text Quality
2 of 14 images have issues
REVIEW
2 of 14 images have issues
Warning::
1 image(s) with filename as alt text
Warning::
1 image(s) with generic alt text
Info::
7 image(s) with alt text over 125 characters
Info::
5 image(s) with good alt text
14 images 5 good alt text 2 generic
IssueCount
filename1 image(s)
generic1 image(s)
too long7 image(s)
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Vantor
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Vantor ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Vantor Display Mode standalone Theme Color #ffffff Background Color #010102 Icons 2 icon(s)
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
h1 Total clarity from space to ground
1.17:1
#000000
on
#171718
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Vantor gives you the tools to unify your…
1.17:1
#000000
on
#171718
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Delivering results for the world’s tou…
1.17:1
#000000
on
#171718
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fueling every part of the spatial intell…
1.17:1
#000000
on
#171718
needs 3.0:1 (large text)
24px · bottom of viewport
title Vantor: Forging the new frontier of spat…
1.10:1
#000000
on
#101011
needs 4.5:1 (normal text)
16px · top of page (header area)
span Products
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · top of page (header area)
span Mission Solutions
1.03:1
#000000
on
#050506
needs 4.5:1 (normal text)
16px · top of page (header area)
span Raptor
1.04:1
#000000
on
#060607
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sentry
1.04:1
#000000
on
#060607
needs 4.5:1 (normal text)
16px · above the fold
span Spatial Intelligence Platform
1.04:1
#000000
on
#070708
needs 4.5:1 (normal text)
16px · above the fold
span Tensorglobe
1.11:1
#000000
on
#111112
needs 4.5:1 (normal text)
16px · above the fold
span Cortex
1.17:1
#000000
on
#171718
needs 4.5:1 (normal text)
16px · above the fold
span Forge
1.17:1
#000000
on
#171718
needs 4.5:1 (normal text)
16px · above the fold
span Nexus
1.19:1
#000000
on
#151921
needs 4.5:1 (normal text)
16px · above the fold
span Hub
1.16:1
#000000
on
#151619
needs 4.5:1 (normal text)
16px · above the fold
span Dynamic Foundation
1.17:1
#000000
on
#1A1618
needs 4.5:1 (normal text)
16px · above the fold
span Vivid
1.10:1
#000000
on
#101012
needs 4.5:1 (normal text)
16px · above the fold
span Mosaic
1.15:1
#000000
on
#141515
needs 4.5:1 (normal text)
16px · mid-page
span Terrain
1.17:1
#000000
on
#171718
needs 4.5:1 (normal text)
16px · mid-page
span Features
1.17:1
#000000
on
#171718
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Total clarity from s…1.17:13.0:1
#000000
#171718
Fail
h2 Vantor gives you the…1.17:13.0:1
#000000
#171718
Fail
h2 Delivering results f…1.17:13.0:1
#000000
#171718
Fail
h2 Fueling every part o…1.17:13.0:1
#000000
#171718
Fail
title Vantor: Forging the …1.10:14.5:1
#000000
#101011
Fail
span Products1.06:14.5:1
#000000
#0A0A0B
Fail
span Mission Solutions1.03:14.5:1
#000000
#050506
Fail
span Raptor1.04:14.5:1
#000000
#060607
Fail
span Sentry1.04:14.5:1
#000000
#060607
Fail
span Spatial Intelligence…1.04:14.5:1
#000000
#070708
Fail
span Tensorglobe1.11:14.5:1
#000000
#111112
Fail
span Cortex1.17:14.5:1
#000000
#171718
Fail
span Forge1.17:14.5:1
#000000
#171718
Fail
span Nexus1.19:14.5:1
#000000
#151921
Fail
span Hub1.16:14.5:1
#000000
#151619
Fail
span Dynamic Foundation1.17:14.5:1
#000000
#1A1618
Fail
span Vivid1.10:14.5:1
#000000
#101012
Fail
span Mosaic1.15:14.5:1
#000000
#141515
Fail
span Terrain1.17:14.5:1
#000000
#171718
Fail
span Features1.17:14.5:1
#000000
#171718
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
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H5: 121 chars
Got: 1 >120-char heading(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
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
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Mobile-Readable Font Sizes
All 112 visible text node(s) render at >= 12 CSS pixels
PASS
All 112 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
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.
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 27 passed
PASS
95

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
of foundational geospatial intelligence used by the U.S. Government is powered … div.stat > div.block-text > div.block-text-col > p
government partners worldwide rely on us when it counts the most. div.stat > div.block-text > div.block-text-col > p
people rely on navigation apps powered by our dynamic foundation. div.stat > div.block-text > div.block-text-col > p
daily collection opportunities of the same location on Earth with the Vantor™ i… div.stat > div.block-text > div.block-text-col > p
sq km of daily high-resolution imagery collection capacity, including 3.5M+ 30 … div.stat > div.block-text > div.block-text-col > p
of the most populous areas mapped in 15 cm and 99% of the world mapped in seaml… div.stat > div.block-text > div.block-text-col > p
sq km of the world mapped in 3D, or 95% of the areas our customers need most. div.stat > div.block-text > div.block-text-col > p

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
The Vantor Advantage div.left > div.block-text > div.block-text-col > h6.text-label
Defense div.image-card > div.card-image > div.mobile-headline-wrapper > h5.headline
Gain operational clarity with software that integrates Vantor tasking, content,… div.section-content > div.block-text > div.block-text-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>`
●`[role]`s have all required `[aria-*]` attributes
●`[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.
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback