Skip to content
https://iubenda.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 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::
7 <nav> landmark(s) found
Warning::
1 of 7 <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 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

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 | iubenda ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Built for compliance.
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Designed for growth.
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
32px · bottom of viewport
h2 You’re in good company
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Clear compliance for confident growth
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Complex laws. Simple compliance.
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Controls and Cookie Solution
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy and Cookie Policy Generator
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Terms and Conditions Generator
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Accessibility Widget
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Advanced Solutions
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why iubenda?
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Global laws, one platform
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The word on iubenda
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your questions, answered
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Set up in minutes. Scale with confidence…
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Support included
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Check your compliance
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
19px · bottom of viewport
h3 in seconds
2.01:1
#000000
on
#2B1EBB
needs 3.0:1 (large text)
19px · bottom of viewport
title Compliance Solutions for Websites, Apps …
2.01:1
#000000
on
#2B1EBC
needs 4.5:1 (normal text)
16px · top of page (header area)
span English
2.02:1
#000000
on
#2B1EBD
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Built for compliance…2.01:13.0:1
#000000
#2B1EBB
Fail
h1 Designed for growth.2.01:13.0:1
#000000
#2B1EBB
Fail
h2 You’re in good com…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Clear compliance for…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Complex laws. Simple…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Privacy Controls and…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Privacy and Cookie P…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Terms and Conditions…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Accessibility Widget2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Advanced Solutions2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Why iubenda?2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Global laws, one pla…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 The word on iubenda2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Your questions, answ…2.01:13.0:1
#000000
#2B1EBB
Fail
h2 Set up in minutes. S…2.01:13.0:1
#000000
#2B1EBB
Fail
h3 Support included2.01:13.0:1
#000000
#2B1EBB
Fail
h3 Check your complianc…2.01:13.0:1
#000000
#2B1EBB
Fail
h3 in seconds2.01:13.0:1
#000000
#2B1EBB
Fail
title Compliance Solutions…2.01:14.5:1
#000000
#2B1EBC
Fail
span English2.02:14.5:1
#000000
#2B1EBD
Fail

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 85/100 — 3 failing, 19 passed
REVIEW
85

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EN div.wpml-ls-dropdown > ul.wp-block-navigation__container > li.wp-block-navigation-item > div.wp-block-navigation-item__content

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
Trustpilot div.wp-block-group > div > div.trustpilot-widget > a

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.wp-block-column > div.wp-block-group > figure.wp-block-image > a div.wp-block-column > div.wp-block-group > figure.wp-block-image > 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-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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.
○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.
○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
16 headings
PASS
16 headings
Info::
Single H1 present
  • H1 Built for compliance.Designed for growth.
  • H2 You’re in good company
  • H2 Clear compliance for confident growth
  • H2 Complex laws. Simple compliance.
  • H2 Privacy Controls and Cookie Solution
  • H2 Privacy and Cookie Policy Generator
  • H2 Terms and Conditions Generator
  • H2 Accessibility Widget
  • H2 Advanced Solutions
  • H2 Why iubenda?
  • H3 Support included
  • H3 Check your compliance in seconds
  • H2 Global laws, one platform
  • H2 The word on iubenda
  • H2 Your questions, answered
  • H2 Set up in minutes. Scale with confidence.
A+
Alt Text Quality
All 82 images OK
PASS
All 82 images OK
Info::
28 decorative image(s) correctly marked
Info::
54 image(s) with good alt text
82 images 54 good alt text 28 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback