Skip to content
https://emarketer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
83 headings, 4 skip(s)
FIX
83 headings, 4 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
9 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Products
  • H1 Events & Resources duplicate H1
  • H1 Topics duplicate H1
  • H3 Latest Articles skipped
  • H4 Digital maturation helped drive Truist’s Q1 2026 earnings growth
  • H4 When kids want to watch their favorite creators, they go to YouTube
  • H4 Accelerator Active Energy bets on athlete creators to grow its brand
  • H4 What Paramount's Warner Bros. Discovery deal means for advertisers
  • H4 LendingClub’s identity shift signals expanded services
  • H4 Mission Lane wants to graduate from its fintech status
  • H4 Apple’s CEO handoff raises stakes for Siri, AI, and devices
  • H4 UnitedHealth’s earnings surge calms a nervous Wall Street
  • H4 By prioritizing CX orchestration, Adobe shields itself from competitors built on agents
  • H4 Eli Lilly builds on deal streak with $7B oncology acquisition
  • H1 About duplicate H1
  • H1 Smarter Insights, Faster Decisions. duplicate H1
  • H2 Latest Research
  • H5 Digital maturation helped drive Truist’s Q1 2026 earnings growth skipped
  • H5 When kids want to watch their favorite creators, they go to YouTube
  • H5 Accelerator Active Energy bets on athlete creators to grow its brand
  • H5 What Paramount's Warner Bros. Discovery deal means for advertisers
  • H5 LendingClub’s identity shift signals expanded services
  • H5 Mission Lane wants to graduate from its fintech status
  • H5 Apple’s CEO handoff raises stakes for Siri, AI, and devices
  • H5 UnitedHealth’s earnings surge calms a nervous Wall Street
  • H5 By prioritizing CX orchestration, Adobe shields itself from competitors built on agents
  • H5 Eli Lilly builds on deal streak with $7B oncology acquisition
  • H5 Live & Virtual Events
  • H5 Cannes Lions 2025
  • H5 Navigating Uncertainty 2025
  • H5 See the trend data we’re featuring today
  • H5 Maximizing Marketing Efficiency with AI
  • H5 Boost Sales with Mobile Apps
  • H5 Brand Safety Toolkit
  • H5 Ebooks, Guides, and More
  • H5 On-Demand Webinar: Unlocking Fresh Data and Deeper Insights
  • H5 Unlock the Secrets to Engaging Gen Z
  • H5 Don’t miss digital advertising’s next major wave
  • H5 The New Era of Social Media
  • H3 Beyond the Research: Analyst Speaking Events
  • H2 In the News
  • H5 Intel results to show if supply chain issues are dimming its AI ambitions skipped
  • H5 Who is John Ternus, set to succeed Tim Cook as Apple's CEO?
  • H5 QVC Lost the Home Shoppers to Social Media Influencers
  • H5 Meta’s Victory Lap Over Google on Ads Will Be Short
  • H5 As upfront negotiations near, buyers chart path through complex sports market
  • H5 The World Cup is set to lift demand for digital out-of-home spending
  • H5 Walmart challenges Amazon on same-day delivery by using stores as warehouses
  • H5 Meta set to overtake Google's advertising dominance
  • H5 AI companies lean into advertising as infrastructure costs rise
  • H5 Can social shopping move beyond TikTok? QVC is betting on it
  • H2 Explore what EMARKETER can provide for your industry.
  • H5 Advertising, Media and Marketing→ skipped
  • H5 Retail & Ecommerce→
  • H5 Financial Services→
  • H5 Technology→
  • H5 Complete Coverage Areas→
  • H2 Here’s what our clients have to say.
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H1 Become a client. duplicate H1
  • H2 Coverage Areas →
  • H2 Coverage Areas →
  • H3 Advertising & Marketing
  • H3 Health
  • H3 Ecommerce & Retail
  • H3 Technology
  • H3 Financial Services
  • H3 More Topics
  • H3 Geographies
  • H3 EMARKETER
  • H3 Media Services
  • H3 Free Content
  • H2 Contact Us →
  • H3 Worldwide HQ
  • H3 Sales Inquiries

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
34 of 56 images have issues
FIX
34 of 56 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
32 image(s) with filename as alt text
Info::
16 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
56 images 6 good alt text 16 decorative 32 generic 2 missing
IssueCount
missing2 image(s)
filename32 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN CONTENTINFO (missing!)

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title EMARKETER ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
18 icon(s) detected
REVIEW
18 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 Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 25 passed
REVIEW
82

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.

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.sm:px-4 > div > form.So9Z7v22cC0OzDj3fgYi > button.OZXE_BZ0I_Il2kJQSM_1 div.sm:px-4 > div > form.So9Z7v22cC0OzDj3fgYi > button.OZXE_BZ0I_Il2kJQSM_1

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
li.glide__slide > div.mb-10 > a.flex > img.object-cover li.glide__slide > div.mb-10 > a.flex > img.object-cover
li.glide__slide > div.mb-10 > a.flex > img.object-cover li.glide__slide > div.mb-10 > a.flex > img.object-cover

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.Branding-module__primaryBar___xF5qj > div.Widget-module__widgetWrapper___4ifOW > div.Widget-module__widgetButton___117tK > a.SearchButton-module__wrapper___yIStV div.Branding-module__primaryBar___xF5qj > div.Widget-module__widgetWrapper___4ifOW > div.Widget-module__widgetButton___117tK > a.SearchButton-module__wrapper___yIStV
ul.glide__slides > li.glide__slide > div.flex > a.flex ul.glide__slides > li.glide__slide > div.flex > a.flex
ul.glide__slides > li.glide__slide > div.mx-0 > a.flex ul.glide__slides > li.glide__slide > div.mx-0 > a.flex
ul.glide__slides > li.glide__slide > div.flex > a.flex ul.glide__slides > li.glide__slide > div.flex > a.flex
ul.glide__slides > li.glide__slide > div.flex > a.flex ul.glide__slides > li.glide__slide > div.flex > a.flex
ul.glide__slides > li.glide__slide > div.mb-10 > a.flex ul.glide__slides > li.glide__slide > div.mb-10 > a.flex
ul.glide__slides > li.glide__slide > div.mb-4 > a.flex ul.glide__slides > li.glide__slide > div.mb-4 > a.flex
ul.glide__slides > li.glide__slide > div.mb-10 > a.flex ul.glide__slides > li.glide__slide > div.mb-10 > a.flex
ul.glide__slides > li.glide__slide > div.mb-10 > a.flex ul.glide__slides > li.glide__slide > div.mb-10 > a.flex
ul.glide__slides > li.glide__slide > div.mb-10 > a.flex ul.glide__slides > li.glide__slide > div.mb-10 > a.flex

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
Accept div.osano-cm-window > div#a352c055-7ac1-45b9-b158-3d2427505576 > div.osano-cm-dialog__buttons > button.osano-cm-accept
Learn More div.container > div.sm:px-4 > div.space-y-4 > a#hpcta_#_getademo
Learn More div.container > div.sm:px-4 > div.space-y-4 > a.btn-primary
Become a Client div.container > div.sm:px-4 > div.space-y-4 > a.btn-primary
* Copyright © 2026  div.Footer-module__footerWrapper___8gP5w > div.FooterFooter-module__container___awvxD > div.ResourceTray-module__resourceTrayContainer___8MW9X > div.ResourceTray-module__copyright___9oQOP
EMARKETER Inc. All Rights Reserved. div.Footer-module__footerWrapper___8gP5w > div.FooterFooter-module__container___awvxD > div.ResourceTray-module__resourceTrayContainer___8MW9X > div.ResourceTray-module__companyInc___1syXM

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
Live & Virtual Events div.Card-module__cardContainer___bS6mz > div.CarouselCard-module__flexContainer___2jCTF > a.CarouselCard-module__titleWrapper___pPc-E > h5.CarouselCard-module__title___l2fed
Intel results to show if supply chain issues are dimming its AI ambitions div.Card-module__cardContainer___bS6mz > div.CarouselCard-module__flexContainer___2jCTF > a.CarouselCard-module__titleWrapper___pPc-E > h5.CarouselCard-module__title___l2fed
Advertising, Media and Marketing→ div.container > div.container > div.sm:px-4 > h5.leading-tight

These are opportunities to improve keyboard navigation in your application.

○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
●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
●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.
●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
●ARIA IDs are unique
●All heading elements contain content.
●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
○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
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: EMARKETER
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name EMARKETER ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name EMARKETER Display Mode minimal-ui Background Color #ffffff Icons 8 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Products18.88:13.0:1
#000000
#F0F3F8
Pass
h1 Events & Resources18.88:13.0:1
#000000
#F0F3F8
Pass
h1 Topics18.88:13.0:1
#000000
#F0F3F8
Pass
h1 About18.88:13.0:1
#000000
#F0F3F8
Pass
h1 Smarter Insights,18.88:13.0:1
#000000
#F0F3F8
Pass
h1 Become a client18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Latest Research18.88:13.0:1
#000000
#F0F3F8
Pass
h2 In the News18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Explore what EMARKET…18.88:13.0:1
#000000
#F0F3F8
Pass
h2 for your industry18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Here’s what our cl…18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Coverage Areas18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Coverage Areas18.88:13.0:1
#000000
#F0F3F8
Pass
h2 Contact Us18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Latest Articles18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Beyond the Research:…18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Advertising & Market…18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Health18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Ecommerce & Retail18.88:13.0:1
#000000
#F0F3F8
Pass
h3 Technology18.88:13.0:1
#000000
#F0F3F8
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.

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

Send Feedback