Skip to content
https://skyhigh.cloud

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-bk14at
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://skyhigh.cloud/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://skyhigh.cloud/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Language selected: English" CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI-Powered, Data-Fir…4.29:13.0:1
#000000
#3664F4
Pass
h1 Security Service Edg…4.29:13.0:1
#000000
#3664F4
Pass
h2 Company4.29:13.0:1
#000000
#3664F4
Pass
h2 Products4.29:13.0:1
#000000
#3664F4
Pass
h2 Solutions4.29:13.0:1
#000000
#3664F4
Pass
h2 Resources4.29:13.0:1
#000000
#3664F4
Pass
h3 Interactive Demo - S…4.29:13.0:1
#000000
#3664F4
Pass
h3 Skyhigh Security Cor…4.29:13.0:1
#000000
#3664F4
Pass
h3 Gartner® Magic Quad…4.29:13.0:1
#000000
#3664F4
Pass
h3 Gartner® Critical C…4.29:13.0:1
#000000
#3664F4
Pass
h3 Skyhigh AI4.29:13.0:1
#000000
#3664F4
Pass
h3 Public Sector4.29:13.0:1
#000000
#3664F4
Pass
h3 Skyhigh Security and…4.29:13.0:1
#000000
#3664F4
Pass
h3 Adopt ChatGPT Withou…4.29:13.0:1
#000000
#3664F4
Pass
h3 Custom Tag Managemen…4.29:13.0:1
#000000
#3664F4
Pass
h3 Shareable Dashboards4.29:13.0:1
#000000
#3664F4
Pass
h3 Real-Time Threat Det…4.29:13.0:1
#000000
#3664F4
Pass
h3 Continuous SaaS Moni…4.29:13.0:1
#000000
#3664F4
Pass
h3 MITRE ATT&CK Framewo…4.29:13.0:1
#000000
#3664F4
Pass
h3 Unified CASB Policie…4.29:13.0:1
#000000
#3664F4
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 29 passed
REVIEW
89

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Previous div.elementor-element > div.elementor-element > div#shsCarousel > div#shsLeft
Next div.elementor-element > div.elementor-element > div#shsCarousel > div#shsRight

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ready to Transform Your Security? div.e-con-inner > div.elementor-element > div.elementor-element > p.elementor-heading-title
Reach out to us and join 3,000+ enterprises protecting their companies with Sky… div.elementor-element > div.elementor-element > div.elementor-element > p
Start Demo div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text

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
Skyhigh Stratosphere 2026 Virtual Customer Summit div#shsTrack > div.shsCard > div > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#shsTrack > div.shsCard > div > a div#shsTrack > div.shsCard > div > a
div#shsTrack > div.shsCard > div > a div#shsTrack > div.shsCard > div > a
div#shsTrack > div.shsCard > div > a div#shsTrack > div.shsCard > div > a
div#shsTrack > div.shsCard > div > a div#shsTrack > div.shsCard > div > a
div#shsTrack > div.shsCard > div > a div#shsTrack > div.shsCard > div > a

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.

○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
●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.
●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"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●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
○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.
○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.
A
Heading Hierarchy
28 headings, 1 skip(s)
PASS
28 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Interactive Demo - Skyhigh SSE
  • H3 Skyhigh Security Corporate Brochure
  • H3 Gartner® Magic Quadrant™ Report
  • H3 Gartner® Critical Capabilities
  • H3 Skyhigh AI
  • H3 Public Sector
  • H3 Skyhigh Security and Trellix Data Protection
  • H3 Adopt ChatGPT Without Putting Your Business-Critical Data at Risk
  • H1 AI-Powered, Data-First Security Service Edge
  • H3 Skyhigh Stratosphere 2026 Virtual Customer Summit skipped
  • H3 DSPM Is Shadow IT All Over Again
  • H3 LLM Attributes Every CISO Should Track Today
  • H3 From DPDPA Requirements to Data Visibility: The DSPM Imperative
  • H3 Q4 2025: Sharper Control, Clearer Visibility Across Data & Cloud
  • H2 Company
  • H2 Products
  • H2 Solutions
  • H2 Resources
  • H3 Custom Tag Management
  • H3 Shareable Dashboards
  • H3 Real-Time Threat Detection
  • H3 Continuous SaaS Monitoring
  • H3 MITRE ATT&CK Framework Integration
  • H3 Unified CASB Policies
  • H3 Cloud Data Protection
  • H3 Superior API Coverage
  • H3 DLP Policies & Zero-Trust
  • H3 User Management & Self-Remediation

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+
Alt Text Quality
All 39 images OK
PASS
All 39 images OK
Info::
14 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
39 images 25 good alt text 14 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
ssearchSearcharia-label
ssearchSearcharia-label
#wg69e11cec56bbb1.977517241776360684391checkboxENfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback