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 3 REVIEW 5 FIX

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

No <nav> landmark found

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.

Search landmark present

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

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

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

1 issue(s) across 48 links and 12 buttons

REVIEW

1 issue(s) across 48 links and 12 buttons

1 link(s) with no accessible text

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

Got: https://complianz.io

5 link(s) open in new tab without warning

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

Got: https://wordpress.org/plugins/complianz-gdpr/; https://www.linkedin.com/company/74253592/; https://github.com/Really-Simple-Plugins; https://cookiedatabase.org/tcf/purposes/; https://cookiedatabase.org/tcf/purposes/

42 link(s) with descriptive text

48 links

1 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://complianz.io	(empty)	empty	Add link text or aria-label
https://wordpress.org/plugins/complianz-…	WordPress	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/7425359…	Linkedin	new tab	Add '(opens in new tab)' to text
https://github.com/Really-Simple-Plugins	Github	new tab	Add '(opens in new tab)' to text
https://cookiedatabase.org/tcf/purposes/	Read more about these purposes	new tab	Add '(opens in new tab)' to text
https://cookiedatabase.org/tcf/purposes/	Read more about these purposes	new tab	Add '(opens in new tab)' to text

54 links and buttons have descriptive text

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

https://complianz.io

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://wordpress.org/plugins/complianz-gdpr/; https://www.linkedin.com/company/74253592/; https://github.com/Really-Simple-Plugins; https://cookiedatabase.org/tcf/purposes/; https://cookiedatabase.org/tcf/purposes/

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

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

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 28 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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
`div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-header > div.cmplz-close`

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
Explore `div.elementor-cta > div.elementor-cta__content > div.elementor-cta__button-wrapper > a.elementor-cta__button`

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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`

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.

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.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.elementor-swiper > div.elementor-main-swiper > 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]`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

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 Join 1 Million Users Trusting Complianz for the Best Cookie Consent Solution
H2 Discover Complianz for WordPress
H2 Discover Complianz for Shopify
H3 News
H3 Sales Question?
H2 Reviews
H3 Join our mailing list - 8 Tips & Tricks in your inbox over the next week, that's all!
H4 Plugins
H3 Get Started
H3 Legal
H3 Premium

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

2 decorative image(s) correctly marked

6 image(s) with good alt text

8 images 6 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#elementor-search-form-72685ec	search	Search	for/id
#form-field-email	email	Your Email	for/id
#cmplz-functional-optin	checkbox	Functional	for/id
#cmplz-preferences-optin	checkbox	Preferences	for/id
#cmplz-statistics-optin	checkbox	Statistics	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id
#cmplz-functional-optout	checkbox	Functional	for/id
#cmplz-preferences-optout	checkbox	Preferences	for/id
#cmplz-statistics-optout	checkbox	Statistics	for/id
#cmplz-marketing-optout	checkbox	Marketing	for/id

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Complianz ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 Join 1 Million Users…	18.13:1	3.0:1	#000000	#E9EFF5	Pass
h2 Discover Complianz f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover Complianz f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Reviews	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h3 News	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h3 Sales Question?	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h3 Join our mailing lis…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h3 Legal	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h3 Premium	14.88:1	3.0:1	#000000	#D9D9D9	Pass
title 1 Million Users Trus…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span WordPress Plugin	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Shopify App	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search	18.13:1	4.5:1	#000000	#E9EFF5	Pass
span Login	18.13:1	4.5:1	#000000	#E9EFF5	Pass
div 4.8 out 1500+ review…	18.13:1	4.5:1	#000000	#E9EFF5	Pass
i 	18.13:1	4.5:1	#000000	#E9EFF5	Pass
i 	18.13:1	4.5:1	#000000	#E9EFF5	Pass
i 	18.13:1	4.5:1	#000000	#E9EFF5	Pass
i 	18.13:1	4.5:1	#000000	#E9EFF5	Pass
i 	18.13:1	4.5:1	#000000	#E9EFF5	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.