Skip to content
https://taboola.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
C
Heading Hierarchy
Action
25 headings, 3 skip(s)
REVIEW
25 headings, 3 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: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Performance Beyond Search and Social
  • H2 Outcomes at Scale Beyond Search and Social
  • H3 Advertisers winning with Realize
  • H2 Specialized Performance Not Full Funnel Promises
  • H4 Awareness skipped
  • H4 Consideration
  • H4 Action
  • H3 Your Ads on Trusted Media Properties
  • H2 Advertise Smarter with Tools that Drive Success
  • H6 Ad Experiences that Drive Performance skipped
  • H6 Powerful Performance AI
  • H6 1st Party Audience Targeting Solutions
  • H6 Intuitive and Effective Campaign Management
  • H2 Master Your Digital Marketing
  • H3 Engagement
  • H3 Leads
  • H3 Purchases
  • H3 Measurable Outcomes
  • H2 Advertiser Success Stories
  • H4 eToro Boosts Global Acquisition with Taboola: 30% Conversion Success skipped
  • H4 Bosch Home Appliances Sees Significant Traffic Increase With Taboola
  • H4 Hyundai Achieves 30% Lower Cost per Session with Taboola
  • H4 10,000 Customers in 6 Months: Lifeboost's Success with Taboola
  • H4 Austria Tourism Sees 33% Boost with Taboola
  • H3 Reach your best audience at the lowest cost!

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

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
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">; <input type="checkbox">; <input type="checkbox">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none

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

<input type="checkbox">; <input type="checkbox">; <input type="checkbox">

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Taboola.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
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
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only
h3 Reach your best audience at the lowest …
2.42:1
#000000
on
#005645
needs 3.0:1 (large text)
19px · bottom of viewport
title Boost your Digital Performance with Tabo…
1.43:1
#000000
on
#002852
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Footer
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
p Don’t let LLMs summarize your journali…
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Launch your own AI answer experience wit…
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Advertisers
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Publishers
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Taboola News
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Company
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Our Story
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Taboola Updates
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · above the fold
a Social Responsibility
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
a Careers
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
a Offices
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
a Taboola Life
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
a Press Center
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
a Management
2.42:1
#000000
on
#005645
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Reach your best audi…2.42:13.0:1
#000000
#005645
Fail
title Boost your Digital P…1.43:14.5:1
#000000
#002852
Fail
div Popup heading4.72:14.5:1
#000000
#627A93
Pass
button Close21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to Main Content10.12:14.5:1
#000000
#99BBB4
Pass
a Skip to Footer2.42:14.5:1
#000000
#005645
Fail
p Don’t let LLMs sum…2.42:14.5:1
#000000
#005645
Fail
a Launch your own AI a…2.42:14.5:1
#000000
#005645
Fail
a Advertisers2.42:14.5:1
#000000
#005645
Fail
a Publishers2.42:14.5:1
#000000
#005645
Fail
a Taboola News2.42:14.5:1
#000000
#005645
Fail
a Company2.42:14.5:1
#000000
#005645
Fail
a Our Story2.42:14.5:1
#000000
#005645
Fail
a Taboola Updates2.42:14.5:1
#000000
#005645
Fail
a Social Responsibilit…2.42:14.5:1
#000000
#005645
Fail
a Careers2.42:14.5:1
#000000
#005645
Fail
a Offices2.42:14.5:1
#000000
#005645
Fail
a Taboola Life2.42:14.5:1
#000000
#005645
Fail
a Press Center2.42:14.5:1
#000000
#005645
Fail
a Management2.42:14.5:1
#000000
#005645
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 87/100 — 4 failing, 26 passed
REVIEW
87

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
2X Avg. Session Duration div.col-md-12 > div.logo-group > div.logo-wrap > p.text-color-mint
+30% Purchase Intent div.col-md-12 > div.logo-group > div.logo-wrap > p.text-color-mint
Purchase Intent div.logo-group > div.logo-wrap > p.text-color-mint > span.text-color-white
-42% Cost per Sale div.col-md-12 > div.logo-group > div.logo-wrap > p.text-color-mint
Cost per Sale div.logo-group > div.logo-wrap > p.text-color-mint > span.text-color-white
Awareness div.col-12 > div.funnel-gray > div.funnel-content > h4.text-color-gray-400
Viewable Impressions div.col-12 > div.funnel-gray > div.funnel-content > span.text-color-gray-400

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Press for Accessibility for blind people who use screen readers div#INDquickAccess > ul > li > button.INDshortcutBtn
Press for Accessibility menu div#INDquickAccess > ul > li > button

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
Awareness div.col-12 > div.funnel-gray > div.funnel-content > h4.text-color-gray-400
Ad Experiences that Drive Performance div.row > div.col-12 > div.ms-4 > h6.mb-1
eToro Boosts Global Acquisition with Taboola: 30% Conversion Success div.col-12 > div.row > div.col-md-12 > h4.mt-4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.menu-main-menu-container > ul#menu-main-menu > li.has-dropdown > input.dropdown-toggle div.menu-main-menu-container > ul#menu-main-menu > li.has-dropdown > input.dropdown-toggle
div.menu-main-menu-container > ul#menu-main-menu > li.has-dropdown > input.dropdown-toggle div.menu-main-menu-container > ul#menu-main-menu > li.has-dropdown > input.dropdown-toggle
nav.site-header__main-nav > ul.d-inline-block > li.has-dropdown > input.dropdown-toggle nav.site-header__main-nav > ul.d-inline-block > li.has-dropdown > input.dropdown-toggle

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.
●`[accesskey]` values are unique
●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 have a discernible name
●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.
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main Navigation" MAIN CONTENTINFO footer
A
Alt Text Quality
6 of 64 images have issues
PASS
6 of 64 images have issues
Warning::
6 image(s) with generic alt text
Info::
36 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
64 images 22 good alt text 36 decorative 6 generic
IssueCount
generic6 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback