Skip to content
https://influencermarketinghub.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Heading Hierarchy
Action
38 headings, 3 skip(s)
FIX
38 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (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.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Stay Ahead of the Influencer Marketing Movement
  • H2 Influencer Marketing Benchmark Report 2026
  • H3 Top Influencer Marketing Agencies in 2026
  • H3 How to Run an Influencer Audit: Metrics and Tools Marketers Use
  • H3 Top 22 Social Media Tools You Need in Your Marketing Arsenal
  • H3 Content Marketing: The Missing Long-Term Strategy for Amazon Sellers
  • H3 Best AI Agents for Influencer Marketing in 2026
  • H3 MoDash
  • H3 The Most Overlooked Asset in Your Influencer Program Is the Content Itself
  • H3 How Influencer Marketing Shapes Brand Perception in Competitive Markets
  • H3 Measuring Brand Perception Before and After a Campaign
  • H2 Explore Marketing Trends
  • H4 By social network skipped
  • H4 By Industry
  • H4 By content type
  • H3 Brandwatch
  • H2 Find the Team and Tools to Power Your Campaigns
  • H4 Agencies skipped
  • H4 Platforms & Software
  • H3 Trending Agencies
  • H3 Trending Platforms
  • H3 Marketing Tools & Calculators
  • H3 Instagram Sponsored Post Calculator
  • H3 TikTok Money Calculator
  • H3 YouTube Money Calculator
  • H3 Featured Brand Stories
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H3 Trending in Influencer Marketing
  • H3 Best Agentic Influencer Platforms for Brands and Agencies
  • H3 Best AI Agents for Influencer Marketing in 2026
  • H3 Kuli
  • H3 A Complete Social Media Content Creation Guide
  • H3 5 Influencer Marketing Tips Brands Use to Drive ROI
  • H3 Refersion Affiliate Management
  • H5 As Seen In skipped
  • H4 The Influential Marketer's Hub

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
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)
1 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="subscribe" id="mc-embedded-subscribe">
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" id="mce-EMAIL">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#mce-EMAILemail(Enter your email)placeholder only
#mc-embedded-subscribesubmit(none)none

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

<input type="submit" name="subscribe" id="mc-embedded-subscribe">

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="email" name="EMAIL" id="mce-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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found Influencer Marketing Hub ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
8 decorative image(s) correctly marked
Info::
39 image(s) with good alt text
47 images 39 good alt text 8 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Stay Ahead of the21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore Marketing Tr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find the Team and To…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 MoDash21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Brandwatch21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trending Agencies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trending Platforms21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Marketing Tools & Ca…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Instagram Sponsored …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TikTok Money Calcula…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 YouTube Money Calcul…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured Brand Stori…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trending in Influenc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Refersion Affiliate …21.00:13.0:1
#000000
#FFFFFF
Pass
title Influencer Marketing…21.00:14.5:1
#000000
#FFFFFF
Pass
a Articles20.65:14.5:1
#000000
#FDFDFD
Pass
a Influencer Marketing21.00:14.5:1
#000000
#FFFFFF
Pass
a Social Media21.00:14.5:1
#000000
#FFFFFF
Pass
a eCommerce21.00:14.5:1
#000000
#FFFFFF
Pass
a Affiliate Marketing21.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.

A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 26 passed
PASS
90

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
Search body.home > div#vce-main > header#header > i#searchWidgetTriggerMobile

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
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
SOCIAL MEDIA div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
ECOMMERCE div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
DIGITAL MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
Mar 19, 2026 div.wp-block-group > div.wp-block-group__inner-container > div.v3-postlist-date > time
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
Mar 19, 2026 div.wp-block-group > div.wp-block-group__inner-container > div.v3-postlist-date > time
INFLUENCER MARKETING PLATFORMS div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
Mar 19, 2026 div.wp-block-group > div.wp-block-group__inner-container > div.v3-postlist-date > time
SOCIAL MEDIA div.wp-block-group > div.wp-block-group__inner-container > div.wp-block-post-terms > a
Mar 19, 2026 div.wp-block-group > div.wp-block-group__inner-container > div.v3-postlist-date > time
INFLUENCER MARKETING div.wp-block-group > div.wp-block-group__inner-container > div.taxonomy-category > a
Mar 19, 2026 div.wp-block-group > div.wp-block-group__inner-container > div.v3-postlist-date > time
NEWSLETTER div.container > div.row > div.col-12 > span.d-block
div.row > div.col-12 > div.clear > input#mc-embedded-subscribe div.row > div.col-12 > div.clear > input#mc-embedded-subscribe

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
BY SOCIAL NETWORK div.wp-bootstrap-blocks-container > div.wp-bootstrap-blocks-row > div.col-12 > h4#h-by-social-network
Agencies div.col-12 > div.wp-block-group > div.wp-block-group__inner-container > h4#h-agencies
AS SEEN IN div.container > div.wp-block-group > div.wp-block-group__inner-container > h5#h-as-seen-in

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback