Accessibility

F

Heading Hierarchy

Action

25 headings, 4 skip(s)

FIX

25 headings, 4 skip(s)

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Driving Performance, Elevating Outcomes
H2 Maximize Your ROI with Outbrain Direct Response
H5 Data Never Lies. Neither Do Our Partners. skipped
H1 +35% duplicate H1
H1 -90% duplicate H1
H1 -15% duplicate H1
H2 Nearly Two Decades of Defining Performance Standards.
H6 Customer-Centricity skipped
H6 Agility & Flexibility
H6 Data-Driven Results
H6 Seamless Integration
H2 Continuity Meets Innovation.
H5 It's the same commitment, amplified. skipped
H6 Léo Hauet & Kilian Le Menestrel
H6 Linda Wan
H6 Don Chen
H6 Léo Hauet & Kilian Le Menestrel
H6 Linda Wan
H2 Start Now
H6 Create your campaign with an Outbrain expert. skipped
H2 Advertisers
H2 Insights
H2 Performance
H2 Company
H2 Resources

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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)

Skip navigation link detected

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.

B

Link & Button Quality

1 issue(s) across 70 links and 3 buttons

REVIEW

1 issue(s) across 70 links and 3 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.outbrain.com/blog/outbrain-direct-response-odr-defining-performance/ ("Read More")

11 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.teads.com/?utm_source=outbrain&utm_medium=internal-referral&utm_c…; https://www.teads.com/?utm_source=outbrain&utm_medium=internal-referral&utm_c…; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://www.linkedin.com/showcase/outbrain-direct-response; https://www.facebook.com/OutbrainDirectResponse; https://www.youtube.com/playlist?list=PLeEpXoN2sZ42FQSvjld_2h3G8m61LbHud; https://t.me/outbrain_direct_response (+1 more)

58 link(s) with descriptive text

70 links

0 empty

1 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.teads.com/?utm_source=outbra…	Visit Teads Website	new tab	Add '(opens in new tab)' to text
https://www.teads.com/?utm_source=outbra…	Visit Teads Website	new tab	Add '(opens in new tab)' to text
https://my.outbrain.com/amplify/funnel/	Get Started	new tab	Add '(opens in new tab)' to text
https://my.outbrain.com/amplify/funnel/	Get Started	new tab	Add '(opens in new tab)' to text
https://www.outbrain.com/blog/outbrain-d…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Outbrain Direct Response Odr Defining Performance
https://my.outbrain.com/amplify/funnel/	Get Started	new tab	Add '(opens in new tab)' to text
https://my.outbrain.com/amplify/funnel/	Get Started	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/showcase/outbra…	Follow Outbrain on Linked	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/OutbrainDirectR…	Follow Outbrain Direct Respons…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/playlist?list=PL…	Follow Outbrain Direct Respons…	new tab	Add '(opens in new tab)' to text
https://t.me/outbrain_direct_response	Follow Outbrain Direct Respons…	new tab	Add '(opens in new tab)' to text
https://open.spotify.com/show/6yNojFJc4f…	Follow Outbrain Direct Respons…	new tab	Add '(opens in new tab)' to text

61 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.outbrain.com/blog/outbrain-direct-response-odr-defining-performance/ ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.teads.com/?utm_source=outbrain&utm_medium=internal-referral&utm_c…; https://www.teads.com/?utm_source=outbrain&utm_medium=internal-referral&utm_c…; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://my.outbrain.com/amplify/funnel/; https://www.linkedin.com/showcase/outbrain-direct-response; https://www.facebook.com/OutbrainDirectResponse; https://www.youtube.com/playlist?list=PLeEpXoN2sZ42FQSvjld_2h3G8m61LbHud; https://t.me/outbrain_direct_response (+1 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title OOPS! Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

18 icon(s) detected

REVIEW

18 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Web Manifest

PWA-ready

REVIEW

PWA-ready

Meets PWA install criteria

Name present: Outbrain

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Outbrain ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Outbrain Display Mode standalone Icons 1 icon(s)

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Driving

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

32px · bottom of viewport

h1 , Elevating

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

32px · bottom of viewport

h1 +35%

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

32px · bottom of viewport

h1 -90%

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

32px · bottom of viewport

h1 -15%

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

32px · bottom of viewport

