Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Landmark Structure

Action

9 landmarks

FIX

9 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

1 of 3 <nav> elements are unlabeled

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

No contentinfo (footer) 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

Form Accessibility

Action

8 of 8 controls have issues

FIX

8 of 8 controls have issues

3 control(s) without accessible label

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

Got: <select name="country_c" id="country_c">; <select name="Monthly_click_volume__c" id="Monthly_click_volume__c">; <input type="submit">

5 control(s) rely on placeholder only

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

Got: <input type="text" name="firstname" id="firstname">; <input type="text" name="lastname" id="lastname">; <input type="email" name="email" id="email">; <input type="text" name="company" id="company">; <input type="tel" name="phone" id="phone">

8 controls

0 labeled

5 placeholder only

3 unlabeled

Control	Type	Label	Method
#firstname	text	(First name)	placeholder only
#lastname	text	(Last name)	placeholder only
#email	email	(Email address)	placeholder only
#company	text	(Company)	placeholder only
#phone	tel	(Phone)	placeholder only
#country_c	select	(none)	none
#Monthly_click_volume__c	select	(none)	none
input	submit	(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

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

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

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

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Alt Text Quality

2 of 116 images have issues

REVIEW

2 of 116 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

62 decorative image(s) correctly marked

52 image(s) with good alt text

116 images 52 good alt text 62 decorative 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

9 issue(s) across 64 links and 4 buttons

REVIEW

9 issue(s) across 64 links and 4 buttons

9 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.linkedin.com/company/clickcease-com; https://www.facebook.com/ClickCease.Official/; https://www.instagram.com/clickcease/; https://www.youtube.com/channel/UCbD3MGLBG3h9drpNOb2SF_g; https://il.linkedin.com/showcase/clickcease/; https://www.facebook.com/ClickCease.Official/; https://www.instagram.com/clickcease/; https://www.youtube.com/channel/UCbD3MGLBG3h9drpNOb2SF_g; #

5 link(s) open in new tab without warning

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

Got: https://support.clickcease.com; https://www.cheq.ai/careers; https://support.clickcease.com; https://cheq.ai/privacy-policy/; https://cheq.ai/trust/

50 link(s) with descriptive text

64 links

9 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://support.clickcease.com	Knowledge center …	new tab	Add '(opens in new tab)' to text
/case-studies/injury-lawyer.html	$65,000+ worth of fraudulent c…	img no alt	Add alt attribute to the image
/case-studies/eric-preston.html	20% CPA improvement, lead cost…	img no alt	Add alt attribute to the image
/case-studies/corkboard.html	$500,000+ savings by preventin…	img no alt	Add alt attribute to the image
https://www.cheq.ai/careers	Careers	new tab	Add '(opens in new tab)' to text
https://support.clickcease.com	Support	new tab	Add '(opens in new tab)' to text
#	Start a chat	img no alt	Add alt attribute to the image
mailto:support@clickcease.com?subject=I%…	Email us	img no alt	Add alt attribute to the image
#	Start a chat	img no alt	Add alt attribute to the image
mailto:support@clickcease.com?subject=I%…	Email us	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/clickce…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/ClickCease.Offi…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/clickcease/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCbD3MGL…	(empty)	empty	Add link text or aria-label
https://cheq.ai/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://cheq.ai/trust/	Trust	new tab	Add '(opens in new tab)' to text
https://il.linkedin.com/showcase/clickce…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/ClickCease.Offi…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/clickcease/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCbD3MGL…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label

54 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.linkedin.com/company/clickcease-com; https://www.facebook.com/ClickCease.Official/; https://www.instagram.com/clickcease/; https://www.youtube.com/channel/UCbD3MGLBG3h9drpNOb2SF_g; https://il.linkedin.com/showcase/clickcease/; https://www.facebook.com/ClickCease.Official/; https://www.instagram.com/clickcease/; https://www.youtube.com/channel/UCbD3MGLBG3h9drpNOb2SF_g; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://support.clickcease.com; https://www.cheq.ai/careers; https://support.clickcease.com; https://cheq.ai/privacy-policy/; https://cheq.ai/trust/

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A+

Heading Hierarchy

32 headings

PASS

32 headings

Single H1 present

2 hidden heading(s) (aria-hidden)

H1 Protect your ads and websites with the best-in-class solution
H2 Block only the bad traffic
H2 Stop potential threats from seeing your ads
H2 Why marketers choose ClickCease
H3 “ClickCease saves us 15-20% of our Google Ads spend every month”
H3 “ClickCease puts my mind at ease regarding Click fraud on Google Ads” hidden
H3 “we save 1000's of Dollars each month by Blocking click fraud with clickcease” hidden
H2 1000+ Reviews
H2 ClickCease works with any platform
H2 Customer success stories
H3 $65,000+ worth of fraudulent clicks prevented
H3 20% CPA improvement, lead cost decreased by 40%
H3 $500,000+ savings by preventing click fraud
H2 Say goodbye to click fraud
H3 Outsmart competitors
H3 Save money 24/7
H3 Improve ads
H3 Customize
H3 Get insights
H3 Get refunds*
H2 Don't settle for ordinary protection
H2 GDPR & CCPA
H2 The leading click fraud protection software
H2 Over 2,000,000 campaigns worldwide are protected by ClickCease
H3 Product
H3 Company
H3 Resources
H3 Got a question?
H3 Got a question?
H3 Got a question?
H3 Social
H2 Schedule a call

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)

Element	Ratio	Required	FG	BG	Result
h1 Protect your ads and…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Block only the bad t…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Stop potential threa…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Why marketers choose…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 1000+ Reviews	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 ClickCease works wit…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Customer success sto…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Say goodbye to click…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Don't settle for ord…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 GDPR & CCPA	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 The leading click fr…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Over 2,000,000 campa…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h2 Schedule a call	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 “ClickCease saves …	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 “ClickCease puts m…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 “we save 1000's of…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 $65,000+ worth of fr…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 20% CPA improvement,…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 $500,000+ savings by…	19.03:1	3.0:1	#000000	#FBF2ED	Pass
h3 Outsmart competitors	19.03:1	3.0:1	#000000	#FBF2ED	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.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 27 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.

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
best-in-class solution `div.hero__wrapper > div.hero__text > h1.h1-heading > span.orange-span`
Start free trial `div.hero__text > div.hero__bottom > div.hero__btn-box > a.cta-btn`
See more reviews `div.slider > div.container > div.button_box > a.cta-btn`
View case study `a.q_card > div.q_card-text > div.q_button-box > p.paragraph`
View case study `a.q_card > div.q_card-text > div.q_button-box > p.paragraph`
View case study `div.q_card-text > div.q_card-body > div.q_button-box > p.paragraph`
Start free trial `div.section > div.container > div.d-button-box > a.cta-btn`
Start free trial `div.content-title > div.botom-cta__btn-wrap > div.cta-wraper-mob > a.cta-btn`
Accept All `section > div#ensNotifyBanner > div.ensButtons > button#ensAcceptAll`
Reject All `section > div#ensNotifyBanner > div.ensButtons > button#ensRejectAll`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-box > div.footer-col > div.footer_social-box > a.social-links `div.footer-box > div.footer-col > div.footer_social-box > a.social-links`
div.footer-box > div.footer-col > div.footer_social-box > a.social-links `div.footer-box > div.footer-col > div.footer_social-box > a.social-links`
div.footer-box > div.footer-col > div.footer_social-box > a.social-links `div.footer-box > div.footer-col > div.footer_social-box > a.social-links`
div.footer-box > div.footer-col > div.footer_social-box > a.social-links `div.footer-box > div.footer-col > div.footer_social-box > a.social-links`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
click here `section > div#ensNotifyBanner > div#ensBannerDescription > span#ensModalLink`

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

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

○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

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

○All heading elements contain content.

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

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