Skip to content
https://comscore.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Heading Hierarchy
Action
26 headings, 3 skip(s)
FIX
26 headings, 3 skip(s)
Info::
Single H1 present
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 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Comscore is a trusted currency for planning, transacting, and evaluating media across platforms.
  • H3 Plan skipped
  • H3 Transact
  • H3 Evaluate
  • H2 Programmatic Targeting, Simplified
  • H2 A True View of Cross-Platform Social Audiences
  • H2 Insights
  • H4 Proximic Political Targeting Playbook skipped
  • H4 2026 Proximic Back to School Audience Guide
  • H4 Comscore Social Brand Survey Lift - Dazed
  • H4 Retrospectiva Digital 2025: Definindo o rumo para 2026
  • H4 2025 Year in Review: Setting the Stage for 2026 – India...
  • H4 2026 Summer Guide
  • H4 2025 Year in Review: Setting the Stage for 2026 – UK...
  • H4 2026 Proximic Championship Playbook
  • H4 El “Social Bowl” y su impacto en redes sociales
  • H4 Fast Facts: 2026 Winter Games Opening on Social Media
  • H4 Comscore Social Brand Survey Lift
  • H4 2026 State of Programmatic
  • H4 Comscore Continues Building Momentum in Local Measurement Through New Agreements with More than 15 Clients
  • H4 Five Decades of Box Office Intelligence: Comscore Celebrates 50 Years of Movie Measurement
  • H4 Comscore Reports Fourth Quarter and Full Year 2025 Results
  • H3 Solutions for
  • H3 Trending Topics
  • H3 Featured
  • H5 (empty)

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

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::
Breadcrumb navigation detected
Got: aria-label
Info::
2 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search
Skip Link
Labeled Navigation 2 <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
Landmark Structure
Action
10 landmarks
REVIEW
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) 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 navigation" MAIN (missing!) CONTENTINFO footer

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

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 Not Found - Comscore, Inc. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h2 Insights
1.56:1
#000000
on
#282F39
needs 3.0:1 (large text)
24px · mid-page
h3 Plan
1.37:1
#000000
on
#23252C
needs 3.0:1 (large text)
19px · above the fold
h3 Transact
1.40:1
#000000
on
#212732
needs 3.0:1 (large text)
19px · above the fold
h3 Evaluate
1.35:1
#000000
on
#1F242F
needs 3.0:1 (large text)
19px · above the fold
span Measure what matters to make cross-platf…
1.39:1
#000000
on
#262628
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Learn more
1.39:1
#000000
on
#26262A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Comscore is a trusted currency for plann…
1.39:1
#000000
on
#25262B
needs 4.5:1 (normal text)
16px · above the fold
p Connect the dots across multiple data so…
1.43:1
#000000
on
#222934
needs 4.5:1 (normal text)
16px · above the fold
p Build your business around the transform…
1.42:1
#000000
on
#212833
needs 4.5:1 (normal text)
16px · above the fold
p Understand the impact of media and marke…
1.45:1
#000000
on
#252A31
needs 4.5:1 (normal text)
16px · above the fold
span Programmatic Targeting, Simplified
1.28:1
#000000
on
#1F1F20
needs 4.5:1 (normal text)
16px · above the fold
div Comscore’s dedicated programmatic targ…
1.25:1
#000000
on
#1E1D21
needs 4.5:1 (normal text)
16px · above the fold
a Proximic by Comscore
1.24:1
#000000
on
#1D1C21
needs 4.5:1 (normal text)
16px · mid-page
div , enables media buyers and sellers to ac…
1.24:1
#000000
on
#1D1C21
needs 4.5:1 (normal text)
16px · mid-page
strong Learn More
1.23:1
#000000
on
#1B1C20
needs 3.0:1 (large text)
16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Insights1.56:13.0:1
#000000
#282F39
Fail
h3 Plan1.37:13.0:1
#000000
#23252C
Fail
h3 Transact1.40:13.0:1
#000000
#212732
Fail
h3 Evaluate1.35:13.0:1
#000000
#1F242F
Fail
h3 Solutions for21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trending Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured21.00:13.0:1
#000000
#FFFFFF
Pass
title Comscore is a truste…21.00:14.5:1
#000000
#FFFFFF
Pass
span Toggle navigation21.00:14.5:1
#000000
#FFFFFF
Pass
span Measure what matters…1.39:14.5:1
#000000
#262628
Fail
a Learn more1.39:14.5:1
#000000
#26262A
Fail
span Comscore is a truste…1.39:14.5:1
#000000
#25262B
Fail
p Connect the dots acr…1.43:14.5:1
#000000
#222934
Fail
p Build your business …1.42:14.5:1
#000000
#212833
Fail
p Understand the impac…1.45:14.5:1
#000000
#252A31
Fail
span Programmatic Targeti…1.28:14.5:1
#000000
#1F1F20
Fail
div Comscore’s dedicat…1.25:14.5:1
#000000
#1E1D21
Fail
a Proximic by Comscore1.24:14.5:1
#000000
#1D1C21
Fail
div , enables media buye…1.24:14.5:1
#000000
#1D1C21
Fail
strong Learn More1.23:13.0:1
#000000
#1B1C20
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 86/100 — 4 failing, 29 passed
REVIEW
86

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

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Measure what matters to make cross-platform audiences and advertising more valu… div.row > div.col-md-7 > div.pl-5 > span.display-5

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 div.row > div.col-md-4 > div#pr_slider > ul.slick-dots
1 2 3 4 5 6 7 div.row > div#homepage_rankings > div.carouseling > ul.slick-dots

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.

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
Proximic by Comscore div.row > div.col-sm-5 > div > a
LEARN MORE div > p.mt-3 > a.btn > strong
LEARN MORE div > p.mt-3 > a.btn > strong
PRESENTATION div.card > div.card-body > label.small > strong
LEARN MORE a.h-100 > div.card > div.card-body > button.mt-auto
PRESS RELEASES div.row > div.col-md-4 > label.text-uppercase > strong
21 Apr 2026 div#slick-slide10 > div > div > div.semibold
RANKINGS div.row > div#homepage_rankings > label.text-uppercase > strong
(ESTIMATES) WEEKEND ENDING APRIL 19, 2026 div.slick-track > div#slick-slide20 > div > div#reporting_period_0
ATTEND div.row > div.col-md-4 > label.text-uppercase > strong
© 2026 Comscore, Inc. div.container > div.row > div.col > p

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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]` 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
●`[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.
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○`[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
○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.
○`<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>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search_inputtextSearcharia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback