Skip to content
https://cookiebot.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
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.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV "Top navigation menu" MAIN CONTENTINFO footer

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

B
Form Accessibility
2 of 11 controls have issues
REVIEW
2 of 11 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="company_name">; <input type="text" name="company_name">
Info::
9 control(s) properly labeled
11 controls
9 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#field_69e7f55aad647searchSearchfor/id
#field_69e7f55c78fe5textYour website addressaria-label
#field_69e7f55c79305textAge*for/id
#field_69e7f55c79659textYour website addressaria-label
#field_69e7f55c798c2textAge*for/id
#field_69e7f55c79beaemailEnter your emailaria-label
#field_69e7f55c79e7ctextAge*for/id
#field_69e7f55c7a1cfemailEnter your emailaria-label
#field_69e7f55c7a442textAge*for/id
company_nametext(none)none
company_nametext(none)none

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

<input type="text" name="company_name">; <input type="text" name="company_name">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Cookiebot ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 AUTOMATE CONSENT SIGNALING AND DRIVE RESULTS ON TOP AD PLATFORMS
  • H2 Which solution works for you?
  • H2 Cookiebot Core Solopreneur Emerging Business
  • H2 Usercentrics Advanced Advanced Business Enterprise
  • H2 How Cookiebot CMP delivers for you
  • H2 What our customers and partners are saying
  • H2 Is your website privacy compliant?
  • H2 Achieve compliance and minimize your legal risk
  • H2 Improve user experience and transparency
  • H2 Gain peace of mind and control over your website
  • H2 Get to know Cookiebot CMP
  • H3 Step 1
  • H3 Step 2
  • H3 Step 3
  • H2 Consent Mode V2: An All-In-One Course
  • H2 Our latest articles on all things privacy
  • H2 Download the CMP integration for your preferred CMS
  • H2 Usercentrics Cookiebot WordPress Plugin
  • H2 Usercentrics for Wix
  • H2 Stay informed
A+
Alt Text Quality
All 124 images OK
PASS
All 124 images OK
Info::
30 decorative image(s) correctly marked
Info::
94 image(s) with good alt text
124 images 94 good alt text 30 decorative
All images have appropriate alt text.
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)
ElementRatioRequiredFGBGResult
h1 AUTOMATE CONSENT SIG…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Which solution works…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Cookiebot Core15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Usercentrics Advance…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 How Cookiebot CMP de…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 What our customers a…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Is your website priv…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Achieve compliance a…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Improve user experie…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Gain peace of mind a…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Get to know Cookiebo…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Consent Mode V2: An …15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Our latest articles …15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Download the CMP int…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Usercentrics Cookieb…15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Usercentrics for Wix15.58:13.0:1
#000000
#B9E4FD
Pass
h2 Stay informed15.58:13.0:1
#000000
#B9E4FD
Pass
h3 Step 115.58:13.0:1
#000000
#B9E4FD
Pass
h3 Step 215.58:13.0:1
#000000
#B9E4FD
Pass
h3 Step 315.58:13.0:1
#000000
#B9E4FD
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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 29 passed
PASS
100

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.

○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.
●`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
●`<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.
●`[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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback