Skip to content
https://mongabay.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
0
PASS
6
INFO
0
Checks
13
6 PASS 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
Heading Hierarchy
Action
71 headings, 17 skip(s)
FIX
71 headings, 17 skip(s)
Warning::
Multiple H1 headings (28 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 Latest
  • H3 Vaupés River contamination identified near rapidly expanding Amazonian town
  • H3 At the U.N., Indigenous leaders tackle how to enforce global climate court rulings
  • H3 Chinese court cases reveal most trafficked rhino horns come from Southern Africa
  • H3 We can navigate conservation’s ‘epidemic of suffering’ by building a culture of care (commentary)
  • H3 A campaign to protect one of the planet’s only expanding kelp forests takes shape
  • H3 Fossil fuel subsidies and high costs stall energy transition across rural Indonesia
  • H4 Top stories
  • H1 Chinese court cases reveal most trafficked rhino horns come from Southern Africa
  • H3 Asia’s longest free-flowing river contaminated by arsenic linked to Myanmar mines skipped
  • H3 Studying the world’s largest gathering of forest elephants with sound and field observation
  • H3 Chimp ‘civil war’ follows rare community split in a Ugandan national park
  • H3 In Tasmania, the mines have closed but the rivers remember
  • H1 Subscribe duplicate H1
  • H1 We’re a nonprofit duplicate H1
  • H1 News and Inspiration from Nature's Frontline. duplicate H1
  • H1 Special issues connect the dots between stories duplicate H1
  • H3 Primate Planet skipped
  • H1 Defying conflict to track the world’s rarest chimpanzees duplicate H1
  • H1 Orangutans rescued undergo re-training to return to the wild duplicate H1
  • H1 Natural bridges to reconnect the last Javan gibbons duplicate H1
  • H1 What singing lemurs can tell us about the origin of music duplicate H1
  • H4 More specials skipped
  • H3 Who controls Mexico’s Yaqui River?
  • H3 Beyond the screen: DCEFF
  • H3 The Dutch Nitrogen Crisis
  • H1 Free and open access to credible information duplicate H1
  • H1 Listen to Nature with thought-provoking podcasts duplicate H1
  • H3 Coexisting with America’s growing urban coyote population is easier than you think skipped
  • H1 Watch unique videos that cut through the noise duplicate H1
  • H1 Defying conflict to track the world’s rarest chimpanzees duplicate H1
  • H3 Lab-made jaguar: Is cloning a solution to extinction? skipped
  • H3 In search of the tiny toad that stopped a dam
  • H3 Why is cockfighting a risk to Peru’s rarest fish?
  • H3 The most desirable songbird in Indonesia is disappearing from the wild
  • H1 We’re a nonprofit duplicate H1
  • H1 In-depth feature stories reveal context and insight duplicate H1
  • H5 Feature story skipped
  • H1 George Schaller: The field biologist who helped redefine conservation duplicate H1
  • H5 Feature story skipped
  • H1 Can nature outcompete war in Eastern Congo? duplicate H1
  • H5 Feature story skipped
  • H1 Nearly a million birds shipped from Africa to Asia in 15 years; canaries top the list duplicate H1
  • H5 Feature story skipped
  • H1 In Brazil, unfinished water project leaves Indigenous villages without safe water duplicate H1
  • H5 Feature story skipped
  • H1 George Schaller: The field biologist who helped redefine conservation duplicate H1
  • H5 Feature story skipped
  • H1 Can nature outcompete war in Eastern Congo? duplicate H1
  • H5 Feature story skipped
  • H1 Nearly a million birds shipped from Africa to Asia in 15 years; canaries top the list duplicate H1
  • H5 Feature story skipped
  • H1 In Brazil, unfinished water project leaves Indigenous villages without safe water duplicate H1
  • H5 Feature story skipped
  • H1 George Schaller: The field biologist who helped redefine conservation duplicate H1
  • H5 Feature story skipped
  • H1 Can nature outcompete war in Eastern Congo? duplicate H1
  • H1 Quickly stay updated with our news shorts duplicate H1
  • H3 Translucent microsnail discovered in Cambodia: Photo of the week skipped
  • H3 Five ‘lost’ bird species rediscovered in 2025
  • H3 Climate displacement in Africa: Court opinion could define states’ obligations
  • H3 Chernobyl’s radioactive landscape is a testament to nature’s resilience and survival spirit
  • H3 A red flower found nowhere else loses ground as mining expands in Brazil’s Amazon
  • H3 Rehab center opens for Brazil’s golden-headed lion tamarins amid urban sprawl threat
  • H2 (empty)
  • H1 Share this short duplicate H1
  • H1 Subscribe duplicate H1
  • H4 News formats skipped
  • H4 About
  • H4 External links
  • H4 Social media

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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
Alt Text Quality
Action
9 of 50 images have issues
FIX
9 of 50 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
5 image(s) with filename as alt text
Info::
4 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
50 images 29 good alt text 8 decorative 5 generic 4 missing
IssueCount
missing4 image(s)
filename5 image(s)
too long4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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: #669900
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.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" id="copy-url">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#copy-urltext(none)none

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

<input type="text" id="copy-url">

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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found - Environmental News Custom Styling Navigation Homepage Link Search Form
A
Favicon & Branding
13 icon(s) detected
PASS
13 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Conservation News
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Conservation News 192×192 icon 512×512 icon Start URL https://news-mongabay-com.mongabay.com?utm_source=PWA Display Mode standalone
Name Conservation News Display Mode standalone Theme Color #669900 Background Color #ffffff Icons 3 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Chinese court cases …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Subscribe21.00:13.0:1
#000000
#FFFFFF
Pass
h1 We’re a nonprofit21.00:13.0:1
#000000
#FFFFFF
Pass
h1 News and Inspiration…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 connect the dots bet…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Defying conflict to …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Orangutans rescued u…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Natural bridges to r…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 What singing lemurs …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Free and open access…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Listen to Nature wit…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Watch unique21.00:13.0:1
#000000
#FFFFFF
Pass
h1 that cut through the…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Defying conflict to …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 We’re a nonprofit21.00:13.0:1
#000000
#FFFFFF
Pass
h1 In-depth21.00:13.0:1
#000000
#FFFFFF
Pass
h1 reveal context and i…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 George Schaller: The…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Can nature outcompet…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Nearly a million bir…21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 18 passed
PASS
91

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
Latest short video main.mx-auto > section.mt-6 > header.mb-4 > h2.text-body
Featured main.mx-auto > section.mt-6 > header.mb-4 > h2.text-body
Aimee Gabay div.grid > a.relative > p.space-x-1 > span
1 hour ago div.grid > a.relative > p.space-x-1 > span
Joseph Lee div.grid > a.relative > p.space-x-1 > span
1 hour ago div.grid > a.relative > p.space-x-1 > span
Spoorthy Raman div.grid > a.relative > p.space-x-1 > span
3 hours ago div.grid > a.relative > p.space-x-1 > span
Jen Miller div.grid > a.relative > p.space-x-1 > span
9 hours ago div.grid > a.relative > p.space-x-1 > span
Alexandra Talty div.grid > a.relative > p.space-x-1 > span
10 hours ago div.grid > a.relative > p.space-x-1 > span
Luh De Suriyani div.grid > a.relative > p.space-x-1 > span
11 hours ago div.grid > a.relative > p.space-x-1 > span
Malaka Rodrigo div.grid > a.relative > p.space-x-1 > span
13 hours ago div.grid > a.relative > p.space-x-1 > span
Rhett Ayers Butler div.grid > a.relative > p.space-x-1 > span
17 hours ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
1 week ago div.grid > a.relative > p.space-x-1 > span
Leo Plunkett div.grid > a.relative > p.space-x-1 > span
1 week ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
2 weeks ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
3 weeks ago div.grid > a.relative > p.space-x-1 > span
Gustavo Fonseca div.grid > a.relative > p.space-x-1 > span
3 weeks ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
4 weeks ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Felipe Rosa div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Romi Castagnino div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Mike DiGirolamo div.grid > a.relative > p.space-x-1 > span
1 month ago div.grid > a.relative > p.space-x-1 > span
Rizky Maulana Yanuar div.grid > a.relative > p.space-x-1 > span
2 months ago div.grid > a.relative > p.space-x-1 > span
Sandy Watt div.grid > a.relative > p.space-x-1 > span
2 months ago div.grid > a.relative > p.space-x-1 > span
Romi Castagnino div.grid > a.relative > p.space-x-1 > span
2 months ago div.grid > a.relative > p.space-x-1 > span
Sam Lee div.grid > a.relative > p.space-x-1 > span
3 months ago div.grid > a.relative > p.space-x-1 > span
You Might Like main.mx-auto > section.mt-6 > header.mb-4 > h2.text-body
World News main.mx-auto > section.mt-6 > header.mb-4 > h2.text-body
12 November 2025 a.block > div.space-y-4 > div.flex > p.whitespace-nowrap
29 October 2025 a.block > div.space-y-4 > div.flex > p.whitespace-nowrap
28 October 2025 a.block > div.space-y-4 > div.flex > p.whitespace-nowrap

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
body.rowan_65d8a8fa-module__ZluQfW__variable > div.relative > header#site-header > a body.rowan_65d8a8fa-module__ZluQfW__variable > div.relative > header#site-header > a

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.

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 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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
Form elements have associated labels
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback