Skip to content
https://cnbc.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 20 -1-on-focusable
FIX
0 positive, 20 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
54 headings, 1 skip(s)
REVIEW
54 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Info::
1 hidden heading(s) (aria-hidden)
  • H2 TSMC, the world’s largest contract chipmaker, reports 68% surge in June revenue
  • H2 Latest News
  • H2 QUOTE FINDER
  • H2 Markets
  • H3 Market MOVERS
  • H4 TOP
  • H4 BOTTOM
  • H3 Most Active
  • H3 Unusual Volume
  • H3 Latest Market News
  • H3 Special Reports
  • H2 Trending Now
  • H2 Top Videos
  • H2 United Kingdom
  • H2 Converge
  • H2 Pro News and Analysis
  • H2 CNBC Travel
  • H2 Make It
  • H2 CNBC Explains
  • H4 News Tips skipped
  • H4 CNBC Newsletters
  • H4 Advertise With Us
  • H3 We and our partners process data to provide:
  • H2 Cookie Settings
  • H2 Cookie Settings hidden
  • H3 Your Privacy
  • H3 Strictly Necessary
  • H3 Save and communicate privacy choices 503 partners can use this special purpose
  • H3 Ensure security, prevent and detect fraud, and fix errors 643 partners can use this special purpose
  • H3 Deliver and present advertising and content 631 partners can use this special purpose
  • H3 Store and/or access information on a device 840 partners can use this purpose
  • H3 Personalised advertising and content, advertising and content measurement, audience research and services development 981 partners can use this purpose
  • H3 Targeted Advertising
  • H3 Content Selection
  • H4 Your Privacy
  • H4 Strictly Necessary
  • H4 Save and communicate privacy choices 503 partners can use this special purpose
  • H4 Ensure security, prevent and detect fraud, and fix errors 643 partners can use this special purpose
  • H4 Deliver and present advertising and content 631 partners can use this special purpose
  • H4 Store and/or access information on a device 840 partners can use this purpose
  • H4 Personalised advertising and content, advertising and content measurement, audience research and services development 981 partners can use this purpose
  • H5 Use limited data to select advertising 781 partners can use this purpose
  • H5 Create profiles for personalised advertising 627 partners can use this purpose
  • H5 Use profiles to select personalised advertising 632 partners can use this purpose
  • H5 Create profiles to personalise content 259 partners can use this purpose
  • H5 Use profiles to select personalised content 231 partners can use this purpose
  • H5 Measure advertising performance 900 partners can use this purpose
  • H5 Measure content performance 407 partners can use this purpose
  • H5 Understand audiences through statistics or combinations of data from different sources 572 partners can use this purpose
  • H5 Develop and improve services 679 partners can use this purpose
  • H5 Use limited data to select content 178 partners can use this purpose
  • H4 Targeted Advertising
  • H4 Content Selection
  • H3 Cookie List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (22 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (22 below threshold)
Info::
22 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 9.0px ("Search quotes, news & videos"); <span> 9.0px ("LAST |"); <span> 9.0px ("4:58:14 PM AET"); <span> 9.0px ("LAST |"); <span> 9.0px ("3:45:03 PM JST").
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title International Business, World News & Glo…
1.11:1
#000000
on
#000F2D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip Navigation
1.81:1
#000000
on
#30394B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 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 QUOTE FINDER21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Now21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cookie Settings21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cookie Settings21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Most Active21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Unusual Volume21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Special Reports21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We and our partners …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Privacy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Strictly Necessary21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Save and communicate…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ensure security, pre…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deliver and present …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Store and/or access …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Personalised adverti…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Targeted Advertising21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Content Selection21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title International Busine…1.11:14.5:1
#000000
#000F2D
Fail
a Skip Navigation1.81:14.5:1
#000000
#30394B
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 88/100 — 5 failing, 30 passed
REVIEW
88

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
S&P section.MarketMovers-container > section.MarketMovers-titleContainer > div.MarketMoversMenu-moverContainer > button#market-tab-SP500

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
EUR section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
US section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
OIL section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
BONDS section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
GOLD section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
FX section#HomePageInternational-MarketsBanner-1 > div.MarketsBannerMenu-marketBannerMenuWrapper > div.MarketsBannerMenu-container > button.MarketsBannerMenu-marketOption
LAST | 4:58:14 PM AET div#market-data-scroll-container > a.MarketCard-container > div.MarketCard-row > span.MarketCard-lastTime
LAST | 3:45:03 PM JST div#market-data-scroll-container > a.MarketCard-container > div.MarketCard-row > span.MarketCard-lastTime
LAST | 3:01:08 PM IST div#market-data-scroll-container > a.MarketCard-container > div.MarketCard-row > span.MarketCard-lastTime
LAST | 4:09:12 PM CTT div#market-data-scroll-container > a.MarketCard-container > div.MarketCard-row > span.MarketCard-lastTime
LAST | 3:00:00 PM CTT div#market-data-scroll-container > a.MarketCard-container > div.MarketCard-row > span.MarketCard-lastTime
31 MIN AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
1 HOUR AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
2 HOURS AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
3 HOURS AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
3 HOURS AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
4 HOURS AGO div.LatestNews-container > div.LatestNews-headlineWrapper > span.LatestNews-wrapper > time.LatestNews-timestamp
+0.09 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain
+0.658 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain
+0.16 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain
+0.859 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain
+2.6 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain
+52 table.BasicTable-table > tbody.BasicTable-tableBody > tr > td.BasicTable-quoteGain

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
News Tips div.CNBCFooter-wrapper > ul.CNBCFooter-section > li.CNBCFooter-sectionItem > h4.CNBCFooter-sectionTitle

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
CNBC Pro div.RiverPlusCard-container > div.RiverPlusCard-cardLeft > div.RiverHeadline-headline > a.ProPill-proPillLink
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div#HomePageInternational-riverPlus-12-9 > div.RiverThumbnail-breakerImage > div.RiverThumbnail-imageThumbnail > a div#HomePageInternational-riverPlus-12-9 > div.RiverThumbnail-breakerImage > div.RiverThumbnail-imageThumbnail > a
CNBC Pro div.RiverPlusCard-container > div.RiverPlusCard-cardLeft > div.RiverHeadline-headline > a.ProPill-proPillLink
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
CNBC Pro div.RiverPlusCard-container > div.RiverPlusCard-cardLeft > div.RiverHeadline-headline > a.ProPill-proPillLink
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
CNBC Pro div.RiverPlusCard-container > div.RiverPlusCard-cardLeft > div.RiverHeadline-headline > a.ProPill-proPillLink
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a div.RiverPlusCard-container > div.RiverThumbnail-thumbnailContainer > div.RiverThumbnail-imageThumbnail > a
CNBC Pro div > div.Card-pro > div > a.ProPill-proPillLink
CNBC Pro div > div.Card-pro > div > a.ProPill-proPillLink
CNBC Pro div > div.Card-pro > div > a.ProPill-proPillLink
CNBC Pro div > div.Card-pro > div > a.ProPill-proPillLink
CNBC Pro div > div.Card-pro > div > a.ProPill-proPillLink

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
META Meta Platforms Inc 5.975% SBAC SBA Communications Corp 4.137% NVDA… section.MarketMovers-container > section.MarketMovers-marketTopContainer > section.MarketTop-container > table.MarketTop-topTable
MRNA Moderna Inc 10.828% CRWD CrowdStrike Holdings Inc 5.655% DDOG Dat… section.MarketMovers-container > section.MarketMovers-marketTopContainer > section.MarketTop-container > table.MarketTop-topTable
○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 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.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`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 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 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.
○`<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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
A
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #MainContent
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV "Cookie Categories" MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 151 chars - H4: 151 chars
Got: 2 >120-char heading(s)
Info::
2 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 2 all-caps heading(s)
A+
Alt Text Quality
All 48 images OK
PASS
All 48 images OK
Info::
48 image(s) with good alt text
48 images 48 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 20 controls have issues
PASS
1 of 20 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="QuoteFinder-searchInput">
Info::
19 control(s) properly labeled
20 controls
19 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-IAB2V2_1checkboxStore and/or access information on a devicefor/id
#ot-group-id-V2STACK42checkboxPersonalised advertising and content, advertising and content measurement, audience research and services developmentfor/id
#ot-sub-group-id-IAB2V2_2checkboxUse limited data to select advertisingaria-label
#ot-sub-group-id-IAB2V2_3checkboxCreate profiles for personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_4checkboxUse profiles to select personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_5checkboxCreate profiles to personalise contentaria-label
#ot-sub-group-id-IAB2V2_6checkboxUse profiles to select personalised contentaria-label
#ot-sub-group-id-IAB2V2_7checkboxMeasure advertising performancearia-label
#ot-sub-group-id-IAB2V2_8checkboxMeasure content performancearia-label
#ot-sub-group-id-IAB2V2_9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
#ot-sub-group-id-IAB2V2_10checkboxDevelop and improve servicesaria-label
#ot-sub-group-id-IAB2V2_11checkboxUse limited data to select contentaria-label
#ot-group-id-4checkboxTargeted Advertisingfor/id
#ot-group-id-7checkboxContent Selectionfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#QuoteFinder-searchInputsearch(Search)placeholder only

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

<input type="search" id="QuoteFinder-searchInput">

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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "vendor-search-handler" should use type="search" (currently type="text")
Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
20 form control(s) checked, no input-semantic issues
PASS
20 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback