Skip to content
https://gminsights.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
Back-to-top link detected
Info::
1 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 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
3 landmarks
REVIEW
3 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!) 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

C
Form Accessibility
Action
8 of 8 controls have issues
REVIEW
8 of 8 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="category_name">
Warning::
7 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input name="name">; <input type="email" name="business_email">; <input type="number" name="phone">; <textarea name="message">; <input type="search" name="q">; <input type="search" name="q">
8 controls
0 labeled
7 placeholder only
1 unlabeled
ControlTypeLabelMethod
qsearch(Search Reports)placeholder only
nameinput(Full Name*)placeholder only
business_emailemail(Business Email*)placeholder only
phonenumber(Phone*)placeholder only
messagetextarea(Research Requirements)placeholder only
qsearch(Search Reports)placeholder only
qsearch(Search Reports)placeholder only
category_nameselect(none)none

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

<select name="category_name">

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.

<input type="search" name="q">; <input name="name">; <input type="email" name="business_email">; <input type="number" name="phone">; <textarea name="message">; <input type="search" name="q">; <input type="search" name="q">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Insights built by humans who know the ma…
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Start Your
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Today
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Clients
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Our Clients Say
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cited by Leading Publication
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Browse Industry Reports
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recent Reports
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Services
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Industry Reports
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Off-the-rack research
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Research Subscription Practice
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Consulting Practice
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Technology Consulting
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Growth Consulting
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Custom Research
1.30:1
#074C65
on
#27364C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Trusted By Leading Publications
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Request Your Trial
1.72:1
#000000
on
#27364C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Insights built by hu…1.72:13.0:1
#000000
#27364C
Fail
h2 Start Your1.72:13.0:1
#000000
#27364C
Fail
h2 Today1.72:13.0:1
#000000
#27364C
Fail
h2 Our Clients1.72:13.0:1
#000000
#27364C
Fail
h2 What Our Clients Say1.72:13.0:1
#000000
#27364C
Fail
h2 Cited by Leading Pub…1.72:13.0:1
#000000
#27364C
Fail
h2 Browse Industry Repo…1.72:13.0:1
#000000
#27364C
Fail
h2 Recent Reports1.72:13.0:1
#000000
#27364C
Fail
h2 Our Services1.72:13.0:1
#000000
#27364C
Fail
h2 Industry Reports1.30:13.0:1
#074C65
#27364C
Fail
h2 Off-the-rack researc…1.30:13.0:1
#074C65
#27364C
Fail
h2 Research Subscriptio…1.30:13.0:1
#074C65
#27364C
Fail
h2 Consulting Practice1.30:13.0:1
#074C65
#27364C
Fail
h2 Technology Consultin…1.30:13.0:1
#074C65
#27364C
Fail
h2 Growth Consulting1.30:13.0:1
#074C65
#27364C
Fail
h2 Custom Research1.30:13.0:1
#074C65
#27364C
Fail
h3 Trusted By Leading P…1.72:13.0:1
#000000
#27364C
Fail
h3 Request Your Trial1.72:13.0:1
#000000
#27364C
Fail
title Global Market Insigh…21.00:14.5:1
#000000
#FFFFFF
Pass
span Industry Reports21.00:14.5:1
#000000
#FFFFFF
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 86/100 — 4 failing, 24 passed
REVIEW
86

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.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn

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.

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
Published: April 2026 div.image_box > div.authour_details > p > a
Published: April 2026 div.image_box > div.authour_details > p > a
Published: April 2026 div.image_box > div.authour_details > p > a
Explore All Reports div.row > div > a > div.search-button
Privacy Policy div#page > div.CookieConsent > div > 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
Yutaka Hosoyamada div.card-body > div.d-flex > div > h6.mb-0

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
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn

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
●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
●`[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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○Elements with `role="dialog"` or `role="alertdialog"` 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
○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
○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
26 headings, 1 skip(s)
PASS
26 headings, 1 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.
  • H2 Start Your 7-Days Trial Today
  • H3 Trusted By Leading Publications
  • H3 Request Your Trial
  • H1 Insights built by humans who know the market
  • H2 Our Clients
  • H2 What Our Clients Say
  • H6 Yutaka Hosoyamada skipped
  • H6 Jeff Hastings
  • H6 Heather Kirkpatrick
  • H6 Takehiko Fushimi
  • H6 Reo Yamawaki
  • H6 Kazuya Mizumoto
  • H2 Cited by Leading Publication
  • H2 Browse Industry Reports
  • H2 Recent Reports
  • H2 Blowing Torch Market 220 Pages
  • H2 North America Pressure Control Equipment Market 220 Pages
  • H2 Educational Toys Market 210 Pages
  • H2 Our Services
  • H2 Industry Reports
  • H2 Off-the-rack research
  • H2 Research Subscription Practice
  • H2 Consulting Practice
  • H2 Technology Consulting
  • H2 Growth Consulting
  • H2 Custom Research

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 75 images OK
PASS
All 75 images OK
Info::
75 image(s) with good alt text
75 images 75 good alt text
All images have appropriate alt text.
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 ✓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