Skip to content
https://wpconsent.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) ASIDE "Language selected: English" CONTENTINFO footer

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

F
Alt Text Quality
Action
5 of 44 images have issues
FIX
5 of 44 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
19 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
44 images 20 good alt text 19 decorative 5 missing
IssueCount
missing5 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
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 Page not found – WPConsent ✓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
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 21 passed
REVIEW
83

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
Get WPConsent Now div#sp-button-parent-cii6rt > a#sp-cii6rt > span > strong
Get WPConsent Now div#sp-wkvfwq > div#sp-button-parent-qc5gjz > a#sp-qc5gjz > span
See all Features div#sp-button-parent-x99byd > a#sp-x99byd > span > strong
Get WPConsent Now div#sp-az9cif > div#sp-button-parent-m31tw2 > a#sp-m31tw2 > span
Get WPConsent Now div.footer-cta-content-1 > div.footer-cta-column > a.wpconsent-buton-cta > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
contact us div#sp-zu6kzg > div#sp-r5baq4 > p > a

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
7 Best Cookiebot Alternatives for WordPress (2026 Compared) div.sp-post-text-container > a > div.sp-container > h4.sp-pt-0

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.duplicator-site-branding > a > span.duplicator-header-logo > img div.duplicator-site-branding > a > span.duplicator-header-logo > img
div.duplicator-mobile-menu > div.duplicator-mobile-menu-top > button#duplicator-menu-open > img div.duplicator-mobile-menu > div.duplicator-mobile-menu-top > button#duplicator-menu-open > img

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-links > div#footer-social-wrapper > div#footer-social-mobile > a div#footer-links > div#footer-social-wrapper > div#footer-social-mobile > a
div#footer-links > div#footer-social-wrapper > div#footer-social-mobile > a div#footer-links > div#footer-social-wrapper > div#footer-social-mobile > 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.

○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
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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
○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.
○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.
○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
Heading Hierarchy
32 headings, 1 skip(s)
PASS
32 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WordPress Privacy Compliance Made Easy
  • H2 Finally, a WordPress Cookie Consent Plugin that’s both Easy and Powerful
  • H3 Customizable Cookie Banner
  • H3 Granular Cookie Control
  • H3 Records of User Consent
  • H3 Automatic Script Blocking
  • H3 Advanced Website Scanning
  • H3 Fully Self-Hosted
  • H3 Smart Geolocation Detection
  • H3 Powerful Integrations
  • H3 Automatic Scanning
  • H2 What our users say about us
  • H2 Top 7 Reasons Why Businesses Love ♥ WPConsent
  • H3 Create Smart Cookie Consent Banners in Minutes, Not Hours
  • H3 Automatic Script Blocking for Better Privacy Compliance
  • H3 Comprehensive User Consent Record Logs and Management in One Place
  • H3 Smart Geolocation Detection for an Optimized User Experience
  • H3 Advanced WordPress Privacy Features That Adapt to Your Needs
  • H3 Fully Self-Hosted Like It Should Be for Privacy Conscious Businesses
  • H3 World-Class Customer Support From an Expert Team
  • H3 Make Your WordPress Site Privacy Compliant
  • H2 Frequently Asked Questions
  • H2 Need Help Improving Your WordPress Website?
  • H4 7 Best Cookiebot Alternatives for WordPress (2026 Compared) skipped
  • H4 CookieYes vs. WPConsent: Which is Best for WordPress in 2026? (Compared)
  • H4 Introducing WPConsent 1.1.4 – Auto Scan Alerts, Scan History, Geo-Targeted Content Blocking & More
  • H3 Get the #1 Most Powerful WordPress Consent Management Plugin Today
  • H3 Company
  • H3 Key Features
  • H3 Integrations
  • H3 Helpful Links
  • H3 Connect with us

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

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#wg69e954c2802dd9.101942401776899266755checkboxEnglishfor/id
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 WordPress Privacy Co…8.37:13.0:1
#000000
#AE9DBF
Pass
h2 Finally, a WordPress…8.37:13.0:1
#000000
#AE9DBF
Pass
h2 What our users say a…8.37:13.0:1
#000000
#AE9DBF
Pass
h2 Top 7 Reasons Why Bu…8.37:13.0:1
#000000
#AE9DBF
Pass
h2 Love8.37:13.0:1
#000000
#AE9DBF
Pass
h2 WPConsent8.37:13.0:1
#000000
#AE9DBF
Pass
h2 Frequently Asked Que…8.37:13.0:1
#000000
#AE9DBF
Pass
h2 Need Help Improving …8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Customizable Cookie …8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Granular Cookie Cont…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Records of User Cons…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Automatic Script Blo…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Advanced Website Sca…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Fully Self-Hosted8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Smart Geolocation De…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Powerful Integration…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Automatic Scanning8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Create Smart Cookie …8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Automatic Script Blo…8.37:13.0:1
#000000
#AE9DBF
Pass
h3 Comprehensive User C…8.37:13.0:1
#000000
#AE9DBF
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.

Send Feedback