Skip to content
https://cookieadmin.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN CONTENTINFO footer

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

B
Heading Hierarchy
3 headings
REVIEW
3 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Quick links
  • H2 Features
  • H2 Our products

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title CookieAdmin - Cookie Consent Banner WordPress Plugin ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
span Cookie Consent Banner
3.84:1
#166AEA
on
#D7E5F7
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Quick links16.55:13.0:1
#000000
#D7E6F7
Pass
h2 Features16.55:13.0:1
#000000
#D7E6F7
Pass
h2 Our products16.55:13.0:1
#000000
#D7E6F7
Pass
title CookieAdmin - Cookie…16.55:14.5:1
#000000
#D7E6F7
Pass
span Home16.55:14.5:1
#000000
#D7E6F7
Pass
span Features16.55:14.5:1
#000000
#D7E6F7
Pass
span Pricing16.44:14.5:1
#000000
#D7E5F7
Pass
span Docs16.44:14.5:1
#000000
#D7E5F7
Pass
span Blog16.44:14.5:1
#000000
#D7E5F7
Pass
span Contact Us16.44:14.5:1
#000000
#D7E5F7
Pass
span Get Now16.44:14.5:1
#000000
#D7E5F7
Pass
div CookieAdmin: Simple,…16.44:14.5:1
#000000
#D7E5F7
Pass
div Lightweight, Powerfu…16.44:14.5:1
#000000
#D7E5F7
Pass
span Cookie Consent Banne…3.84:14.5:1
#166AEA
#D7E5F7
Fail
div Plugin for WordPress16.44:14.5:1
#000000
#D7E5F7
Pass
div Privacy compliance s…16.44:14.5:1
#000000
#D7E5F7
Pass
span GDPR & CCPA16.44:14.5:1
#000000
#D7E5F7
Pass
span Customizable Banner16.44:14.5:1
#000000
#D7E5F7
Pass
span Consent Logs16.44:14.5:1
#000000
#D7E5F7
Pass
span Granular Control16.41:14.5:1
#000000
#D6E5F7
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 20 passed
REVIEW
88

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
Customize Consent Form div.p-it39097 > div.pagelayer-tabs-holder > span#undefined > span

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GDPR & CCPA Customizable Banner Consent Logs Granular Control div.p-jtj9608 > div.pagelayer-col-holder > div.p-mxn593 > ul.pagelayer-list-ul
Consent Logs Anonymized User IP GDPR & US State Laws Customizable Consent Form … div.p-u6y8057 > div.pagelayer-col-holder > div.p-mmd9921 > ul.pagelayer-list-ul
Softaculous Softaculous Cloud Virtualizor Webuzo AMPPS SitePad div.p-pm79180 > div.pagelayer-col-holder > div.p-uu8626 > ul.pagelayer-list-ul

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GDPR & CCPA div.p-mxn593 > ul.pagelayer-list-ul > div.p-ajo189 > li.pagelayer-list-li
Customizable Banner div.p-mxn593 > ul.pagelayer-list-ul > div.p-va41176 > li.pagelayer-list-li
Consent Logs div.p-mxn593 > ul.pagelayer-list-ul > div.p-yjb4687 > li.pagelayer-list-li
Granular Control div.p-mxn593 > ul.pagelayer-list-ul > div.p-hoo1239 > li.pagelayer-list-li
Consent Logs div.p-mmd9921 > ul.pagelayer-list-ul > div.p-adn8365 > li.pagelayer-list-li
Anonymized User IP div.p-mmd9921 > ul.pagelayer-list-ul > div.p-k4b3758 > li.pagelayer-list-li
GDPR & US State Laws div.p-mmd9921 > ul.pagelayer-list-ul > div.p-9ng876 > li.pagelayer-list-li
Customizable Consent Form div.p-mmd9921 > ul.pagelayer-list-ul > div.p-yii2720 > li.pagelayer-list-li
Preview Consent Form div.p-mmd9921 > ul.pagelayer-list-ul > div.p-cje3487 > li.pagelayer-list-li
Visitor Country Detection div.p-mmd9921 > ul.pagelayer-list-ul > div.p-vcp1327 > li.pagelayer-list-li
Scan cookies div.p-mmd9921 > ul.pagelayer-list-ul > div.p-sml117 > li.pagelayer-list-li
Google Consent Mode v2 div.p-mmd9921 > ul.pagelayer-list-ul > div.p-j2h5062 > li.pagelayer-list-li
ADA, EAA & WCAG Compliant div.p-mmd9921 > ul.pagelayer-list-ul > div.p-8ki7188 > li.pagelayer-list-li
Softaculous div.p-uu8626 > ul.pagelayer-list-ul > div.p-eey8633 > li.pagelayer-list-li
Softaculous Cloud div.p-uu8626 > ul.pagelayer-list-ul > div.p-z8b3462 > li.pagelayer-list-li
Virtualizor div.p-uu8626 > ul.pagelayer-list-ul > div.p-ju67765 > li.pagelayer-list-li
Webuzo div.p-uu8626 > ul.pagelayer-list-ul > div.p-s361500 > li.pagelayer-list-li
AMPPS div.p-uu8626 > ul.pagelayer-list-ul > div.p-qsg6738 > li.pagelayer-list-li
SitePad div.p-uu8626 > ul.pagelayer-list-ul > div.p-kkq9753 > li.pagelayer-list-li

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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 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 have a discernible name
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Identical links have the same purpose.
○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+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
19 image(s) with good alt text
19 images 19 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailtext(Enter your email)placeholder only

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

<input type="text" name="email">

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

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

Send Feedback