Skip to content
https://nielsen.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Heading Hierarchy
Action
43 headings, 4 skip(s)
FIX
43 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H4 → H6 (missing H5)
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: H3 → H5 (missing H4)
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.
  • H6 Featured
  • H4 Type
  • H4 Topic
  • H6 Featured skipped
  • H6 Featured
  • H1 Nielsen’s comprehensive data and measurement are powering the future of media
  • H2 Real audiences. Real data. Real decisions.
  • H2 Plan your sports marketing strategy for 2026
  • H2 Real audiences. Real data. Real decisions.
  • H2 Plan your sports marketing strategy for 2026
  • H3 Stay ahead of shifting sports fan behaviors from the Super Bowl to the Olympics with exclusive insights on sponsorships, streaming, and next-gen fans.
  • H2 Connecting you to audiences, growth and new opportunities.
  • H3 Nielsen ONE
  • H4 (empty)
  • H3 Audiencemeasurement
  • H3 Media planning
  • H3 Marketing optimization
  • H3 Gracenote content metadata
  • H2 Stay ahead of media’s evolution with our timely insights.
  • H6 Featured skipped
  • H4 The Gauge
  • H3 2025 Annual Marketing Report
  • H3 The Black influence: How Black culture & identity drive the market
  • H3 The Gauge
  • H3 Need to Know: What are Nielsen ratings?
  • H2 Real people are always at the heart of our data.
  • H3 People around the world participate in our panels
  • H3 Employees power our business globally
  • H3 Business resource groups champion an inclusive culture
  • H2 Let’s Talk
  • H3 Get a demo
  • H3 Find the right solution for your business
  • H5 How can we help? skipped
  • H3 Find the right solution for your business
  • H5 How can we help? skipped
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H4 Social Media Cookies
  • H3 Cookie List

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

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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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
Form Accessibility
Action
3 of 51 controls have issues
REVIEW
3 of 51 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="submit" id="nf-field-2947">; <input type="submit" id="nf-field-1866_1">; <input type="submit" id="nf-field-1866">
Info::
48 control(s) properly labeled
51 controls
48 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#nav-searchtextSearch inputaria-label
#wp-block-search__input-1searchSearchfor/id
#nf-field-2919textFirst name *for/id
#nf-field-2920textLast name *for/id
#nf-field-2921emailBusiness email address *for/id
#nf-field-2922selectLocation *for/id
#nf-field-2923textJob title *for/id
#nf-field-2924textCompany *for/id
#nf-field-2925textareaTell us more about your needs *for/id
#nf-field-2927-0checkboxSign me up! I want to stay ahead of media's evolution with emails on the latest trends and insights, Nielsen/Gracenote content, products, events, and more!for/id
#nf-field-hp-87textIf you are a human seeing this field, please leave it empty.none
#nf-field-1878_1textpostidfor/id
#nf-field-1873_1selectHow can we help? *for/id
#nf-field-1869_1textFirst name *for/id
#nf-field-1870_1textLast name *for/id
#nf-field-1864_1emailBusiness email address *for/id
#nf-field-1863_1textJob title *for/id
#nf-field-1872_1selectIndustry *for/id
#nf-field-1868_1textCompany *for/id
#nf-field-1871_1selectLocation *for/id
#nf-field-1865_1textareaTell us more about your needs: *for/id
#nf-field-1875_1-0checkboxYes! Sign me up for insights and news that count in Nielsen's weekly newsletter.for/id
#nf-field-1891_1-0checkboxSign me up! I want to stay ahead of media's evolution with emails on the latest trends and insights, Nielsen/Gracenote content, products, events, and more!for/id
#nf-field-1877_1textnewsletterfor/id
#nf-field-hp-61_1textIf you are a human seeing this field, please leave it empty.none
#nf-field-1878textpostidfor/id
#nf-field-1873selectHow can we help? *for/id
#nf-field-1869textFirst name *for/id
#nf-field-1870textLast name *for/id
#nf-field-1864emailBusiness email address *for/id
#nf-field-1863textJob title *for/id
#nf-field-1872selectIndustry *for/id
#nf-field-1868textCompany *for/id
#nf-field-1871selectLocation *for/id
#nf-field-1865textareaTell us more about your needs: *for/id
#nf-field-1875-0checkboxYes! Sign me up for insights and news that count in Nielsen's weekly newsletter.for/id
#nf-field-1891-0checkboxSign me up! I want to stay ahead of media's evolution with emails on the latest trends and insights, Nielsen/Gracenote content, products, events, and more!for/id
#nf-field-1877textnewsletterfor/id
#nf-field-hp-61textIf you are a human seeing this field, please leave it empty.none
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#nf-field-1866_1submit(none)none
#nf-field-1866submit(none)none
#nf-field-2947submit(none)none

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

<input type="submit" id="nf-field-2947">; <input type="submit" id="nf-field-1866_1">; <input type="submit" id="nf-field-1866">

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Nielsen ✓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
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
10 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
16 images 6 good alt text 10 decorative
All images have appropriate alt text.
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 Nielsen’s comprehe…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Real audiences. Real…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Plan your sports mar…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Real audiences. Real…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Connecting you to au…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Stay ahead of media…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Real people are alwa…19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Let’s19.63:13.0:1
#000000
#F7F7F9
Pass
h2 Privacy Preference C…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Stay ahead of shifti…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Audience19.63:13.0:1
#000000
#F7F7F9
Pass
h3 measurement19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Media19.63:13.0:1
#000000
#F7F7F9
Pass
h3 planning19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Marketing optimizati…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Gracenote content me…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 2025 Annual Marketin…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 People around the wo…19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Employees power our …19.63:13.0:1
#000000
#F7F7F9
Pass
h3 Business resource gr…19.63:13.0:1
#000000
#F7F7F9
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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

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
Cookie Settings div.wp-block-columns > div.wp-block-column > p.has-dark-color > a#privacy-preferences-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-*]` 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.
●`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 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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[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.
○`[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
○Form elements have associated labels
○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.
○`[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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback