Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

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.

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 ✗

Heading Hierarchy

Action

24 headings, 2 skip(s)

REVIEW

24 headings, 2 skip(s)

Multiple H1 headings (6 found)

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

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: H1 → H3 (missing H2)

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

H3 PC Apps
H3 Mobile Apps
H3 Mac Apps
H3 Download Center
H3 Product Support
H3 Partner Program
H3 PC Apps
H3 Mobile Apps
H3 Mac Apps
H3 Download Center
H3 Product Support
H3 Partner Program
H1 Clean up, speed up, and fix your PC with CCleaner
H1 As featured in: duplicate H1
H3 Reclaim valuable storage space skipped
H3 Give your online privacy a boost
H1 Need a more specific type of app or service? duplicate H1
H1 You're almost done! duplicate H1
H1 To finish setting up, open the file you've downloaded and follow the simple on-screen steps duplicate H1
H1 Thanks for downloading CCleaner duplicate H1
H3 Run the CCleaner installer skipped
H3 Confirm the installation
H3 Follow installation instructions
H3 Manage Consent Preferences

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

Action

12 of 28 images have issues

REVIEW

12 of 28 images have issues

12 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

16 image(s) with good alt text

28 images 16 good alt text 12 missing

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 87/100 — 5 failing, 25 passed

REVIEW

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
We value your privacy By clicking "OK" you allow cookies that improve your expe… `section > div#ensNotifyBanner > div#ensBannerDescription > div.privacyDialog`

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
1Patent number 8,463,758 from the United States Patent and Trademark Office for… `div.lg:border > div.shrink > div > div.disclaimer-text`
Find out more `div.shrink > div > div.disclaimer-text > a`
© Copyright 2005-2026 Gen Digital Inc - All rights reserved. `footer.py-8 > div.container > div.foot > p.mb-[15px]`
Terms of Use `div.mb-[15px] > span > a#GTM__footer__terms-of-use > span.underline`
Supplier Guidelines `div.mb-[15px] > span > a#GTM__footer__supplier-guidelines > span.underline`
Modern Slavery Statement `div.mb-[15px] > span > a#GTM__footer__modern-slavery-statement > span.underline`
General Privacy Policy `div.mb-[15px] > span > a#GTM__footer__privacy-policy > span.underline`
Do Not Sell or Share My Personal Information `div.mb-[15px] > span > a.hover:text-grey-4 > span.underline`
Consent Policy `div.mb-[15px] > span > a.hover:text-grey-4 > span.underline`
Products Policy `div.mb-[15px] > span > a.hover:text-grey-4 > span.underline`
Cookies Policy `div.mb-[15px] > span > a#GTM__footer__cookies-policy > span.underline`
Accessibility Policy `div.mb-[15px] > span > a#GTM__footer__accessibility-statement > span.underline`
Cookie Settings `div.container > div.foot > div.mb-[15px] > button#cookies-settings`
CCleaner, Defraggler, Recuva and Speccy are all registered trademarks of Gen Di… `footer.py-8 > div.container > div.foot > p`

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
Reclaim valuable storage space `div.lg:max-w-[548px] > ul.mb-[32px] > li.list-item > h3.font-bold`

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
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.container > div.max-w-[926px] > div.relative > img `div.container > div.max-w-[926px] > div.relative > img`
div.flex > div.flex > div.flex > img.v-lazy-image `div.flex > div.flex > div.flex > img.v-lazy-image`
div.flex > div.flex > div.flex > img.v-lazy-image `div.flex > div.flex > div.flex > img.v-lazy-image`
div.flex > div.flex > div.flex > img.v-lazy-image `div.flex > div.flex > div.flex > img.v-lazy-image`

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
Cookies Policy `div.privacyDialog > div.privacyContent > div.privacyDescription > a.privacyPolicyLink`

○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

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Form Accessibility

All 11 controls labeled

PASS

All 11 controls labeled

11 control(s) properly labeled

11 controls

11 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#PreferenceSlide	checkbox	Preference cookies	none
#Preference-Akamai-Mpulse-\go-mpulse\net-slide	checkbox	Akamai Mpulse	none
#PerformanceSlide	checkbox	Performance cookies	none
#Performance-Qualtrics-siteinterceptqualtricscom-slide	checkbox	Qualtrics	none
#Performance-Google-Analytics-^(+\)?(google-analytics\|analytics\google)\com$-slide	checkbox	Google Analytics	none
#AdvertisingSlide	checkbox	Marketing cookies	none
#Advertising-Bing-\bing\com-slide	checkbox	Bing	none
#Advertising-LinkedIn--wwwlinkedincom-slide	checkbox	LinkedIn	none
#Advertising-Meta-^(+\)?(facebook\(com\|net)\|fbcdn\net\|meta\com\|instagram\com)$-slide	checkbox	Meta	none
#Advertising-Google-Ads-^(+\)?(doubleclick\net\|googleads\com\|googleadservices\com\|googlesyndication\com\|adservice\google\com\|merchant-center-analytics\goog)$-slide	checkbox	Google Ads	none
#Advertising-Microsoft-\microsoft\com-slide	checkbox	Microsoft	none

Link & Button Quality

1 issue(s) across 154 links and 12 buttons

PASS

1 issue(s) across 154 links and 12 buttons

1 link(s) with generic text

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

Got: /ccleaner/professional ("Learn More")

1 link(s) open in new tab without warning

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

Got: https://www.ccleaner.com/about/cookies-policy

152 link(s) with descriptive text

154 links

0 empty

1 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/ccleaner/professional	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Professional
https://www.ccleaner.com/about/cookies-p…	More information about your pr…	new tab	Add '(opens in new tab)' to text

164 links and buttons have descriptive text

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

/ccleaner/professional ("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

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

https://www.ccleaner.com/about/cookies-policy

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

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 Clean up, speed up, …	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h1 As featured in:	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h1 Need a more specific…	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h1 You're almost done!	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h1 To finish setting up…	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h1 Thanks for downloadi…	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 PC Apps	4.94:1	3.0:1	#000000	#787B80	Pass
h3 Mobile Apps	4.94:1	3.0:1	#000000	#787B80	Pass
h3 Mac Apps	4.94:1	3.0:1	#000000	#787B80	Pass
h3 Download Center	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Product Support	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Partner Program	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 PC Apps	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Mobile Apps	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Mac Apps	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Download Center	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Product Support	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Partner Program	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Reclaim valuable sto…	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Give your online pri…	5.03:1	3.0:1	#000000	#7C7C7C	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.