Skip to content
https://ecowatch.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
40 headings
REVIEW
40 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Most recent: Climate
  • H3 Methane 101: Understanding the Second Most Important Greenhouse Gas
  • H3 New York Finalizes Rule for New Buildings to Be Electric
  • H3 Pristine Forest and Endangered Gorilla Habitat at Risk as Half of DRC Opened to Bids for Oil and Gas Drilling: Report
  • H3 Probiotic Found to Slow Disease Spread Among Florida Coral
  • H2 Methane 101: Understanding the Second Most Important Greenhouse Gas
  • H3 Culture
  • H3 ‘Poisoning the Well’ Authors Sharon Udasin and Rachel Frazin on PFAS Contamination and Why It ‘Has Not Received the Attention It Deserves’
  • H3 Facing Climate Anxiety With Visual Comedy: ‘World Without End’ Graphic Artist Christophe Blain
  • H3 First-Ever Mushroom Casket Burial in North America Could Signal Cultural Shift Toward More Planet-Friendly Traditions
  • H3 ‘Animals in War’ Film Anthology Tells Stories of Animals and Ecosystems Impacted by Russia’s War on Ukraine
  • H3 Meet the Winners of the 12th Annual UN World Oceans Day Photo Competition
  • H3 Join our Newsletter
  • H2 Editor’s Pick
  • H3 A Complete Guide to Chaos Gardening
  • H3 A Philosopher’s Guide to an Ethical Diet: A Conversation With Peter Singer
  • H3 ‘We Have Just Arrived’: Author Rick Bass on Writing and Activism in Montana
  • H3 ‘To Dye For’: The Toxic Evolution of Fast Fashion by Alden Wicker
  • H3 Tasty, Carbon-Negative Kelp Burgers Are ‘Everything That’s Right With the Food System’
  • H2 Editorial Contributors
  • H2 EcoWatch Explainers
  • H2 EcoWatch Reviews
  • H2 Climate
  • H3 Methane 101: Understanding the Second Most Important Greenhouse Gas
  • H3 New York Finalizes Rule for New Buildings to Be Electric
  • H3 Pristine Forest and Endangered Gorilla Habitat at Risk as Half of DRC Opened to Bids for Oil and Gas Drilling: Report
  • H3 Probiotic Found to Slow Disease Spread Among Florida Coral
  • H3 Earth Overshoot Day Reaches Record for Earliest Date
  • H2 Energy
  • H3 Methane 101: Understanding the Second Most Important Greenhouse Gas
  • H3 New York Finalizes Rule for New Buildings to Be Electric
  • H3 Pristine Forest and Endangered Gorilla Habitat at Risk as Half of DRC Opened to Bids for Oil and Gas Drilling: Report
  • H3 Earth Overshoot Day Reaches Record for Earliest Date
  • H3 Renewables Helped Prevent Blackouts on New England’s Hottest Day This Summer
  • H2 Conservation
  • H3 New York Finalizes Rule for New Buildings to Be Electric
  • H3 Mass Die-Off of Western Monarch Butterflies Linked to Pesticides, Study Finds
  • H3 Deepest-Known Animal Communities Found Almost Six Miles Below Sea Level
  • H3 Pristine Forest and Endangered Gorilla Habitat at Risk as Half of DRC Opened to Bids for Oil and Gas Drilling: Report
  • H3 Probiotic Found to Slow Disease Spread Among Florida Coral

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.4.6 / Google Search Central

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - EcoWatch ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Alt Text Quality
All 57 images OK
PASS
All 57 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
5 decorative image(s) correctly marked
Info::
51 image(s) with good alt text
57 images 51 good alt text 5 decorative
IssueCount
too long1 image(s)
A+
Form Accessibility
All 13 controls labeled
PASS
All 13 controls labeled
Info::
13 control(s) properly labeled
13 controls
13 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-form-1searchnone
#menu-search-form-2searchnone
your-emailemailnone
_mc4wp_subscribe_contact-form-7checkboxnone
inputsubmitnone
#mobile-search-form3searchnone
your-emailemailnone
_mc4wp_subscribe_contact-form-7checkboxnone
inputsubmitnone
newsletter-consentcheckboxnone
your-emailemailnone
_mc4wp_subscribe_contact-form-7checkboxnone
inputsubmitnone
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
h2 Methane 101: Underst…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Climate21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Energy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conservation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Most recent:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Methane 101: Underst…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New York Finalizes R…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pristine Forest and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Probiotic Found to S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Culture21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Poisoning the Wel…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Facing Climate Anxie…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 First-Ever Mushroom …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Animals in War’…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Meet the Winners of …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Join our Newsletter21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A Complete Guide to …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A Philosopher’s Gu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘We Have Just Arri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘To Dye For’: Th…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 94/100 — 2 failing, 29 passed
PASS
94

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
form.wpcf7-form > label > span.wpcf7-form-control-wrap > input.wpcf7-form-control form.wpcf7-form > label > span.wpcf7-form-control-wrap > input.wpcf7-form-control

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CLIMATE div.ew-row > div.ew-col-6 > article.home-post > a.home-post__category
FOOD AND AGRICULTURE div.slick-track > article.home-editor-picks__post > div.home-editor-picks__post-inner > a.home-post__category
1 of 5 div.home-editor-picks__post-inner > ul.home-editor-picks__posts-nav > li.home-editor-picks__posts-nav-active > button.home-editor-picks__posts-nav-item-js
2 of 5 div.home-editor-picks__post-inner > ul.home-editor-picks__posts-nav > li > button.home-editor-picks__posts-nav-item-js
3 of 5 div.home-editor-picks__post-inner > ul.home-editor-picks__posts-nav > li > button.home-editor-picks__posts-nav-item-js
4 of 5 div.home-editor-picks__post-inner > ul.home-editor-picks__posts-nav > li > button.home-editor-picks__posts-nav-item-js
5 of 5 div.home-editor-picks__post-inner > ul.home-editor-picks__posts-nav > li > button.home-editor-picks__posts-nav-item-js

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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.
○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