Skip to content
https://zerohedge.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #222222
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 ModePartial Dark Mode
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 header MAIN CONTENTINFO footer

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
Heading Hierarchy
28 headings
REVIEW
28 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Time For CAR To Come Back Down To Earth
  • H3 BY Portfolio Armor
  • H2 States with the Highest Murder Rate
  • H3 BY ammodotcom
  • H2 Strait Of Hormuz Will Cause "Ripple Effects" For The Whole World
  • H3 BY quoth the raven
  • H2 Login
  • H2 Trump Extends Ceasefire By 3-5 Days, Precisely Amount Of Time Needed For Third Carrier To Arrive
  • H2 We're In The 'Final Innings Of Systematic Support' For Stocks: Goldman Delta-One Desk-Head Warns 'The Easy Part Is Behind Us'
  • H2 'Alligator Alcatraz' Can Continue Operating, Appeals Court Says
  • H2 Tesla Earnings Preview: "Braced For A Miss"
  • H2 Duffy Seeking $10 Billion From Congress To Revamp Air Traffic Control System
  • H2 Two Armed Robbers Steal $1.8 Million From Brinks Armored Truck In Philadelphia
  • H2 Trump Deploys Five Defense Production Act Memos For American Energy
  • H2 CIA Security Officer Files Lawsuit Against Steve Baker And The Blaze For Identifying Her As J6 Bomber
  • H2 "All Systems Go": Goldman Sees Improvement As Boeing Turnaround Gains Momo
  • H2 Solid 20Y Auction Stops Through With Above Average Foreign Demand
  • H2 Iran's Covert Oil Trade Persists As Tankers Breach US Blockade
  • H2 U.S. Gov't Could End Up Owning 90% Of Spirit In Rescue Deal
  • H2 Virginia Redistricting Rout Deals Major Blow To House Republicans
  • H2 Risk Assets Are Leaning Too Hard On Trump's Peace Push
  • H2 Anthropic's 'Too Dangerous To Release' AI Model Was Accessed By Discord Group On Day One
  • H2 China Tech Left Behind… But For How Long?
  • H2 US Law Firm Apologizes After AI Hallucinations Made It To Legal Filing
  • H2 After "Tectonic" Serra Verde Acquisition, Canaccord Reiterates Buy, Raises Price Target To $32 On USA Rare Earth
  • H2 'Tactical Risk/Reward Not Compelling Here': Goldman's Hedge Fund Honcho Lays Out The Bull/Bear Case
  • H2 A New Iran (Military?) Base Case
  • H3 Today's Top Stories

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="username">; <input type="password" name="password">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="qTitle" id="qTitle">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#qTitletext(Search ZeroHedge)placeholder only
passwordpassword(none)none
usernametext(none)none

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

<input type="text" name="username">; <input type="password" name="password">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="qTitle" id="qTitle">

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

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 404 | ZeroHedge 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 Present
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 5 pass AA only
title ZeroHedge
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · top of page (header area)
a Join Premium
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contributors
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · top of page (header area)
span Channels
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a All
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Partners
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a The Market Ear
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a SpotGamma
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Store
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Donate
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span More
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a RSS
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a About
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
a Advertise
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Login3.66:13.0:1
#000000
#666666
Pass
h3 BY Portfolio Armor3.66:13.0:1
#000000
#666666
Pass
h3 BY ammodotcom3.66:13.0:1
#000000
#666666
Pass
h3 BY quoth the raven3.66:13.0:1
#000000
#666666
Pass
h3 Today's Top Stories3.66:13.0:1
#000000
#666666
Pass
title ZeroHedge1.02:14.5:1
#000000
#040404
Fail
a Home1.02:14.5:1
#000000
#040404
Fail
a Join Premium1.02:14.5:1
#000000
#040404
Fail
a Contributors1.02:14.5:1
#000000
#040404
Fail
span Channels3.66:14.5:1
#000000
#666666
Fail
a All3.66:14.5:1
#000000
#666666
Fail
span Partners3.66:14.5:1
#000000
#666666
Fail
a The Market Ear3.66:14.5:1
#000000
#666666
Fail
a SpotGamma3.66:14.5:1
#000000
#666666
Fail
a Store3.66:14.5:1
#000000
#666666
Fail
a Donate3.66:14.5:1
#000000
#666666
Fail
span More3.66:14.5:1
#000000
#666666
Fail
a RSS3.66:14.5:1
#000000
#666666
Fail
a About3.66:14.5:1
#000000
#666666
Fail
a Advertise3.66:14.5:1
#000000
#666666
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 89/100 — 3 failing, 24 passed
REVIEW
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
35m ago div.PolymarketWidget_container__r11vx > div.PolymarketWidget_card__viSl5 > div.PolymarketWidget_sourceLine__jxB9S > span.PolymarketWidget_time__SwRyU
1% div.PolymarketWidget_markets__FfKdn > a.PolymarketWidget_market__VmD87 > div.PolymarketWidget_marketBar__u_u1w > span.PolymarketWidget_marketOdds__AqIJc
$378K vol div.PolymarketWidget_markets__FfKdn > a.PolymarketWidget_market__VmD87 > div.PolymarketWidget_marketBar__u_u1w > span.PolymarketWidget_volume___cMCs
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

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 > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu
div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu div > article.NewArticle_teaser__jQRQd > div.NewArticle_imageWrapper__AIPsK > a.NewArticle_rel__tBjfu

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DISCRIMINATION NOTICE footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a
PRIVACY POLICY footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a
DISCLOSURE footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a
DISCLAIMER footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a
PRIVACY AND COOKIE SETTINGS footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a
ADVERTISE WITH ZEROHEDGE footer.Footer_container__pP_Gj > ul.Footer_nav__ok3sF > li > a

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]`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.
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
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Elements with visible text labels have matching accessible names.
`[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
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.
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>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
20 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
34 images 14 good alt text 20 decorative
All images have appropriate alt text.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: ZeroHedge
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name ZeroHedge 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name ZeroHedge Display Mode standalone Theme Color #222222 Background Color #FFFFFF Icons 2 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback