Skip to content
https://tradedoubler.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 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::
1 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 1 <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
Alt Text Quality
5 of 55 images have issues
REVIEW
5 of 55 images have issues
Warning::
4 image(s) with filename as alt text
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
49 image(s) with good alt text
55 images 49 good alt text 1 decorative 5 generic
IssueCount
filename4 image(s)
generic1 image(s)
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 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 24 passed
REVIEW
86

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
About cookies on this site We use cookies to enhance your browsing experience,… body.device-mobile-optimized > div.ch2 > div.ch2-container > div#ch2-dialog

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Antonio Matijevic, Head of Partner Development div > div.item-link-wrapper > div#pgiedc665f81de44101a85938c8bec0a8b6_0 > div#item-action-edc665f8-1de4-4101-a859-38c8bec0a8b6
Ignacio Maldonado Garcia div > div.item-link-wrapper > div#pgi47a7c5e70a334a168ca83cd3bed8c78f_0 > div#item-action-47a7c5e7-0a33-4a16-8ca8-3cd3bed8c78f

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
Allow all div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn
Deny all div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn

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 > div > div#comp-m0dpwfxb > a.aeyn4z div > div > div#comp-m0dpwfxb > a.aeyn4z
div > div > div#comp-m0dosabq > a.aeyn4z div > div > div#comp-m0dosabq > a.aeyn4z
div > div > div#comp-m0dosabq7 > a.aeyn4z div > div > div#comp-m0dosabq7 > a.aeyn4z
div > div > div#comp-m0donala5 > a.aeyn4z div > div > div#comp-m0donala5 > a.aeyn4z
div > div > div#comp-m0dotss96 > a.aeyn4z div > div > div#comp-m0dotss96 > a.aeyn4z
div > div > div#comp-m0dotssa3 > a.aeyn4z div > div > div#comp-m0dotssa3 > a.aeyn4z
div > div > div#comp-m0dou277 > a.aeyn4z div > div > div#comp-m0dou277 > a.aeyn4z
div > div > div#comp-m0dou2784 > a.aeyn4z div > div > div#comp-m0dou2784 > a.aeyn4z
div > div > div#comp-m0doz8q6 > a.aeyn4z div > div > div#comp-m0doz8q6 > a.aeyn4z
div > div > div#comp-m0doz8q67 > a.aeyn4z div > div > div#comp-m0doz8q67 > a.aeyn4z
div > div > div#comp-m0dozh941 > a.aeyn4z div > div > div#comp-m0dozh941 > a.aeyn4z
div > div > div#comp-m0dq2i95 > a.aeyn4z div > div > div#comp-m0dq2i95 > a.aeyn4z
div > div > div#comp-m0nucwmq1 > a.aeyn4z div > div > div#comp-m0nucwmq1 > a.aeyn4z
div > div > div#comp-m0nucwmx > a.aeyn4z div > div > div#comp-m0nucwmx > a.aeyn4z
div > div > div#comp-m0nucwmz1 > a.aeyn4z div > div > div#comp-m0nucwmz1 > a.aeyn4z
div > div > div#comp-m0nucwn11 > a.aeyn4z div > div > div#comp-m0nucwn11 > a.aeyn4z
div > div > div#comp-m0nucwne > a.aeyn4z div > div > div#comp-m0nucwne > a.aeyn4z
div > div > div#comp-m0nucwnf1 > a.aeyn4z div > div > div#comp-m0nucwnf1 > a.aeyn4z
div > div > div#comp-m0nucwng8 > a.aeyn4z div > div > div#comp-m0nucwng8 > a.aeyn4z
div > div > div#comp-m0nucwnp2 > a.aeyn4z div > div > div#comp-m0nucwnp2 > a.aeyn4z
div > div > div#comp-m0nucwnr1 > a.aeyn4z div > div > div#comp-m0nucwnr1 > a.aeyn4z
div > div > div#comp-m0nucwns7 > a.aeyn4z div > div > div#comp-m0nucwns7 > a.aeyn4z
div > div > div#comp-m0nucwnu > a.aeyn4z div > div > div#comp-m0nucwnu > a.aeyn4z

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
●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.
●`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
●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
●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
●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 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.
○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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV "Site" 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

A+
Heading Hierarchy
28 headings
PASS
28 headings
Info::
Single H1 present
  • H1 Boosting
  • H2 partnerships
  • H2 since 1999
  • H2 We empower a thriving partner network where everyone wins.
  • H2 1999
  • H2 90
  • H2 USA
  • H2 3,000
  • H2 Get ready, America.
  • H2 Our Products
  • H3 Partner Programs
  • H3 Influencer Programs
  • H3 SaaS Partner Marketing
  • H3 White Label / Inhouse
  • H3 Lead Generation
  • H3 App Marketing
  • H3 For Brands
  • H3 For Publishers & Creators
  • H3 For Agencies
  • H2 What our Partners say about us.
  • H2 Our Markets. Your Potential.
  • H2 What's happening on our Blog
  • H2 How bonprix Combined Premium Visibility with 100%+ Growth
  • H2 Unlocking Retail Media: Tradedoubler co-founds Bridge Retail Media
  • H2 Welcome to Tradedoubler
  • H3 Brands
  • H3 Publishers & Creators
  • H3 Agencies
A+
Form Accessibility
All 14 controls labeled
PASS
All 14 controls labeled
Info::
14 control(s) properly labeled
14 controls
14 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#c2-c-1checkboxfor/id
#c2-c-2checkboxfor/id
#c2-c-3checkboxfor/id
#c2-c-4checkboxfor/id
#c2-vv-516checkboxfor/id
#c2-v-sv-516-2checkboxfor/id
#c2-vv-1100checkboxfor/id
#c2-v-sv-1100-1checkboxfor/id
#c2-vv-942checkboxfor/id
#c2-v-sv-942-4checkboxfor/id
#c2-vv-1038checkboxfor/id
#c2-v-sv-1038-18checkboxfor/id
#c2-vv-873checkboxfor/id
#c2-v-sv-873-3checkboxfor/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
h2 We empower a thrivin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 199921.00:13.0:1
#000000
#FFFFFF
Pass
h2 3,00021.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get ready, America.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Products21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What our Partners sa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Markets.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Potential.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's happening on …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How bonprix Combined…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlocking Retail Med…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Welcome to Tradedoub…21.00:13.0:1
#000000
#FFFFFF
Pass
title Tradedoubler | Boost…21.00:14.5:1
#000000
#FFFFFF
Pass
span top of page21.00:14.5:1
#000000
#FFFFFF
Pass
button Skip to Main Content21.00:14.5:1
#000000
#FFFFFF
Pass
p For Brands19.02:14.5:1
#000000
#EEF4FF
Pass
a Overview17.84:14.5:1
#000000
#E4EDFE
Pass
a Partner Programs21.00:14.5:1
#000000
#FFFFFF
Pass
a Influencer Marketing21.00:14.5:1
#000000
#FFFFFF
Pass
a SaaS (Grow)21.00:14.5:1
#000000
#FFFFFF
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