Accessibility

D

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

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

F

Heading Hierarchy

Action

67 headings, 18 skip(s)

FIX

67 headings, 18 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

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

H5 Performance
H5 Creator
H5 Advocate
H1 One platform. All partnerships. AI-powered.
H2 Creators.
H2 Affiliates.
H2 Customer referrals.
H2 Communities.
H2 Unified.
H2 The AI-native partnership platform powering global commerce
H2 Affiliate, Creator, and Referral programs together at last
H5 Stop juggling multiple tools and fragmented data. Finally, manage all your partnerships from one dashboard. skipped
H5 No more silos. No more switching between platforms. Just one platform where you can see which partnerships actually drive sales.
H3 The ROI case for unified partnership management
H6 Brands using affiliates + influencers drive up to 46% more sales than single-channel strategies skipped
H2 46%
H6 Integrating referrals with affiliate can lift revenue by as much as 22% skipped
H2 22%
H6 You save 15+ hours per week managing partnerships from one dashboard instead of three skipped
H2 15+
H3 Why it matters now
H6 AI-driven traffic to retail sites: up 4,700% YoY skipped
H2 4,700%
H6 Shoppers using AI for purchases: 39% (53% plan to this year) skipped
H2 39%
H6 Gen Z using AI search daily: 35% skipped
H2 35%
H2 Why leading brands are shifting marketing budget to partnerships
H5 Paid ads hit a ceiling skipped
H5 Consumers trust people, not ads
H5 AI accelerates everything
H2 Finally see which partnerships actually drive sales
H3 Stop guessing which partners are worth your budget.
H2 We uncover which partnerships generate revenue, not just clicks and traffic
H2 Track real results from influencer campaigns, not just engagement. #1 influencer platform for performance-driven creator marketing
H2 Turn your customers into a measurable revenue channel
H6 (empty)
H3 Partnerships work. But don’t just take our word for it—see the results yourself
H6 Case study skipped
H3 23.6m
H6 Case study skipped
H3 160%
H6 Case study skipped
H3 3,755%
H6 Case study skipped
H3 10+
H6 Case study skipped
H3 421%
H6 Case study skipped
H3 $1M
H6 Case study skipped
H3 160%
H1 Take your partnership program to the next level duplicate H1
H3 Request a demo skipped
H4 Yes, I would like to receive marketing communications regarding impact.com products, services, and events. I can unsubscribe at a later time. By registering, you c
H3 impact.com partnership management platform
H2 Discover & Recruit
H2 Contract & Pay
H2 Track
H2 Engage
H2 Protect & Monitor
H2 Optimize
H2 We also recommend
H6 Blog skipped
H6 Blog
H6 Blog
H4 Yes, I would like to receive marketing communications regarding impact.com products, services, and events. I can unsubscribe at a later time. By registering, you confirm that you agree to the storing

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

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

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

Link & Button Quality

Action

8 issue(s) across 197 links and 11 buttons

FIX

8 issue(s) across 197 links and 11 buttons

8 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://impact.com/creator/ ("Learn more"); https://impact.com/advocate/ ("Learn more"); /discover-recruit/ ("Learn more"); /partnership-contract-pay/ ("Learn more"); /partnership-track/ ("Learn more"); /manage-engage/ ("Learn more"); /protect-monitor/ ("Learn more"); /optimize-insights/ ("Learn more")

