Skip to content
https://criteo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
9 landmarks
FIX
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
8 <nav> landmark(s) found
Warning::
7 of 8 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV "Main" MAIN (missing!) 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

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

D
Alt Text Quality
Action
8 of 45 images have issues
FIX
8 of 45 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with alt text over 125 characters
Info::
32 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
45 images 3 good alt text 32 decorative 8 missing
IssueCount
missing8 image(s)
too long2 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
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
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
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::
8 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 8 <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
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found | Criteo Custom Styling Navigation Homepage Link Search Form
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 7 failing, 25 passed
REVIEW
70

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
Advertisers Increase brand visibility and sales div.slick-list > div.slick-track > li.nav-item > a.tab

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Advertisers Increase brand visibility and sales Retailers Control, scale, and m… div.container > div.content > div.pt-st-4 > ul#mobile-slider-tabs

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
By clicking “Accept All Cookies”, you agree to the storing of cookies on your d… div.cmp-wrapper > div#uc-main-dialog

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.

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
body.home > div#page-modular > section#sID-0 > img.hero-bg-grid body.home > div#page-modular > section#sID-0 > img.hero-bg-grid
div.background-wrapper-inner > div.post-inner > div.post-logo > img.logo-slide div.background-wrapper-inner > div.post-inner > div.post-logo > img.logo-slide
div.row > div.col-12 > a > img div.row > div.col-12 > a > 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.container > div.banner-content > span.banner-right > a div.container > div.banner-content > span.banner-right > a
div.header-container > div#global-banner > div.container > a.overlay-link div.header-container > div#global-banner > div.container > a.overlay-link
div.slick-list > div.slick-track > div.solution > a.overlay-link div.slick-list > div.slick-track > div.solution > a.overlay-link
div.post-wrapper > article#post-417529 > div.background-wrapper > a.article-link div.post-wrapper > article#post-417529 > div.background-wrapper > a.article-link
div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link
div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link
div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link
div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link
div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link div.container > div.technologies-wrapper > div.content-box-wrapp > a.overlay-link
div.row > div.col-12 > div.inner-block > a.overlay-link div.row > div.col-12 > div.inner-block > a.overlay-link
div.row > div.col-12 > div.inner-block > a.overlay-link div.row > div.col-12 > div.inner-block > a.overlay-link
div.row > div.col-12 > div.inner-block > a.overlay-link div.row > div.col-12 > div.inner-block > a.overlay-link
div.col-12 > div.social-links > div.social-icons > a div.col-12 > div.social-links > div.social-icons > a
div.col-12 > div.social-links > div.social-icons > a div.col-12 > div.social-links > div.social-icons > a
div.col-12 > div.social-links > div.social-icons > a div.col-12 > div.social-links > div.social-icons > a
div.col-12 > div.social-links > div.social-icons > a div.col-12 > div.social-links > div.social-icons > a
div.row > div.col-12 > div > a.d-block div.row > div.col-12 > div > a.d-block
div.container > div.row > div.col-12 > a div.container > div.row > div.col-12 > 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.

Tables and lists

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
Advertisers Increase brand visibility and sales ul#mobile-slider-tabs > div.slick-list > div.slick-track > li.nav-item
Success Stories div.col-12 > div.footer-menu > ul.mt-4 > li
Agencies div.col-12 > div.footer-menu > ul.mt-4 > li
Marketplace Performance Outcome div.col-12 > div.footer-menu > ul.mt-4 > li
Partners div.col-12 > div.footer-menu > ul.mt-4 > li
Privacy Policy div.col-12 > div.footer-menu > ul.mt-4 > li
CCPA Privacy Policy div.col-12 > div.footer-menu > ul.mt-4 > li
Website Privacy Policy div.col-12 > div.footer-menu > ul.mt-4 > li
Do Not Sell or Share My Personal Information div.col-12 > div.footer-menu > ul.mt-4 > li
Cookie Management div.col-12 > div.footer-menu > ul.mt-4 > li
Privacy Guidelines for Clients and Publisher Partners div.col-12 > div.footer-menu > ul.mt-4 > li
Trust Center div.col-12 > div.footer-menu > ul.mt-4 > li
Security div.col-12 > div.footer-menu > ul.mt-4 > li
Reports & Research div.col-12 > div.footer-menu > ul.mt-4 > li
Blog div.col-12 > div.footer-menu > ul.mt-4 > li
Webinars div.col-12 > div.footer-menu > ul.mt-4 > li
Events div.col-12 > div.footer-menu > ul.mt-4 > li
Developers div.col-12 > div.footer-menu > ul.mt-4 > li
Terms and Conditions div.col-12 > div.footer-menu > ul.mt-4 > li
Legal Mentions div.col-12 > div.footer-menu > ul.mt-4 > li
Supply Partner Guidelines div.col-12 > div.footer-menu > ul.mt-4 > li
Advertising Guidelines div.col-12 > div.footer-menu > ul.mt-4 > li
Supported Platforms div.col-12 > div.footer-menu > ul.mt-4 > li
UK Modern Slavery Act div.col-12 > div.footer-menu > ul.mt-4 > li
Tax Strategy div.col-12 > div.footer-menu > ul.mt-4 > li
Careers div.col-12 > div.footer-menu > ul.mt-4 > li
Company div.col-12 > div.footer-menu > ul.mt-4 > li
Investors div.col-12 > div.footer-menu > ul.mt-4 > li
In the News div.col-12 > div.footer-menu > ul.mt-4 > li
Sustainability div.col-12 > div.footer-menu > ul.mt-4 > li
Diversity, Equity & Inclusion div.col-12 > div.footer-menu > ul.mt-4 > li
Contact Us div.col-12 > div.footer-menu > ul.mt-4 > li
Office Locations div.col-12 > div.footer-menu > ul.mt-4 > li
Retail Media div.col-12 > div.footer-menu > ul.mt-4 > li
Retargeting div.col-12 > div.footer-menu > ul.mt-4 > li
Customer Acquisition div.col-12 > div.footer-menu > ul.mt-4 > li
Display Advertising div.col-12 > div.footer-menu > ul.mt-4 > li
Customer Targeting div.col-12 > div.footer-menu > ul.mt-4 > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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>`
`[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
`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.
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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
Tables have different content in the summary attribute and `<caption>`.
Image elements do not have `[alt]` attributes that are redundant text.
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
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Make every commerce moment smarter.
  • H2 Engage shoppers across their entire journey
  • H2 See the results we helped others achieve
  • H2 Our Award-winning Technology
  • H2 Stay in the know on all things commerce media
  • H2 Turn ads into commerce moments with the Commerce Media Platform
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="searchsubmit">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#stextSearch for:for/id
#search-mobiletextSearch for:for/id
#searchsubmitsubmit(none)none

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

<input type="submit" name="submit" id="searchsubmit">

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

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 Make every commerce …8.81:13.0:1
#000000
#A6A8AB
Pass
h2 Engage shoppers acro…8.81:13.0:1
#000000
#A6A8AB
Pass
h2 See the results we h…8.81:13.0:1
#000000
#A6A8AB
Pass
h2 Our Award-winning Te…8.81:13.0:1
#000000
#A6A8AB
Pass
h2 Stay in the know on …8.81:13.0:1
#000000
#A6A8AB
Pass
h2 Turn ads into commer…8.81:13.0:1
#000000
#A6A8AB
Pass
title The Global Commerce …8.81:14.5:1
#000000
#A6A8AB
Pass
span Meet8.81:14.5:1
#000000
#A6A8AB
Pass
b Criteo GO8.81:13.0:1
#000000
#A6A8AB
Pass
span : smarter advertisin…8.81:14.5:1
#000000
#A6A8AB
Pass
span Learn more8.81:14.5:1
#000000
#A6A8AB
Pass
a Contact Sales8.81:14.5:1
#000000
#A6A8AB
Pass
span Open mobile menu8.33:14.5:1
#000000
#A1A3A9
Pass
span Platform8.81:14.5:1
#000000
#A6A8AB
Pass
span Platform8.41:14.5:1
#000000
#A2A4A8
Pass
span Commerce Media Platf…8.30:14.5:1
#000000
#A1A3A6
Pass
span The connected commer…7.72:14.5:1
#000000
#9B9DA0
Pass
span Commerce Growth7.28:14.5:1
#000000
#97989B
Pass
span For marketers & agen…7.17:14.5:1
#000000
#95979A
Pass
span Criteo GO7.17:14.5:1
#000000
#95979A
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