Accessibility

F

Heading Hierarchy

Action

119 headings, 40 skip(s)

FIX

119 headings, 40 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

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

H5 INSURERS
H1 ‘They deny the medication that is keeping you alive’: Patients wage grueling legal battles for lifesaving cancer drug
H5 By Brenda Medina / Apr 13, 2026 skipped
H5 OVERVIEW
H2 How Merck turned its wonder drug into a blockbuster — and priced out cancer patients worldwide
H5 By Sydney P. Freedberg / Apr 13, 2026 skipped
H5 KEYTRUDA
H2 Report: Merck’s blockbuster cancer drug topped $200,000 a year under Trump
H5 By Nicole Sadek / Apr 17, 2026 skipped
H5 COUNTERFEITS
H2 Counterfeiters cash in on the world’s bestselling cancer drug
H5 By Nicole Sadek / Apr 13, 2026 skipped
H5 Kinahan cartel
H2 Cartel boss Daniel Kinahan arrested in Dubai
H5 By David Kenner / Apr 17, 2026 skipped
H2 GIVE TO HELP US INVESTIGATE!
H5 PARTNER STORIES skipped
H3 A ‘burgeoning black market’, inflated dosing and the over-judicialization of health care: reporters around the world tell stories about Keytruda
H5 Apr 21, 2026 skipped
H5 INTERACTIVE
H3 How Merck uses patents to help maintain Keytruda’s exorbitant price
H5 Apr 13, 2026 skipped
H5 VIDEO
H3 WATCH: How Merck keeps Keytruda prices sky-high
H5 Apr 13, 2026 skipped
H5 FAQS
H3 Frequently asked questions about the Cancer Calculus investigation
H5 Apr 13, 2026 skipped
H5 Behind the scenes
H3 About the Cancer Calculus investigation
H5 Apr 13, 2026 skipped
H5 BEHIND THE SCENES
H3 Global headlines and a public reckoning: Ten years of the Panama Papers, part 3
H5 Apr 07, 2026 skipped
H5 Behind the scenes
H3 ICIJ’s investigations into systemic failures highlighted in 2025 annual report
H5 Apr 07, 2026 skipped
H5 IMPACT
H3 Judge orders Nazi-looted Modigliani linked to Panama Papers be returned to heirs
H5 Apr 06, 2026 skipped
H5 VIDEO
H3 WATCH: The Panama Papers — ten years of impact
H5 Apr 02, 2026 skipped
H5 VIDEO
H3 WATCH: The Panama Papers at 10 live panel event
H5 Apr 02, 2026 skipped
H5 BEHIND THE SCENES
H3 Behind the veil of secrecy: Ten years of the Panama Papers, part 2
H5 Apr 02, 2026 skipped
H5 IMPACT
H3 Ten years after the Panama Papers, enablers and tax cheats are still being brought to justice
H5 Apr 02, 2026 skipped
H5 BEHIND THE SCENES
H3 The story that rocked the world: Ten years of the Panama Papers, part 1
H5 Mar 31, 2026 skipped
H5 ACCOUNTABILITY
H3 France to try alleged Magnitsky Affair mastermind Dimitry Klyuev in absentia
H5 Mar 29, 2026 skipped
H5 IMPACT
H3 Canada revokes dozens of crypto firms’ registrations
H5 Mar 24, 2026 skipped
H5 CRYPTOCURRENCY
H3 Questions swirl around US plans for record $15B Prince Group crypto seizure
H5 Mar 18, 2026 skipped
H4 Cancer Calculus
H4 Damascus Dossier
H4 The Coin Laundry
H4 China Targets
H4 Caspian Cabals
H4 Swazi Secrets
H4 Cyprus Confidential
H4 Deforestation Inc.
H2 Cancer Calculus
H5 PARTNER STORIES skipped
H3 A ‘burgeoning black market’, inflated dosing and the over-judicialization of health care: reporters around the world tell stories about Keytruda
H5 By Isabella Cota - Apr 21, 2026 skipped
H5 KEYTRUDA
H3 Report: Merck’s blockbuster cancer drug topped $200,000 a year under Trump
H5 By Nicole Sadek - Apr 17, 2026 skipped
H5 OVERVIEW
H3 How Merck turned its wonder drug into a blockbuster — and priced out cancer patients worldwide
H5 By Sydney P. Freedberg - Apr 13, 2026 skipped
H2 Damascus Dossier
H5 PARTNER STORIES skipped
H3 Damascus Dossier stories from around the world
H5 By David Kenner - Dec 19, 2025 skipped
H5 Data methodology
H3 Inside the Damascus Dossier: From leaked images to verified data
H5 By Karrie Kehoe - Dec 10, 2025 skipped
H5 Damascus Dossier
H3 After 13 years of searching, a Syrian man learns his brother’s fate
H5 By David Kenner - Dec 04, 2025 skipped
H2 The Coin Laundry
H5 IMPACT skipped
H3 Canada revokes dozens of crypto firms’ registrations
H5 By Spencer Woodman - Mar 24, 2026 skipped
H5 CRYPTOCURRENCY
H3 Questions swirl around US plans for record $15B Prince Group crypto seizure
H5 By Spencer Woodman - Mar 18, 2026 skipped
H5 IMPACT
H3 Massachusetts sues Bitcoin Depot, alleging the crypto ATM operator knowingly facilitated crypto scams
H5 By Ben Dooley - Feb 26, 2026 skipped
H2 WANT TO KNOW WHEN WE PUBLISH?
H2 WATCH: The Panama Papers at 10 live panel event
H5 Apr 02, 2026 skipped
H3 WATCH: Inside The Coin Laundry — a live Q&A
H5 Nov 25, 2025 skipped
H3 ‘Censorship disguised as law’: Investigative journalists in Peru push back against government crackdown
H5 Nov 12, 2025 skipped
H3 ICIJ members and partners honored with top journalism prize
H5 Oct 09, 2025 skipped
H3 WATCH: Inside China Targets — a live panel with ICIJ reporters
H5 Jun 10, 2025 skipped
H2 Do you have a story about corruption, fraud, or abuse of power?
H5 (empty)
H5 About us
H5 Investigations
H5 More
H5 Follow us

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

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

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

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

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

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

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

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

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

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

Source: WCAG 2.4.6

F

Link & Button Quality

Action

51 issue(s) across 222 links and 11 buttons

FIX

51 issue(s) across 222 links and 11 buttons

41 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /; https://www.x.com/icijorg; https://www.instagram.com/icijorg; https://www.facebook.com/icijorg; https://www.whatsapp.com/channel/0029ValJAn32v1ItC3oOfv1F; https://bsky.app/profile/icij.org; /; /; / (+31 more)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: # ("More")

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://offshoreleaks.icij.org/; https://datashare.icij.org/; https://www.icij.org/newsletter; https://www.icij.org/topics/; https://www.icij.org/feed/; https://profile.google.com/cp/CgwvZy8xMmRwd2wyd2M

9 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navbar-toggler (#88 on page); button#navBarCollapse; button#navBarCollapse; button.navbar-toggler (#166 on page); button#navBarCollapse; button#navBarCollapse; button.navbar-toggler (#215 on page); button#navBarCollapse; button#navBarCollapse

174 link(s) with descriptive text

222 links

41 empty

1 generic text

6 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.x.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.instagram.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.facebook.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.whatsapp.com/channel/0029Val…	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/icij.org	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.x.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.instagram.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.facebook.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.whatsapp.com/channel/0029Val…	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/icij.org	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/news/2026/04/cartel…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/canc…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/pana…	(empty)	empty	Add link text or aria-label
https://www.icij.org/inside-icij/2026/04…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/pana…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/pana…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/chin…	China Targets	img no alt	Add alt attribute to the image
https://www.icij.org/investigations/casp…	Caspian Cabals	img no alt	Add alt attribute to the image
https://www.icij.org/investigations/cypr…	Cyprus Confidential	img no alt	Add alt attribute to the image
https://www.icij.org/investigations/defo…	Deforestation Inc.	img no alt	Add alt attribute to the image
#	More	generic text	Replace with descriptive text
Before: More Suggested: #
https://www.icij.org/investigations/pana…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/pana…	(empty)	empty	Add link text or aria-label
https://www.icij.org/investigations/coin…	(empty)	empty	Add link text or aria-label
https://www.icij.org/news/2025/11/censor…	(empty)	empty	Add link text or aria-label
https://icij.org	(empty)	empty	Add link text or aria-label
https://offshoreleaks.icij.org/	Offshore Leaks Database	new tab	Add '(opens in new tab)' to text
https://datashare.icij.org/	Datashare	new tab	Add '(opens in new tab)' to text
https://www.icij.org/newsletter	Newsletter	new tab	Add '(opens in new tab)' to text
https://www.icij.org/topics/	Topics	new tab	Add '(opens in new tab)' to text
https://www.icij.org/feed/	RSS Feed	new tab	Add '(opens in new tab)' to text
https://profile.google.com/cp/CgwvZy8xMm…	Google News	new tab	Add '(opens in new tab)' to text
https://www.x.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.instagram.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.reddit.com/user/ICIJ/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/icijorg	(empty)	empty	Add link text or aria-label
https://www.whatsapp.com/channel/0029Val…	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/icij.org	(empty)	empty	Add link text or aria-label
https://www.threads.net/@icijorg	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/interna…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

176 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /; https://www.x.com/icijorg; https://www.instagram.com/icijorg; https://www.facebook.com/icijorg; https://www.whatsapp.com/channel/0029ValJAn32v1ItC3oOfv1F; https://bsky.app/profile/icij.org; /; /; / (+31 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

# ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://offshoreleaks.icij.org/; https://datashare.icij.org/; https://www.icij.org/newsletter; https://www.icij.org/topics/; https://www.icij.org/feed/; https://profile.google.com/cp/CgwvZy8xMmRwd2wyd2M

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.navbar-toggler (#88 on page); button#navBarCollapse; button#navBarCollapse; button.navbar-toggler (#166 on page); button#navBarCollapse; button#navBarCollapse; button.navbar-toggler (#215 on page); button#navBarCollapse; button#navBarCollapse

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

D

Web Manifest

Action

Not found

FIX

Not found

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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)

Skip navigation link detected

1 navigation landmark(s) detected

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="search" name="q" id="q">

1 control(s) properly labeled

3 controls

1 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#input-email	email	Stories in your inbox	for/id
#q	search	(Enter a search term)	placeholder only
input	submit	(none)	none

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

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.

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 Consortium of Investigativ…

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 How Merck turned its…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Report: Merck’s bl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Counterfeiters cash …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cartel boss Daniel K…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 GIVE TO HELP US INVE…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 WANT TO KNOW WHEN WE…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 WATCH: The Panama Pa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Do you have a story …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A ‘burgeoning blac…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Report: Merck’s bl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How Merck turned its…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Damascus Dossier sto…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Inside the Damascus …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 After 13 years of se…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Canada revokes dozen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Questions swirl arou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Massachusetts sues B…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title International Consor…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	1.00:1	4.5:1	#000000	#000000	Fail
a Investigations	20.82:1	4.5:1	#000000	#FEFEFE	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.

B

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 24 passed

REVIEW

87

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.bg-dark > div.d-flex > span.open-btn > button.navbar-toggler `nav.bg-dark > div.d-flex > span.open-btn > button.navbar-toggler`
nav.bg-dark > div.d-flex > span.open-btn > button#navBarCollapse `nav.bg-dark > div.d-flex > span.open-btn > button#navBarCollapse`

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
header#header-navbar > nav.bg-dark > div.navbar-brand > a.vue-workspace `header#header-navbar > nav.bg-dark > div.navbar-brand > a.vue-workspace`
div.col-12 > article.row > div.align-self-center > a `div.col-12 > article.row > div.align-self-center > a`
div.col-12 > article.row > div.align-self-center > a `div.col-12 > article.row > div.align-self-center > a`
div.col-12 > article.row > div.align-self-center > a `div.col-12 > article.row > div.align-self-center > a`
div.col-12 > article.row > div.align-self-center > a `div.col-12 > article.row > div.align-self-center > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.col-12 > article.row > div.col-5 > a `div.col-12 > article.row > div.col-5 > a`
div.row > div.col-12 > div.row > a `div.row > div.col-12 > div.row > a`
div.col-12 > div.row > div.col-sm-12 > a `div.col-12 > div.row > div.col-sm-12 > a`
div.col-12 > article.row > div.col-6 > a `div.col-12 > article.row > div.col-6 > a`
div.col-12 > article.row > div.col-6 > a `div.col-12 > article.row > div.col-6 > a`
div.row > div.col-12 > h5.text-uppercase > a.brand `div.row > div.col-12 > h5.text-uppercase > a.brand`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`
div.col-12 > div > div > a.d-inline-block `div.col-12 > div > div > a.d-inline-block`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
INSURERS `div.row > div.col-12 > article > h5.post-kicker`
OVERVIEW `article.row > div.col-7 > div.p-1 > h5.post-kicker`
KEYTRUDA `article.row > div.col-7 > div.p-1 > h5.post-kicker`
COUNTERFEITS `article.row > div.col-7 > div.p-1 > h5.post-kicker`
KINAHAN CARTEL `article.row > div.col-7 > div.p-1 > h5.post-kicker`
Popular topics: `div.container > div.row > div.col-12 > a.text-primary`
Donate `div.row > div.col-12 > div.donation-actions > a.btn`
Latest news `div.col-12 > ul.nav > li.nav-item > span.nav-link`
Recent investigations `div.col-md-12 > ul.mb-3 > li.nav-item > a.bg-light`
Meet the investigators `div.col-12 > ul.nav > li.nav-item > a.nav-link`
Leak to us `div.col-sm-12 > ul.nav > li.nav-item > a.nav-link`

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
BY BRENDA MEDINA / APR 13, 2026 `div.row > div.col-12 > article > h5.badge`
BY SYDNEY P. FREEDBERG / APR 13, 2026 `article.row > div.col-7 > div.p-1 > h5.badge`
BY NICOLE SADEK / APR 17, 2026 `article.row > div.col-7 > div.p-1 > h5.badge`
BY NICOLE SADEK / APR 13, 2026 `article.row > div.col-7 > div.p-1 > h5.badge`
BY DAVID KENNER / APR 17, 2026 `article.row > div.col-7 > div.p-1 > h5.badge`
PARTNER STORIES `div.col-12 > article.row > div.col-7 > h5.badge`
APR 21, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 13, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 13, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 13, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 13, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 07, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 07, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 06, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 02, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 02, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 02, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
APR 02, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
MAR 31, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
MAR 29, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
MAR 24, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
MAR 18, 2026 `div.col-12 > article.row > div.col-7 > h5.badge`
PARTNER STORIES `div.col-12 > div.border-bottom > a.archive-project-list__link > h5.badge-light`
BY ISABELLA COTA - APR 21, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY NICOLE SADEK - APR 17, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY SYDNEY P. FREEDBERG - APR 13, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
PARTNER STORIES `div.col-12 > div.border-bottom > a.archive-project-list__link > h5.badge-light`
BY DAVID KENNER - DEC 19, 2025 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY KARRIE KEHOE - DEC 10, 2025 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY DAVID KENNER - DEC 04, 2025 `article.row > div.col-12 > div.border-bottom > h5.p-0`
IMPACT `div.col-12 > div.border-bottom > a.archive-project-list__link > h5.badge-light`
BY SPENCER WOODMAN - MAR 24, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY SPENCER WOODMAN - MAR 18, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
BY BEN DOOLEY - FEB 26, 2026 `article.row > div.col-12 > div.border-bottom > h5.p-0`
APR 02, 2026 `div.col-12 > div.row > div.col-sm-12 > h5.p-0`
NOV 25, 2025 `div.col-12 > article.row > div.col-6 > h5.p-0`
NOV 12, 2025 `div.col-12 > article.row > div.col-6 > h5.p-0`
OCT 09, 2025 `div.col-12 > article.row > div.col-6 > h5.p-0`
JUN 10, 2025 `div.col-12 > article.row > div.col-6 > h5.p-0`
div.container > div.row > div.col-12 > h5.text-uppercase `div.container > div.row > div.col-12 > h5.text-uppercase`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○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.

○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.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A

Alt Text Quality

All 37 images OK

PASS

All 37 images OK

5 image(s) with alt text over 125 characters

18 decorative image(s) correctly marked

14 image(s) with good alt text

37 images 14 good alt text 18 decorative

Issue	Count
too long	5 image(s)

A

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - ICIJ ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