Skip to content
https://gigaom.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Landmark Structure
23 landmarks
REVIEW
23 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
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main-nav-label" MAIN (missing!) 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

B
Heading Hierarchy
53 headings, 2 skip(s)
REVIEW
53 headings, 2 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.
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 Create a Free GigaOm Account, or Sign in
  • H3 Featured Insights skipped
  • H4 blog
  • H4 Data, Analytics & AI
  • H3 GigaOm Analysts on: The Rise of Constrained Autonomy
  • H4 The Forces Driving AI’s Structural Shift
  • H4 blog
  • H4 Data, Analytics & AI
  • H3 It’s All About the Data Platform: Learning Lessons from Motorsport
  • H4 Availability, Accessibility, Usability and Resilience
  • H4 video
  • H3 Business Disruptions in Tech with Kavitha Mariappan
  • H4 CxO Decision Brief
  • H4 Security & Risk
  • H3 CxO Decision Brief: Data Security Posture Management - Theom
  • H4 Theom delivers embedded data governance with real-time, query-layer visibility and AI-driven security controls for comprehensive data and AI risk management.
  • H3 Most Popular
  • H3 GigaOm Radar for Attack Surface Management
  • H3 GigaOm Radar for XDR
  • H3 GigaOm Radar for Enterprise Firewalls
  • H3 GigaOm Radar for Deception Technology
  • H3 Get the scoop on what's new
  • H3 Our Latest Research Sign Up For Free
  • H3 GigaOm Radar for AI Infrastructure
  • H3 GigaOm Radar for Network Observability
  • H3 GigaOm Radar for Security Service Edge (SSE)
  • H3 GigaOm Radar for Data Security Posture Management (DSPM)
  • H3 GigaOm Radar for XDR
  • H3 GigaOm Radar for Streaming Data Platforms
  • H3 Looking for a research category?
  • H3 Anticipate. Accelerate. Innovate.
  • H3 Tools and Services That Power Decisions
  • H3 Advisory
  • H4 Innovate at the speed of the market
  • H3 Research Subscription
  • H4 Upskill yourself, and your team
  • H3 Webinars
  • H4 Grasp new technologies and market solutions
  • H3 GigaOm Key Criteria Report
  • H4 Gain detailed insight into mission-critical solutions
  • H3 GigaOm Radar Report
  • H4 Enable faster decision making
  • H3 GigaOm Benchmark Report
  • H4 Make confident decisions with hard evidence
  • H3 Why GigaOm? See Our Case Studies
  • H3 Helping Practitioners and Vendors Get Ahead of the Market
  • H2 Leading Enterprise customers worldwide rely on GigaOm. Join them.
  • H4 Subscribe to our monthly analyst insights newsletter skipped
  • H4 Research
  • H4 For Vendors
  • H4 Insights
  • H4 Company
  • H4 Privacy Overview

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
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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title Home - Gigaom
1.26:1
#000000
on
#1C1E21
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.26:1
#000000
on
#1C1E21
needs 4.5:1 (normal text)
16px · top of page (header area)
a Gigaom
3.76:1
#000000
on
#006BB4
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Create a Free GigaOm…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leading Enterprise c…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured Insights21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Most Popular21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get the scoop on wha…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Our Latest Research21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Looking for a resear…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tools and Services T…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Advisory21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Research Subscriptio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Webinars21.00:13.0:1
#000000
#FFFFFF
Pass
h3 GigaOm Key Criteria …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 GigaOm Radar Report21.00:13.0:1
#000000
#FFFFFF
Pass
h3 GigaOm Benchmark Rep…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Why GigaOm?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Helping Practitioner…21.00:13.0:1
#000000
#FFFFFF
Pass
title Home - Gigaom1.26:14.5:1
#000000
#1C1E21
Fail
a Skip to content1.26:14.5:1
#000000
#1C1E21
Fail
span Main Navigation7.12:14.5:1
#000000
#009BFE
Pass
a Gigaom3.76:14.5:1
#000000
#006BB4
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 26 passed
REVIEW
85

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
Microsoft div.container > div.row > div.col > div.brand
Bank of America div.container > div.row > div.col > div.brand
DataStax div.container > div.row > div.col > div.brand
Kong div.container > div.row > div.col > div.brand
Cohesity div.container > div.row > div.col > div.brand
Confluent div.container > div.row > div.col > div.brand
Progressive div.container > div.row > div.col > div.brand
Nginx div.container > div.row > div.col > div.brand
Paloalto div.container > div.row > div.col > div.brand
ADP div.container > div.row > div.col > div.brand
CISO Series div.col-lg-10 > div.row > div.col > div.partner
CRN div.col-lg-10 > div.row > div.col > div.partner
A Cloud Guru div.col-lg-10 > div.row > div.col > div.partner
The Register div.col-lg-10 > div.row > div.col > div.partner
SDX Central div.col-lg-10 > div.row > div.col > div.partner
Pluralsight div.col-lg-10 > div.row > div.col > div.partner

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
CONTINUE div.column > div.form-container > form.form > button.w-100
Jon Collins article.row > div.col-md-6 > div.meta > span.author
READ MORE article.row > div.col-md-6 > div.entry-content > a.read-more-button
Jon Collins article.row > div.col-md-6 > div.meta > span.author
READ MORE article.row > div.col-md-6 > div.entry-content > a.read-more-button
Howard Holton article.row > div.col-md-6 > div.meta > span.author
WATCH NOW article.row > div.col-md-6 > div.entry-content > a.read-more-button
Howard Holton article.row > div.col-md-6 > div.meta > span.author
READ MORE article.row > div.col-md-6 > div.entry-content > a.read-more-button
Chris Ray, Whit Walters article#post-971548 > header.entry-header > div.meta > span.author
Feb 26, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Chris Ray article#post-971548 > header.entry-header > div.meta > span.author
Apr 9, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Paul Stringfellow article#post-971548 > header.entry-header > div.meta > span.author
Mar 5, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Stan Wisseman article#post-971548 > header.entry-header > div.meta > span.author
Feb 18, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Get the scoop on what's new div.col-xl-3 > div.scoop-cta > div.container > h3
Subscribe to get the latest GigaOm blogs, guides and industry insight. div.col-xl-3 > div.scoop-cta > div.container > p
SUBSCRIBE NOW div.col-xl-3 > div.scoop-cta > div.container > a.btn
SIGN UP FOR FREE div.row > div.col > h3.heading > a.btn
James Brown article#post-971548 > header.entry-header > div.meta > span.author
Apr 14, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Andrew Green article#post-971548 > header.entry-header > div.meta > span.author
Apr 13, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Ivan McPhee article#post-971548 > header.entry-header > div.meta > span.author
Apr 13, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Paul Stringfellow article#post-971548 > header.entry-header > div.meta > span.author
Apr 13, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Chris Ray article#post-971548 > header.entry-header > div.meta > span.author
Apr 9, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
Andrew J. Brust, Jelani Harper article#post-971548 > header.entry-header > div.meta > span.author
Apr 9, 2026 article#post-971548 > header.entry-header > div.meta > time.entry-date
MEDIA PARTNERS div.container > div.row > div.col-lg-2 > span.partners-heading
SIGN UP FOR FREE div.container > div.row > div.col > a.cta-button
SUBSCRIBE NOW footer#colophon > div.row > div.col-md-4 > a#footer-cta-button
Privacy Policy div#cookie-law-info-bar > div.cli-wrapper > span#wt-cli-cookie-banner > a

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
Featured Insights div.container > div.row > div.col > h3.heading
Subscribe to our monthly analyst insights newsletter footer#colophon > div.row > div.col-md-4 > h4

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.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay
div.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay
div.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay
div.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay
div.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay
div.container > div.row > div.col-lg-6 > a.overlay div.container > div.row > div.col-lg-6 > a.overlay

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.

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
Search header#wrapper-navbar > nav#main-nav > div.container > a.search-button
Patrick McMorran, FCP Euro VP of Technology Strategy & Operations div.row > div#brands-testimonial-carousel > div.carousel-indicators > button.active
Ishan Mukherjee, New Relic SVP of Marketing div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Jon Bratseth, CEO and Founder, Vespa div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Atul Deshpande, Principal Solutions Architect, RedHat div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Lightlytics div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Large Energy Company div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Minio div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Hitachi div.row > div#brands-testimonial-carousel > div.carousel-indicators > button
Large Insurance Company div.row > div#brands-testimonial-carousel > div.carousel-indicators > button

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>`
`[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
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.
`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
`<frame>` or `<iframe>` elements have a title
`<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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
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
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
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.
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.
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.
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
26 image(s) with good alt text
26 images 26 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearchSearcharia-label
#wt-cli-checkbox-necessarycheckboxNecessaryaria-label
emailemail(i.e. john@mail.com)placeholder only

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

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

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

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found - Gigaom Custom Styling Navigation Homepage Link Search Form
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback