Skip to content
https://ewg.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
8 navigation landmark(s) detected
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 8 <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
Heading Hierarchy
24 headings, 1 skip(s)
REVIEW
24 headings, 1 skip(s)
Info::
Single H1 present
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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Search
  • H2 Mega Menu
  • H2 Who We Are
  • H2 Areas of Focus
  • H2 Key Issues
  • H2 (empty)
  • H3 Women's Health
  • H3 Food Chemicals
  • H2 News & Insights
  • H2 Header Utility Menu
  • H1 EARTH DAY MATCH
  • H3 Tap Water Database skipped
  • H3 EWG's Guide to Sunscreens
  • H3 EWG's 2026 Shopper's Guide to Pesticides in Produce™
  • H3 Skin Deep®
  • H3 Guide to Healthy Cleaning
  • H3 Guide to Solar Energy
  • H3 Interactive map: Tracking state food chemical regulation in the U.S.
  • H3 EWG’s 2026 Shopper’s Guide to Pesticides in Produce™ finds widespread PFAS pesticide residue on non-organic fruits and vegetables
  • H3 California bill would ban toxic ‘forever chemical’ pesticides contaminating nearly 40% of state-grown non-organic produce
  • H3 Natural and artificial flavor: What's the difference?
  • H3 EWG evaluation of food chemicals: Sucralose
  • H2 Footer -- Footer menu
  • H2 Footer Utility Menu

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

B
Alt Text Quality
1 of 11 images have issues
REVIEW
1 of 11 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
11 images 9 good alt text 1 decorative 1 missing
IssueCount
missing1 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

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#site-searchsearchSearch this Sitefor/id
#site-search2searchSearch this Sitefor/id
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

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

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

10 pass 10 fail WCAG AA
title Environmental Working Group – EARTH DA…
4.47:1
#000000
on
#0F854A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
4.47:1
#000000
on
#0F854A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Who We Are
2.58:1
#000000
on
#4F504A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Open submenu
2.10:1
#000000
on
#444337
needs 4.5:1 (normal text)
16px · top of page (header area)
a Areas of Focus
2.02:1
#000000
on
#434032
needs 4.5:1 (normal text)
16px · above the fold
span Open submenu
2.12:1
#000000
on
#4B413C
needs 4.5:1 (normal text)
16px · above the fold
a Consumer Guides
1.65:1
#000000
on
#38312F
needs 4.5:1 (normal text)
16px · above the fold
a Research
1.33:1
#000000
on
#282120
needs 4.5:1 (normal text)
16px · above the fold
a News & Insights
1.21:1
#000000
on
#1E1919
needs 4.5:1 (normal text)
16px · above the fold
span Open submenu
2.52:1
#000000
on
#60493D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 EARTH DAY MATCH16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Search16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Mega Menu16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Who We Are16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Areas of Focus16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Key Issues16.16:13.0:1
#000000
#CFE9CA
Pass
h2 News & Insights16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Header Utility Menu16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Footer -- Footer men…16.16:13.0:1
#000000
#CFE9CA
Pass
h2 Footer Utility Menu16.16:13.0:1
#000000
#CFE9CA
Pass
title Environmental Workin…4.47:14.5:1
#000000
#0F854A
Fail
span Menu4.47:14.5:1
#000000
#0F854A
Fail
a Who We Are2.58:14.5:1
#000000
#4F504A
Fail
span Open submenu2.10:14.5:1
#000000
#444337
Fail
a Areas of Focus2.02:14.5:1
#000000
#434032
Fail
span Open submenu2.12:14.5:1
#000000
#4B413C
Fail
a Consumer Guides1.65:14.5:1
#000000
#38312F
Fail
a Research1.33:14.5:1
#000000
#282120
Fail
a News & Insights1.21:14.5:1
#000000
#1E1919
Fail
span Open submenu2.52:14.5:1
#000000
#60493D
Fail

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

B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 25 passed
REVIEW
82

Accessibility

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Dialog popup start body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-start
Dialog popup end body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-end

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
APRIL 13, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 24, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 20, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 19, 2026 div.field > div.field__items > div.field__item > time.datetime
GET MY FREE GUIDE div.froala-editor-button > p > span > span

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See which produce has the highest and lowest pesticide residues. div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
By submitting, you'll receive updates from EWG.  Unsubscribe any time or refer … div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
Continue to site div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div#poptinFormCloseText
GET MY FREE GUIDE div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div#poptinFormSubmitText > input#poptinFormSubmitButton
JUST RELEASED div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
2026 Dirty Dozen™  & Clean Fifteen™ div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
EMAIL* div.inputs-container > div.froala-editor-input > div#poptinDesignInputTextFieldEmail > input#poptinDesignInputTextFieldEmail
ZIP CODE* div.inputs-container > div.froala-editor-input > div#poptinDesignInputCustomField-CUSTOM_ZIPCODE > input#poptinDesignInputCustomField-CUSTOM_ZIPCODE
CELL (OPTIONAL) div.inputs-container > div.froala-editor-input > div#poptinDesignInputTextFieldPhone > input#poptinDesignInputTextFieldPhone
Dialog popup start body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-start
Dialog popup end body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-end

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
Tap Water Database div#tns1-item0 > article.node > div.node__content > h3.node-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.field__items > div.field__item > p > a.search-toggle div.field__items > div.field__item > p > a.search-toggle

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > a
Legal Disclaimer nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > a
Reprint Permission Information nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > a

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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
○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.
○`[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.
○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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 NAV "mega-menu-menu" MAIN CONTENTINFO footer

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

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 Working Group ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback