Skip to content
https://earthday.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
36 headings, 7 skip(s)
FIX
36 headings, 7 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Join Us
  • H3 Thank you for signing up
  • H4 EARTHDAY.ORG’s founders created and organized the very first Earth Day on April 22, 1970. Since then, Earth Day Network has been mobilizing over 1 billion people annually on Earth Day, and every oth
  • H2 Earth Day 2026: Our Power, Our Planet™
  • H2 This Earth Day, people of all backgrounds and generations are called to stand shoulder to shoulder in defense of the only home we share. Join us on Saturday, April 18, Earth Day on April 22, and throu
  • H2 With over 10,000 events, EARTHDAY.ORG's 2026 Event Map shows the community power taking place across the globe.
  • H2 EARTH DAY NEEDS YOU!
  • H2 Climate Education Goes Global
  • H4 Tracking mandatory climate education worldwide skipped
  • H2 We recognize the vital role of education in preparing communities to address the climate crisis. The European Union has taken a historic step by embedding climate education into school curricula from
  • H2 News and Stories
  • H2 The Green Skills Gap: 22 Minutes with Efrem Bycer
  • H2 Data Centers are the Hidden Costs to Your Power Bill, Water, and Community: 22 Minutes with Ashish Kapoor
  • H2 Good Jobs, Clean Future, and Earth Day’s Union Roots: 22 Minutes with Jason Walsh
  • H4 our Featured Work skipped
  • H2 Canopy Tree Project
  • H2 Join us in making a lasting impact with The Canopy Project! Since 2010, we've planted millions of trees globally, restoring forests in areas hit hardest by environmental challenges. By donating as lit
  • H2 Climate Education vs. The Climate Crisis
  • H2 Climate and environmental literacy, coupled with strong civic education, will create jobs, build a green consumer market and allow citizens to engage with their governments in a meaningful way to addr
  • H2 The Great Global Cleanup
  • H2 Get involved and help us create a waste-free world.
  • H2 Fashion For The Earth
  • H2 Fast fashion has completely revolutionized the apparel industry, but not for the better.
  • H2 Get Inspired!
  • H4 Take Action skipped
  • H2 Make a difference today. Explore actions you can take to protect our planet and join a global movement for environmental change.
  • H4 Toolkits skipped
  • H2 Knowledge is key to making an impact. Check out our toolkits to learn how anyone can help solve some of the world's most pressing issues.
  • H4 Quizzes​ skipped
  • H2 Test your knowledge and learn more about environmental issues. Challenge yourself and discover new ways to make a positive impact.
  • H2 We Look Good On You
  • H4 EARTHDAY.ORG in the News skipped
  • H4 Earth Day Network Supporters
  • H4 OUR PARTNERS
  • H2 Join Earth Day Today!
  • H6 International Network skipped

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

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

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::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
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.
C
Alt Text Quality
Action
5 of 75 images have issues
REVIEW
5 of 75 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.
Warning::
2 image(s) with filename as alt text
Warning::
2 image(s) with generic alt text
Info::
12 decorative image(s) correctly marked
Info::
58 image(s) with good alt text
75 images 58 good alt text 12 decorative 4 generic 1 missing
IssueCount
missing1 image(s)
filename2 image(s)
generic2 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
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 This Earth Day, peop…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 With over 10,000 eve…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 We recognize the vit…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 News and Stories12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Join us in making a …12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Climate and environm…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Get involved and hel…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Fast fashion has com…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Get Inspired!12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Make a difference to…12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Knowledge is key to …12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Test your knowledge …12.96:13.0:1
#000000
#C8CCCC
Pass
h2 Join Earth Day Today…12.96:13.0:1
#000000
#C8CCCC
Pass
h3 Thank you for signin…12.96:13.0:1
#000000
#C8CCCC
Pass
title Earth Day: The Offic…5.80:14.5:1
#000000
#7E8797
Pass
a Skip to Content9.49:14.5:1
#000000
#A9AFB6
Pass
h4 Join Us12.71:13.0:1
#000000
#C6CACB
Pass
p An unexpected error …10.35:14.5:1
#000000
#ADB8BB
Pass
label First Name *7.37:14.5:1
#000000
#869DA4
Pass
label Last Name *7.46:14.5:1
#000000
#879EA4
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 7 failing, 23 passed
REVIEW
75

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.

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
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-contact > p > a > img div.footer-contact > p > a > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > iframe body.home > iframe

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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.col-sm-12 > div.footer-logo > p > a div.col-sm-12 > div.footer-logo > p > a
div.col-sm-12 > div.footer-contact > p > a div.col-sm-12 > div.footer-contact > p > 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.

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
DONATE TODAY div.elementor-button-wrapper > a#homepage_hero_donate > span.elementor-button-content-wrapper > span.elementor-button-text
GET INVOLVED div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Samantha Burchard div.eael-entry-footer > div.eael-entry-meta > span.eael-posted-by > a
Sarah Sternhagen div.eael-entry-footer > div.eael-entry-meta > span.eael-posted-by > a
Darby Burgett div.eael-entry-footer > div.eael-entry-meta > span.eael-posted-by > a
DONATE TODAY div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
REGISTER YOUR UPCOMING CLEANUP div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
SHOP NOW div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
SEE ALL 267 ARTICLES div.elementor-widget-container > div.elementor-shortcode > a.news-count-btn > span
ALL OUR PARTNERS div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
PARTNER WITH US div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
SIGN UP div > form.signup > button.btn > span
div.container > div.d-block > form.signup > button.btn div.container > div.d-block > form.signup > button.btn
div.container > div.d-block > p.text-center > a.btn div.container > div.d-block > p.text-center > a.btn
nav > ul > li > a nav > ul > li > a
nav > ul > li > a nav > ul > li > a

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
Tracking mandatory climate education worldwide div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
OUR FEATURED WORK div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
Take Action div.e-con-inner > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
Toolkits div.e-con-inner > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
Quizzes​ div.e-con-inner > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
EARTHDAY.ORG IN THE NEWS div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
div.row > div.col-sm-12 > div.footer-network > h6.footer-widget-title div.row > div.col-sm-12 > div.footer-network > h6.footer-widget-title

These are opportunities to improve keyboard navigation in your application.

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
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot div.ue_listing_carousel > div#uc_ue_listing_carousel_elementor_49144894 > div.owl-dots > button.owl-dot
div.footer-network > ul > li > a div.footer-network > ul > li > a
div.footer-network > ul > li > a div.footer-network > ul > li > a

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[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
ARIA IDs are unique
No form fields have multiple labels
`<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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
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
11 landmarks
PASS
11 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.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV 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

A
Form Accessibility
1 of 17 controls have issues
PASS
1 of 17 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="zip" id="footer-signup-zip">
Info::
16 control(s) properly labeled
17 controls
16 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#modal-first-nametextFirst Name *for/id
#modal-last-nametextLast Name *for/id
#modal-emailemailEmail address *for/id
#modal-mobile-numbertextMobile numberfor/id
#modal-countryselectCountry *for/id
#modal-email-opt-incheckboxI want to receive email updates from EARTHDAY.ORG.for/id
#modal-mobile-opt-incheckboxI want to receive text updates from EARTHDAY.ORG.for/id
#search1searchSearch:for/id
#search2searchSearch:for/id
#survey-map-date-fromdateFromfor/id
#survey-map-date-todateTofor/id
#block_b24e64d526cdb5a4db8833165166f9d9-emailemailEmail address *for/id
#block_b24e64d526cdb5a4db8833165166f9d9-ziptextZip Code *for/id
#block_b24e64d526cdb5a4db8833165166f9d9-email-opt-incheckboxI want to receive email updates from EARTHDAY.ORG.for/id
#footer-signup-emailemailEmail addressfor/id
#footer-signup-email-opt-incheckboxI want to receive email updates from EARTHDAY.ORG.for/id
#footer-signup-ziptext(Zip code *)placeholder only

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

<input type="text" name="zip" id="footer-signup-zip">

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

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 | Earth Day 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