Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Link & Button Quality

Action

137 links, 21 buttons — all OK

REVIEW

137 links, 21 buttons — all OK

4 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[href="https://www.activecampaign.com/platform/email-marketing"]; a[href="https://www.activecampaign.com/platform/whatsapp-messaging"]; a[href="https://www.activecampaign.com/platform/sms-marketing"]; a[href="https://www.activecampaign.com/apps"]

6 link(s) open in new tab without warning

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

Got: https://www.activecampaign.com/legal/privacy-policy; https://twitter.com/ActiveCampaign; https://www.facebook.com/activecampaign; https://www.linkedin.com/company/activecampaign; https://www.instagram.com/activecampaign; https://www.youtube.com/@ActiveCampaign

127 link(s) with descriptive text

137 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.activecampaign.com/legal/pri…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.activecampaign.com/platform/…	Personalized email marketingBu…	img no alt	Add alt attribute to the image
https://www.activecampaign.com/platform/…	WhatsApp automationMeet custom…	img no alt	Add alt attribute to the image
https://www.activecampaign.com/platform/…	Powerful SMS messagingBuild al…	img no alt	Add alt attribute to the image
https://www.activecampaign.com/apps	1,000+ app integrationsConnect…	img no alt	Add alt attribute to the image
https://twitter.com/ActiveCampaign	Visit ActiveCampaign on Twitte…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/activecampaign	Visit ActiveCampaign on Facebo…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/activec…	Visit ActiveCampaign on Linked…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/activecampaign	Visit ActiveCampaign on Instag…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@ActiveCampaign	Visit ActiveCampaign on Youtub…	new tab	Add '(opens in new tab)' to text

148 links and buttons have descriptive text

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

a[href="https://www.activecampaign.com/platform/email-marketing"]; a[href="https://www.activecampaign.com/platform/whatsapp-messaging"]; a[href="https://www.activecampaign.com/platform/sms-marketing"]; a[href="https://www.activecampaign.com/apps"]

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://www.activecampaign.com/legal/privacy-policy; https://twitter.com/ActiveCampaign; https://www.facebook.com/activecampaign; https://www.linkedin.com/company/activecampaign; https://www.instagram.com/activecampaign; https://www.youtube.com/@ActiveCampaign

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Email Marketing, Automation, and CRM | ActiveCampaign ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 Cut 13 hours of marketing busywork each …

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Get 1‑on‑1 time with an expert

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get your tailored plan, built for your b…

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Automate strategy, not just tasks. Becom…

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Go to market 3x faster. Backed by real i…

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Automate every marketing channel

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Helping thousands of teams punch above t…

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See results in 30 days or get your

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to take ActiveCampaign for a spin…

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Try the autonomous way to work

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Channels

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ecosystem

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 spotlight

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Make it happen

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Featured Industries

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Audiences

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Personalized email marketing

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 WhatsApp automation

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Powerful SMS messaging

1.04:1

#000000

#00002D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Cut 13 hours of mark…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Get 1‑on‑1 time …	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Get your tailored pl…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Automate strategy, n…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Go to market 3x fast…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Automate every marke…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Helping thousands of…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 See results in 30 d…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Ready to take Active…	1.04:1	3.0:1	#000000	#00002D	Fail
h2 Try the autonomous w…	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Capabilities	8.55:1	3.0:1	#000000	#8AA0FF	Pass
h3 Channels	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Ecosystem	1.04:1	3.0:1	#000000	#00002D	Fail
h3 spotlight	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Make it happen	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Featured Industries	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Audiences	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Personalized email m…	1.04:1	3.0:1	#000000	#00002D	Fail
h3 WhatsApp automation	1.04:1	3.0:1	#000000	#00002D	Fail
h3 Powerful SMS messagi…	1.04:1	3.0:1	#000000	#00002D	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.

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

7 <nav> landmark(s) found

2 of 7 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

37 headings

PASS

37 headings

Single H1 present

H3 Capabilities
H3 Channels
H3 Ecosystem
H3 spotlight
H3 Make it happen
H3 Featured Industries
H3 Audiences
H2 Get 1‑on‑1 time with an expert
H2 Get your tailored plan, built for your business
H1 Cut 13 hours of marketing busywork each week¹ with autonomous marketing.
H2 Automate strategy, not just tasks. Become unstoppable.
H2 Go to market 3x faster. Backed by real insights, not endless reports.
H2 Automate every marketing channel
H3 Personalized email marketing
H3 WhatsApp automation
H3 Powerful SMS messaging
H3 1,000+ app integrations
H2 Helping thousands of teams punch above their weight
H2 See results in 30 days or get your money back
H2 Ready to take ActiveCampaign for a spin?
H2 Platform
H3 Capabilities
H3 Channels
H3 Ecosystem
H2 Use Cases
H3 Featured Industries
H3 Audiences
H2 Learn
H3 Resources
H3 Help
H3 Services
H3 Connect
H2 Company
H3 Channel Partners
H3 Contact
H3 Company
H2 Try the autonomous way to work

A+

Alt Text Quality

1 of 26 images have issues

PASS

1 of 26 images have issues

1 image(s) with generic alt text

22 decorative image(s) correctly marked

3 image(s) with good alt text

26 images 3 good alt text 22 decorative 1 generic

Issue	Count
generic	1 image(s)

Form Accessibility

1 of 13 controls have issues

PASS

1 of 13 controls have issues

1 control(s) without accessible label

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

Got: <textarea id="talon6">

12 control(s) properly labeled

13 controls

12 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#demo-name-field	text	Name*	for/id
#demo-email-field	email	Business Email*	for/id
#demo-contacts-field	select	Number of Contacts*	for/id
#demo-phone-field	tel	Phone*	for/id
#demo_messaging_consent	checkbox	ActiveCampaign can contact me by SMS and WhatsApp.	for/id
#pricing-request-name-field	text	Name*	for/id
#pricing-request-email-field	email	Business Email*	for/id
#pricing-request-contacts-field	select	Number of Contacts*	for/id
#pricing-request-phone-field	tel	Phone*	for/id
#pricing_request_messaging_consent	checkbox	ActiveCampaign can contact me by SMS and WhatsApp.	for/id
#signupEmail	email	Email address	for/id
#signupEmail	email	Email address	for/id
#talon6	textarea	(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

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 32 passed

PASS

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
REQUEST A DEMO Get 1‑on‑1 time with an expert Book a personalized demo and see… `body#site > div#demoRequestDrawer`
REQUEST PRICING Get your tailored plan, built for your business Tell us your n… `body#site > div#pricingRequestDrawer`

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.

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
Go to slide 1 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.prompt-text-box__wrapper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 1 `div.container-alignment-helper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.container-alignment-helper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.container-alignment-helper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.container-alignment-helper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.container-alignment-helper > div.carousel-navigation-controls > div.swiper-pagination > span.swiper-pagination-bullet`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

●Background and foreground colors have a sufficient contrast ratio

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

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○No form fields have multiple labels

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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