7 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a.block (#483 on page); a[href="https://impact.com/case-studies/strands-are-media-case-study-pars-csp-imp-vd-…"]; a[href="https://impact.com/case-studies/taylor-hart-case-study-affa-csb-imp-ev-emea/"]; a[href="https://impact.com/case-studies/elite-supplements-case-study-affa-csb-imp-ev-…"]; a[href="https://impact.com/case-studies/starshipit-case-study-refr-csb-adv-ev-apac/"]; a[href="https://impact.com/case-studies/bill-case-study-affa-csb-imp-ev-nam/"]; a[href="https://impact.com/case-studies/scrambly-case-study-affa-csb-imp-ev-emea/"]

19 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://impact.com/privacy-policy/; https://app.impact.com/login.user; https://app.impact.com/login.user; https://impact.com/privacy-policy/; https://app.impact.com/signup/none/create-new-mediapartner-account-flow.ihtml…; https://integrations.impact.com/; https://help.impact.com/en/support/home; /privacy-policy/; https://www.linkedin.com/company/impactdotcom/; https://www.instagram.com/impactdotcom/ (+9 more)

163 link(s) with descriptive text

197 links

0 empty

8 generic text

19 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://impact.com/privacy-policy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://app.impact.com/login.user	Sign in	new tab	Add '(opens in new tab)' to text
https://app.impact.com/login.user	Sign in	new tab	Add '(opens in new tab)' to text
	Consumers trust people, not ad…	img no alt	Add alt attribute to the image
https://impact.com/creator/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Creator
https://impact.com/advocate/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advocate
https://impact.com/case-studies/strands-…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/case-studies/taylor-h…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/case-studies/elite-su…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/case-studies/starship…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/case-studies/bill-cas…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/case-studies/scrambly…	Case study …	img no alt	Add alt attribute to the image
https://impact.com/privacy-policy/	privacy policy…	new tab	Add '(opens in new tab)' to text
https://app.impact.com/signup/none/creat…	Sign up	new tab	Add '(opens in new tab)' to text
/discover-recruit/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Discover Recruit
/partnership-contract-pay/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Partnership Contract Pay
/partnership-track/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Partnership Track
/manage-engage/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Manage Engage
/protect-monitor/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Protect Monitor
/optimize-insights/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Optimize Insights
https://integrations.impact.com/	Developer portal	new tab	Add '(opens in new tab)' to text
https://help.impact.com/en/support/home	Help center	new tab	Add '(opens in new tab)' to text
/privacy-policy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/impactd…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/impactdotcom/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/impactdotcom1	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/impactdotcom	Youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@impactdotcom	TikTok	new tab	Add '(opens in new tab)' to text
https://impact.com/feed/	RSS feed	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/impact-com/id…	Download on the app store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Get it on Google play	new tab	Add '(opens in new tab)' to text
https://impact.responsibledisclosure.com…	Responsible disclosure	new tab	Add '(opens in new tab)' to text
https://impact.com/legal/IRL_Modern_Slav…	Modern slavery statement	new tab	Add '(opens in new tab)' to text
https://impact.com/legal/PAIA_manual_imp…	PAIA manual	new tab	Add '(opens in new tab)' to text

174 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://impact.com/creator/ ("Learn more"); https://impact.com/advocate/ ("Learn more"); /discover-recruit/ ("Learn more"); /partnership-contract-pay/ ("Learn more"); /partnership-track/ ("Learn more"); /manage-engage/ ("Learn more"); /protect-monitor/ ("Learn more"); /optimize-insights/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a.block (#483 on page); a[href="https://impact.com/case-studies/strands-are-media-case-study-pars-csp-imp-vd-…"]; a[href="https://impact.com/case-studies/taylor-hart-case-study-affa-csb-imp-ev-emea/"]; a[href="https://impact.com/case-studies/elite-supplements-case-study-affa-csb-imp-ev-…"]; a[href="https://impact.com/case-studies/starshipit-case-study-refr-csb-adv-ev-apac/"]; a[href="https://impact.com/case-studies/bill-case-study-affa-csb-imp-ev-nam/"]; a[href="https://impact.com/case-studies/scrambly-case-study-affa-csb-imp-ev-emea/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://impact.com/privacy-policy/; https://app.impact.com/login.user; https://app.impact.com/login.user; https://impact.com/privacy-policy/; https://app.impact.com/signup/none/create-new-mediapartner-account-flow.ihtml…; https://integrations.impact.com/; https://help.impact.com/en/support/home; /privacy-policy/; https://www.linkedin.com/company/impactdotcom/; https://www.instagram.com/impactdotcom/ (+9 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

D

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

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)

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

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

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

3 navigation landmark(s) detected

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 3 <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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - impact.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 One platform. All partnerships. AI-power…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Take your partnership program to the nex…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The AI-native partnership platform power…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Affiliate, Creator, and Referral program…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 46%

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 22%

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 15+

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 4,700%

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 39%

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 35%

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why leading brands are shifting marketin…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Finally see which partnerships actually …

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We uncover which partnerships generate r…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Track real results from influencer campa…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Turn your customers into a measurable re…

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discover & Recruit

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contract & Pay

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Track

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Engage

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Protect & Monitor

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 One platform. All pa…	1.00:1	3.0:1	#000000	#000000	Fail
h1 Take your partnershi…	1.00:1	3.0:1	#000000	#000000	Fail
h2 The AI-native partne…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Affiliate, Creator, …	1.00:1	3.0:1	#000000	#000000	Fail
h2 46%	1.00:1	3.0:1	#000000	#000000	Fail
h2 22%	1.00:1	3.0:1	#000000	#000000	Fail
h2 15+	1.00:1	3.0:1	#000000	#000000	Fail
h2 4,700%	1.00:1	3.0:1	#000000	#000000	Fail
h2 39%	1.00:1	3.0:1	#000000	#000000	Fail
h2 35%	1.00:1	3.0:1	#000000	#000000	Fail
h2 Why leading brands a…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Finally see which pa…	1.00:1	3.0:1	#000000	#000000	Fail
h2 We uncover which par…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Track real results f…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Turn your customers …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Discover & Recruit	1.00:1	3.0:1	#000000	#000000	Fail
h2 Contract & Pay	1.00:1	3.0:1	#000000	#000000	Fail
h2 Track	1.00:1	3.0:1	#000000	#000000	Fail
h2 Engage	1.00:1	3.0:1	#000000	#000000	Fail
h2 Protect & Monitor	1.00:1	3.0:1	#000000	#000000	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

Alt Text Quality

1 of 41 images have issues

PASS

1 of 41 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

9 decorative image(s) correctly marked

31 image(s) with good alt text

41 images 31 good alt text 9 decorative 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A

Form Accessibility

1 of 17 controls have issues

PASS

1 of 17 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" name="GDPR_email_opt_in__c" id="GDPR_email_opt_in__c">

16 control(s) properly labeled

17 controls

16 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#osano-cm-dialog-toggle--category_MARKETING	checkbox		none
#osano-cm-dialog-toggle--category_PERSONALIZATION	checkbox		none
#osano-cm-dialog-toggle--category_ANALYTICS	checkbox		none
#Account_Type__c	select	Company type	aria-label
#PC_Primary_Topic_Interest__c	select	What are you interested in?	aria-label
#FirstName	text	First name	for/id
#LastName	text	Last name	for/id
#Email	email	Business email	for/id
#Title	text	Job title	for/id
#Phone	tel	Business phone	for/id
#Country	select	Country	aria-label
#Company	text	Company name	for/id
#Website	url	Company website	for/id
#Existing_Affiliate_Program__c	select	Existing Affiliate program	aria-label
#GDPR_email_opt_in__c	checkbox	Marketing communications	aria-label
#newsletterEmail	email	Business email	for/id
#GDPR_email_opt_in__c	checkbox	(none)	none

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

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

A

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 32 passed

PASS

91

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
ADVOCATE `div.feature > div.feature-inner > div.left > p.caption`
Resource hub `div.page-content > section.recommended-content > div.more > 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
Stop juggling multiple tools and fragmented data. Finally, manage all your part… `div.feature-block-inner > div.blocks > a.block > h5`
Brands using affiliates + influencers drive up to 46% more sales than single-ch… `div.inner > div.specs > div.block > h6`
Integrating referrals with affiliate can lift revenue by as much as 22% `div.inner > div.specs > div.block > h6`
You save 15+ hours per week managing partnerships from one dashboard instead of… `div.inner > div.specs > div.block > h6`
AI-driven traffic to retail sites: up 4,700% YoY `div.inner > div.specs > div.block > h6`
Shoppers using AI for purchases: 39% (53% plan to this year) `div.inner > div.specs > div.block > h6`
Gen Z using AI search daily: 35% `div.inner > div.specs > div.block > h6`
Paid ads hit a ceiling `div.feature-block-inner > div.blocks > a.block > h5`
div.featured-series-container > div.content-column > div.content > h6 `div.featured-series-container > div.content-column > div.content > h6`
CASE STUDY `div > a.insight-content-card > div.copy > h6`
Request a demo `div.consolidated-hero > div.consolidated-hero-container > div.right > h3`
BLOG `div.posts > a.insight-content-card > div.copy > h6`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div.page-content > img `body.home > div.page-content > img`

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

●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.

●Select elements have associated label elements.

●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

●ARIA IDs are unique

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●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 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

○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

○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>`.

○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.