Skip to content
https://moloco.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://moloco.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://moloco.com/manifest.json

Manifest contains invalid JSON.

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::
10 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 10 <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.
C
Landmark Structure
Action
15 landmarks
REVIEW
15 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
10 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) 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 header NAV "w-dropdown-toggle-0" MAIN (missing!) CONTENTINFO (missing!)

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

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 Not Found Custom Styling Navigation Homepage Link Search Form
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The future of advert…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 with ads in 3 millio…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 that delivers what l…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 of every ad impressi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Moloco Ads21.00:13.0:1
#000000
#FFFFFF
Pass
h2 with ads in 3 millio…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Moloco Commerce Medi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 that delivers what l…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Moloco Streaming Mon…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 of every ad impressi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by the world…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Powered by21.00:13.0:1
#000000
#FFFFFF
Pass
h2 machine learning21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's new at Moloco21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stay up to date21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Moloco - Grow, scale…5.24:14.5:1
#000000
#7F7F7F
Pass
a English21.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.

A
Heading Hierarchy
90 headings, 1 skip(s)
PASS
90 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Solutions
  • H5 Solutions
  • H5 Moloco Ads
  • H5 Reach 2 billion daily users on the advertising platform built for app marketers
  • H5 Moloco Performance CTV
  • H5 Drive app installs and outcomes from the tv screen
  • H5 Moloco SDK
  • H5 Improve app monetization with a direct Moloco integration
  • H5 Moloco Commerce Media
  • H5 AI-powered onsite ads for retailers
  • H5 Moloco Streaming Monetization
  • H5 The AI-native ad stack for large streaming providers
  • H5 Resources
  • H5 resources
  • H5 Blog
  • H5 Reports
  • H5 Case Studies
  • H5 Events
  • H5 Moloco Help Center
  • H5 Moloco Ads Developer Hub
  • H5 Commerce Media Developer Hub
  • H5 Company
  • H5 company
  • H5 About Moloco
  • H5 Careers
  • H5 Newsroom
  • H5 Solutions
  • H5 Moloco Ads
  • H5 Reach 2 billion daily users on the advertising platform built for app marketers
  • H5 Moloco Performance CTV
  • H5 Drive app installs and outcomes from the tv screen
  • H5 Moloco SDK
  • H5 Improve app monetization with a direct Moloco integration
  • H5 Moloco Commerce Media
  • H5 AI-powered onsite ads for retailers
  • H5 Moloco Streaming Monetization
  • H5 The AI-native ad stack for large streaming providers
  • H5 Resources
  • H5 Blog
  • H5 Reports
  • H5 Case Studies
  • H5 Events
  • H5 Moloco Help Center
  • H5 Moloco Ads Developer Hub
  • H5 Commerce Media Developer Hub
  • H5 Company
  • H5 About Moloco
  • H5 Careers
  • H5 Newsroom
  • H1 The future of advertising is powered by AI
  • H2 Grow your app with ads in 3 million independent apps
  • H2 Real-time AI that delivers what legacy systems can’t
  • H2 Make the most of every ad impression
  • H2 Moloco Ads
  • H2 Grow your app with ads in 3 million independent apps.
  • H2 Moloco Commerce Media
  • H2 Real-time AI that delivers what legacy systems can’t
  • H2 Moloco Streaming Monetization
  • H2 Make the most of every ad impression
  • H2 Trusted by the world's biggest brands
  • H2 Powered by advanced machine learning
  • H2 What's new at Moloco
  • H2 Stay up to date
  • H5 Moloco Ads skipped
  • H5 Moloco Performance CTV
  • H5 Moloco SDK
  • H5 Moloco Commerce Media
  • H5 Moloco Streaming Monetization
  • H5 For Agency Partners
  • H5 About Moloco
  • H5 Blog
  • H5 Careers
  • H5 Newsroom
  • H5 Help Center
  • H5 Moloco Ads Developer Hub
  • H5 Commerce Media Developer Hub
  • H5 Suppliers
  • H5 Privacy Policy
  • H5 Brand Safety Policy
  • H5 Advertising Policy
  • H5 Terms of Use
  • H5 Security
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Functional Cookies
  • H4 Share Or Sale of Personal Data
  • H5 Performance Cookies
  • H5 Targeting Cookies
  • H4 Strictly Necessary Cookies
  • H3 Cookie List

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+
Alt Text Quality
All 83 images OK
PASS
All 83 images OK
Info::
14 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
83 images 69 good alt text 14 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 10 controls have issues
PASS
1 of 10 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="0-1/email" id="683985db-f3da-43b4-bba2-d81ed0202439-3-input">
Info::
9 control(s) properly labeled
10 controls
9 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-SSPD_BGcheckboxShare Or Sale of Personal Datafor/id
#ot-sub-group-id-C0002checkboxPerformance Cookiesaria-label
#ot-sub-group-id-C0004checkboxTargeting Cookiesaria-label
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#683985db-f3da-43b4-bba2-d81ed0202439-3-inputemail(Enter your email to get the latest news*)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="0-1/email" id="683985db-f3da-43b4-bba2-d81ed0202439-3-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A
Lighthouse Accessibility Audits
Score 94/100 — 3 failing, 29 passed
PASS
94

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
Real-time AI div.w-layout-blockcontainer > div.mobile-overview-commerce-media > h2.is-semibold > span.is-bright-blue
Make the most div.w-layout-blockcontainer > div.mobile-overview-streaming > h2.is-semibold > span.is-teal
SUBSCRIBE div.hsfc-Step__Content > div#b152c1fc-1f17-47dc-aea4-591e10306a58-22 > div#b152c1fc-1f17-47dc-aea4-591e10306a58-22-b > button#b152c1fc-1f17-47dc-aea4-591e10306a58-15
GET STARTED div.column-3x1 > div#w-node-f4dcf613-9b09-fc68-804a-6105289cee5f-3d28a861 > a.button-primary > div.button-text-secondary-white-text-2

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.footer-width > div.column-3x1 > div#w-node-_12c2df38-e0ff-a436-4a58-c38a3d28a8b2-3d28a861 > a.link-block-social-media div.footer-width > div.column-3x1 > div#w-node-_12c2df38-e0ff-a436-4a58-c38a3d28a8b2-3d28a861 > a.link-block-social-media
div.footer-width > div.column-3x1 > div#w-node-_12c2df38-e0ff-a436-4a58-c38a3d28a8b2-3d28a861 > a.link-block-social-media div.footer-width > div.column-3x1 > div#w-node-_12c2df38-e0ff-a436-4a58-c38a3d28a8b2-3d28a861 > a.link-block-social-media

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GET STARTED div.footer-width > div.column-3x1 > div#w-node-f4dcf613-9b09-fc68-804a-6105289cee5f-3d28a861 > a.button-primary
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
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
`[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
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
Links are distinguishable without relying on color.
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
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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.
`<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.
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