Skip to content
https://liftoff.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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::
1 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 1 <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
Heading Hierarchy
31 headings, 2 skip(s)
REVIEW
31 headings, 2 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.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 FEATURED
  • H6 FEATURED
  • H1 Close the creative gap with Liftoff at MAU
  • H2 Discover next-gen performance with Cortex™
  • H2 Our products
  • H3 Accelerate
  • H4 Accelerate acquires 
the best users for your app
  • H3 Monetize
  • H4 Monetize maximizes earnings for your app
  • H3 Vungle Exchange
  • H4 Vungle Exchange increases your programmatic reach
  • H3 Creative
  • H4 Creative crafts ads that deliver high impact
  • H3 Intelligence
  • H4 Intelligence powers smarter mobile growth
  • H2 What Our Customers Say
  • H4 “Over the past year, we migrated many of our campaigns to Liftoff’s next-generation AI-enabled platform, Cortex. The impact has been game-changing.” skipped
  • H4 “The results of buying non-personalized traffic at scale with Liftoff are encouraging, giving us confidence in our continued investment in programmatic. With the release of iOS 14, our long-term par
  • H4 “At Badoo we look at the retention of users as one of the most important metrics for determining quality. Liftoff understands how to acquire these high-quality users at scale.”
  • H4 “Our goal was to improve our volume of new customers by keeping a stable performance. Together with Liftoff, we were able to achieve this. The Liftoff team has extensive industry knowledge and are a
  • H4 “The LTVs of Liftoff users are on par with some of the better social media channels as well. So it’s been a very fruitful partnership that we would like to invest more into in the future.”
  • H2 What’s new at Liftoff
  • H3 The iGaming Marketer’s Guide to Mobile User Acquisition
  • H3 Introducing AppRefinery: Liftoff’s Exclusive Platform for Consumer App Insights
  • H3 New Mobile Hero: Ravid Sela from Playstudios
  • H3 Ready for Liftoff?Getting started is easy.
  • H3 Products
  • H3 Solutions
  • H3 Resources
  • H3 Company
  • H6 © 2025 Liftoff, Inc. skipped

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

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

C
Alt Text Quality
Action
5 of 37 images have issues
REVIEW
5 of 37 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
23 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
37 images 9 good alt text 23 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

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

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

18 pass 2 fail WCAG AA
a Cookies settings
1.61:1
#000000
on
#273143
needs 4.5:1 (normal text)
16px · top of page (header area)
a Accept All
1.61:1
#000000
on
#273143
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Close the creative g…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover next-gen pe…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our products21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What Our Customers S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What’s new at Lift…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Accelerate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Monetize21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vungle Exchange21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Creative21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Intelligence21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The iGaming Marketer…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Introducing AppRefin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New Mobile Hero: Rav…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ready for Liftoff?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Getting started is e…21.00:13.0:1
#000000
#FFFFFF
Pass
title The Leading Growth A…21.00:14.5:1
#000000
#FFFFFF
Pass
p This website stores …21.00:14.5:1
#000000
#FFFFFF
Pass
p If you decline, your…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cookies settings1.61:14.5:1
#000000
#273143
Fail
a Accept All1.61:14.5:1
#000000
#273143
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 7 failing, 20 passed
REVIEW
75

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

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
VEGAS div#animation > svg > g > g#1362

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > button.lf-block--testimonial-card--playbtn div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > button.lf-block--testimonial-card--playbtn
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > button.lf-block--testimonial-card--playbtn div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > button.lf-block--testimonial-card--playbtn

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.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero
div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero div.lf-block--testimonials--content > div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > img.lf-block--testimonial-card--hero

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#lf-footer > div.footer-container > div.brand-logo-container > a div#lf-footer > div.footer-container > div.brand-logo-container > 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.

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
First name form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_firstname > label#label-firstname-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > span
Last name form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_lastname > label#label-lastname-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > span
Company name form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_company > label#label-company-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > span
Email form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_email > label#label-email-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > span
© 2025 LIFTOFF, INC. div#lf-footer > div.footer-container > div.bottom-container > h6.company

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
“Over the past year, we migrated many of our campaigns to Liftoff’s next-genera… div.lf-block--testimonials--cards > div.wp-block-liftoff-blocks-testimonial-card > div.lf-block--testimonial-card--content > h4.wp-block-heading
© 2025 LIFTOFF, INC. div#lf-footer > div.footer-container > div.bottom-container > h6.company

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_submit > div.actions > input.hs-button form#hsForm_0bc5e290-a389-4e3b-9ae9-b3ab78d27e5d > div.hs_submit > div.actions > input.hs-button

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-*]` 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
●Input buttons have discernible text.
●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.
●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
●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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 type="image">` elements have `[alt]` text
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`<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
12 landmarks
PASS
12 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 "Main menu" 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
Form Accessibility
1 of 11 controls have issues
PASS
1 of 11 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">
Info::
10 control(s) properly labeled
11 controls
10 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
ssearchSearch for:none
search-buttonsubmitsearch buttonaria-label
#firstname-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5dtextFirst name*for/id
#lastname-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5dtextLast name*for/id
#company-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5dtextCompany name*for/id
#email-0bc5e290-a389-4e3b-9ae9-b3ab78d27e5demailEmail*for/id
inputsubmit(none)none

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

<input type="submit">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback