Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

23 landmarks

FIX

23 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

12 <nav> landmark(s) found

2 of 12 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

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

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

Form Accessibility

Action

13 of 13 controls have issues

FIX

13 of 13 controls have issues

6 control(s) without accessible label

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

Got: <select name="Country-2" id="Country-2">; <select name="I-am-a-2" id="I-am-a-2">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-1">; <input type="submit">

7 control(s) rely on placeholder only

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

Got: <input type="text" name="First-Name-3" id="First-Name-3">; <input type="text" name="Last-Name-5" id="Last-Name-5">; <input type="text" name="Company-2" id="Company-2">; <input type="email" name="Email-8" id="Email-8">; <textarea name="field-2" id="field-2">; <input type="text" name="ipFormInput" id="ipFormInput">; <input type="email" name="Email-6" id="Email-6">

13 controls

0 labeled

7 placeholder only

6 unlabeled

Control	Type	Label	Method
#First-Name-3	text	(First Name*)	placeholder only
#Last-Name-5	text	(Last Name*)	placeholder only
#Company-2	text	(Company*)	placeholder only
#Email-8	email	(Work Email*)	placeholder only
#field-2	textarea	(Type your message here...)	placeholder only
#ipFormInput	text	(Example Text)	placeholder only
#Email-6	email	(Email)	placeholder only
input	submit	(none)	none
#g-recaptcha-response	textarea	(none)	none
#I-am-a-2	select	(none)	none
#Country-2	select	(none)	none
#g-recaptcha-response-1	textarea	(none)	none
input	submit	(none)	none

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

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

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

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

Link & Button Quality

Action

9 issue(s) across 136 links and 3 buttons

FIX

9 issue(s) across 136 links and 3 buttons

9 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; https://adnetzero.com/; https://www.scope3.com/; https://sciencebasedtargets.org/; https://www.51tocarbonzero.com/; https://www.linkedin.com/company/sharethrough/; https://www.facebook.com/sharethrough/; https://twitter.com/sharethrough; https://www.instagram.com/sharethrough/

9 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="#"]; a[href="#"]; a[href="#"]; a[href="#"]; a#weglot-language-en; a#weglot-language-fr; a#weglot-language-de; a#weglot-language-ru; a#weglot-language-es

18 link(s) open in new tab without warning

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

Got: https://equativ.com/press/equativ-and-sharethrough-will-now-operate-under-equ…; https://support.sharethrough.com/hc/en-us; https://headlines.sharethrough.com/; https://generator.sharethrough.com/; https://support.sharethrough.com/hc/en-us; https://pubmaestro.sharethrough.com; https://support.sharethrough.com/hc/en-us; https://pubmaestro.sharethrough.com; https://www.sharethrough.com/blog/sharethrough-and-equativ-are-merging; https://www.sharethrough.com/blog/sharethrough-and-equativ-are-merging (+8 more)

100 link(s) with descriptive text

136 links

9 empty

0 generic text

18 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://equativ.com/press/equativ-and-sh…	Learn More →	new tab	Add '(opens in new tab)' to text
https://support.sharethrough.com/hc/en-u…	Support ↗	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://headlines.sharethrough.com/	Headline Analyzer ↗	new tab	Add '(opens in new tab)' to text
https://generator.sharethrough.com/	Ad Generator ↗	new tab	Add '(opens in new tab)' to text
https://support.sharethrough.com/hc/en-u…	Support ↗	new tab	Add '(opens in new tab)' to text
https://pubmaestro.sharethrough.com	Log in	new tab	Add '(opens in new tab)' to text
https://support.sharethrough.com/hc/en-u…	Support	new tab	Add '(opens in new tab)' to text
https://pubmaestro.sharethrough.com	Publishers (PubMaestro)	new tab	Add '(opens in new tab)' to text
https://www.sharethrough.com/blog/sharet…	Learn More →	new tab	Add '(opens in new tab)' to text
https://www.sharethrough.com/blog/sharet…	Learn More →	new tab	Add '(opens in new tab)' to text
#	Best Video Ad Tech Innovation	img no alt	Add alt attribute to the image
#	Best Use of Video	img no alt	Add alt attribute to the image
https://adnetzero.com/	(empty)	empty	Add link text or aria-label
https://www.scope3.com/	(empty)	empty	Add link text or aria-label
https://sciencebasedtargets.org/	(empty)	empty	Add link text or aria-label
https://www.51tocarbonzero.com/	(empty)	empty	Add link text or aria-label
#	Best Sustainable Ad Tech Platf…	img no alt	Add alt attribute to the image
#	Best Sustainable Initiative	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/shareth…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/sharethrough/	(empty)	empty	Add link text or aria-label
https://twitter.com/sharethrough	(empty)	empty	Add link text or aria-label
https://www.instagram.com/sharethrough/	(empty)	empty	Add link text or aria-label
https://support.sharethrough.com/hc/en-u…	Support ↗	new tab	Add '(opens in new tab)' to text
https://support.sharethrough.com/hc/en-u…	Support ↗	new tab	Add '(opens in new tab)' to text
https://www.politicaladregistry.com/?com…	Political Ads Registry ↗	new tab	Add '(opens in new tab)' to text
https://privacy-center.sharethrough.com	Privacy Center ↗	new tab	Add '(opens in new tab)' to text
https://privacy-center.sharethrough.com/…	Opt-Out/Do Not Sell Personal I…	new tab	Add '(opens in new tab)' to text
https://www.greenpmp.io/	GreenPMP.io ↗	new tab	Add '(opens in new tab)' to text
https://headlines.sharethrough.com/	Headline Analyzer ↗	new tab	Add '(opens in new tab)' to text
https://www.equativ.com/press/equativ-an…	Learn More →	new tab	Add '(opens in new tab)' to text
#	English	img no alt	Add alt attribute to the image
#	Français	img no alt	Add alt attribute to the image
#	Deutsch	img no alt	Add alt attribute to the image
#	Русский	img no alt	Add alt attribute to the image
#	Español	img no alt	Add alt attribute to the image

103 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; https://adnetzero.com/; https://www.scope3.com/; https://sciencebasedtargets.org/; https://www.51tocarbonzero.com/; https://www.linkedin.com/company/sharethrough/; https://www.facebook.com/sharethrough/; https://twitter.com/sharethrough; https://www.instagram.com/sharethrough/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="#"]; a[href="#"]; a[href="#"]; a[href="#"]; a#weglot-language-en; a#weglot-language-fr; a#weglot-language-de; a#weglot-language-ru; a#weglot-language-es

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://equativ.com/press/equativ-and-sharethrough-will-now-operate-under-equ…; https://support.sharethrough.com/hc/en-us; https://headlines.sharethrough.com/; https://generator.sharethrough.com/; https://support.sharethrough.com/hc/en-us; https://pubmaestro.sharethrough.com; https://support.sharethrough.com/hc/en-us; https://pubmaestro.sharethrough.com; https://www.sharethrough.com/blog/sharethrough-and-equativ-are-merging; https://www.sharethrough.com/blog/sharethrough-and-equativ-are-merging (+8 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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

12 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 12 <nav> element(s)

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.

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 404 Not Found — Sharethrough ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

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 Enhancing the Ad Experience.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Across Every Channel.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h1 For Better Outcomes.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Enhancing the Ad Experience.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Across Every Channel.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h1 For Better Outcomes.

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Big News! Sharethrough & Equativ are Mer…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Big News! Sharethrough & Equativ are Mer…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sharethrough Core Principles for Maximiz…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

24px · bottom of viewport

h2 You Don't Have to Take Our Word For It..…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Us

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Solutions For Brands & Agencies

1.22:1

#000000

#0E1C28

needs 3.0:1 (large text)

19px · above the fold

h3 Solutions For Publishers

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Company

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Resources

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unique Proprietary Technology Automatica…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sharethrough Products and Technologies a…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pioneering Sustainability in Ad Tech

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Inventory Curation Towards Advertiser Pe…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

h3 United as One: Sharethrough is now Equat…

1.21:1

#000000

#0C1C27

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Enhancing the Ad Exp…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h1 Across Every Channel…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h1 For Better Outcomes.	1.21:1	3.0:1	#000000	#0C1C27	Fail
h1 Enhancing the Ad Exp…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h1 Across Every Channel…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h1 For Better Outcomes.	1.21:1	3.0:1	#000000	#0C1C27	Fail
h2 Big News! Sharethrou…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h2 Big News! Sharethrou…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h2 Sharethrough Core Pr…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h2 You Don't Have to Ta…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h2 Contact Us	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Solutions For Brands…	1.22:1	3.0:1	#000000	#0E1C28	Fail
h3 Solutions For Publis…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Company	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Resources	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Unique Proprietary T…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Sharethrough Product…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Pioneering Sustainab…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 Inventory Curation T…	1.21:1	3.0:1	#000000	#0C1C27	Fail
h3 United as One: Share…	1.21:1	3.0:1	#000000	#0C1C27	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 29 passed

REVIEW

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
GreenPMPs™ `div.border-bottom > div.column-testimonials > p > a`
GreenPMPs™ `div.border-bottom > div.column-testimonials > p > a`
div.column-18 > div.w-clearfix > form#email-form > input#Email-6 `div.column-18 > div.w-clearfix > form#email-form > input#Email-6`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js `html.w-mod-js`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Country* United States United Kingdom Canada Germany Netherlands Japan Australi… `div.w-clearfix > form#Website-Contact-Form-En > div.div-block-contact-form > select#Country-2`
I am a... Publisher Advertiser Trader DSP Other `div.w-clearfix > form#Website-Contact-Form-En > div.div-block-contact-form > select#I-am-a-2`

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-11 > div.columns-6 > div.column-19 > a.linkedin `div.container-11 > div.columns-6 > div.column-19 > a.linkedin`
div.container-11 > div.columns-6 > div.column-19 > a.facebook `div.container-11 > div.columns-6 > div.column-19 > a.facebook`
div.container-11 > div.columns-6 > div.column-19 > a.twitter `div.container-11 > div.columns-6 > div.column-19 > a.twitter`
div.container-11 > div.columns-6 > div.column-19 > a.instagram `div.container-11 > div.columns-6 > div.column-19 > a.instagram`

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

●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

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

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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●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"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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 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

○`<html>` element has a valid value for its `[lang]` attribute

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

Heading Hierarchy

18 headings

PASS

18 headings

Multiple H1 headings (4 found)

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

H3 Solutions For Brands & Agencies
H3 Solutions For Publishers
H3 Company
H3 Resources
H2 Big News! Sharethrough & Equativ are Merging
H2 Big News! Sharethrough & Equativ are Merging
H1 Enhancing the Ad Experience.Across Every Channel.For Better Outcomes.
H1 Enhancing the Ad Experience. duplicate H1
H1 Across Every Channel. duplicate H1
H1 For Better Outcomes. duplicate H1
H2 Sharethrough Core Principles for Maximizing Advertiser Outcomes
H3 Unique Proprietary Technology Automatically Enhances All Standard Ad Formats
H3 Sharethrough Products and Technologies are Proven to Improve
H3 Pioneering Sustainability in Ad Tech
H3 Inventory Curation Towards Advertiser Performance Goals and Needs
H2 You Don't Have to Take Our Word For It...
H2 Contact Us
H3 United as One: Sharethrough is now Equativ

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

A+

Alt Text Quality

All 46 images OK

PASS

All 46 images OK

42 decorative image(s) correctly marked

4 image(s) with good alt text

46 images 4 good alt text 42 decorative

All images have appropriate alt text.

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