h2 with Outbrain Direct Response

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Nearly Two Decades of Defining

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Continuity Meets

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Advertisers

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Insights

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Performance

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Company

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.07:1

#000000

on

#090A1B

needs 3.0:1 (large text)

24px · bottom of viewport

title Outbrain Direct Response to Maximize You…

1.21:1

#000000

on

#19005F

needs 4.5:1 (normal text)

16px · top of page (header area)

p Outbrain Direct Response is a subsidiary…

1.21:1

#000000

on

#19005F

needs 4.5:1 (normal text)

16px · top of page (header area)

p Discover how the

1.21:1

#000000

on

#19005F

needs 4.5:1 (normal text)

16px · top of page (header area)

a new Teads

1.06:1

#000000

on

#060A15

needs 4.5:1 (normal text)

16px · top of page (header area)

delivers elevated outcomes following the merger o…

1.06:1

#000000

on

#060A15

needs 4.5:1 (normal text)

16px · above the fold

p Discover how the new Teads delivers elev…

1.27:1

#000000

on

#2B1923

needs 4.5:1 (normal text)

16px · above the fold

a Visit Teads Website

1.22:1

#000000

on

#261622

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Driving	1.07:1	3.0:1	#000000	#090A1B	Fail
h1 , Elevating	1.07:1	3.0:1	#000000	#090A1B	Fail
h1 +35%	1.07:1	3.0:1	#000000	#090A1B	Fail
h1 -90%	1.07:1	3.0:1	#000000	#090A1B	Fail
h1 -15%	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 with Outbrain Direct…	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Nearly Two Decades o…	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Continuity Meets	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Advertisers	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Insights	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Performance	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Company	1.07:1	3.0:1	#000000	#090A1B	Fail
h2 Resources	1.07:1	3.0:1	#000000	#090A1B	Fail
title Outbrain Direct Resp…	1.21:1	4.5:1	#000000	#19005F	Fail
p Outbrain Direct Resp…	1.21:1	4.5:1	#000000	#19005F	Fail
p Discover how the	1.21:1	4.5:1	#000000	#19005F	Fail
a new Teads	1.06:1	4.5:1	#000000	#060A15	Fail
delivers elevated outcomes fo…	1.06:1	4.5:1	#000000	#060A15	Fail
p Discover how the new…	1.27:1	4.5:1	#000000	#2B1923	Fail
a Visit Teads Website	1.22:1	4.5:1	#000000	#261622	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 89/100 — 4 failing, 27 passed

REVIEW

89

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 Advertisers Ads Specs Buy Your Way Advertiser Guidelines Advertisin… `div.footer-top-inner > div.footer-menu-links > div.expandable > div`
Insights Advertising Glossary Vertical Insights Vertical Hub `div.footer-top-inner > div.footer-menu-links > div.expandable > div`
Performance Affiliate Marketing Affiliate Hub High-Conversion Content Repurpose… `div.footer-top-inner > div.footer-menu-links > div.expandable > div`
Company About Us Leadership Join Us Trust & Transparency News Contact Us Partne… `div.footer-top-inner > div.footer-menu-links > div.expandable > div`
Resources Blog Resources Hub Marketing Podcast Case Studies Help Center Partners `div.footer-top-inner > div.footer-menu-links > div.expandable > div`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Affiliate Marketing `div > ul.menu-nav > li > a`
High-Conversion Content `div > ul.menu-nav > li > a`
Repurpose Social Campaigns `div > ul.menu-nav > li > a`

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.

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
Data Never Lies. Neither Do Our Partners. `section.partners > div.partners__inner > div.partners__inner-top > h5`
Customer-Centricity `div.performance-cards > div.performance-cards__item > div.performance-cards__content > h6`
It's the same commitment, amplified. `div.container > div.featured-section__inner > blockquote.featured-section__blockquote > h5`
Create your campaign with an Outbrain expert. `section.bottom-cta > div.bottom-cta__inner > div.bottom-cta__inner-right > h6`

These are opportunities to improve keyboard navigation in your application.

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
new Teads `div.content > div.text > p.mobile-only > a`
Outbrain’s Privacy Policy. `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

●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

●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.

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Uses ARIA roles only on compatible elements

○`[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.

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

10 decorative image(s) correctly marked

3 image(s) with good alt text

13 images 3 good alt text 10 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.