Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure17 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
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
BAlt Text Quality1 of 63 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
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.
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
BLink & Button Quality4 issue(s) across 131 links and 28 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /protect | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Protect | |||
| https://vitalsigns.edf.org/story/coal-pl… | Explainer Coal plant for… | img no alt | Add alt attribute to the image |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Generic link text like 'click here' doesn't describe the destination.
/protect ("Learn more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Icon-only buttons need an aria-label so screen readers can announce them.
button.change-slide (#603 on page); button.change-slide (#605 on page); button.change-slide (#607 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
BWeb ManifestValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 19 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 We are Environmental… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h1 Today only: 300% mat… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 Together, we're find… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 Issues we address | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 How we get results t… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 Latest stories | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 Maximize your impact | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h2 Another easy way to … | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Scientific evidence | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Economic sustainabil… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Powerful partnership… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Climate justice | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Strong advocacy | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Vibrant culture | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Deep dive | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Explainer | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Analysis | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 In Pictures | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| h3 Maximize your impact… | 1.94:1 | 3.0:1 | #000000 | #3D3D3E | Fail |
| title Environmental Defens… | 19.24:1 | 4.5:1 | #000000 | #F2F5FC | 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.
AHeading Hierarchy27 headingsPASS
- H1 We are Environmental Defense Fund
- H2 Together, we're finding the ways that work.
- H2 Issues we address
- H3 Energy transition
- H3 Natural solutions
- H3 Sustainable fishing
- H3 Hydrogen
- H3 Clean Air
- H3 Methane
- H3 Agriculture
- H3 Safer chemicals
- H2 How we get results that last
- H3 Scientific evidence
- H3 Economic sustainability
- H3 Powerful partnerships
- H3 Climate justice
- H3 Strong advocacy
- H3 Vibrant culture
- H2 Latest stories
- H3 Deep dive
- H3 Explainer
- H3 Analysis
- H3 In Pictures
- H2 Maximize your impact
- H3 Maximize your impact this Earth Day
- H2 Another easy way to help
- H1 Today only: 300% match on all gifts duplicate H1
A page should have only one H1. Multiple H1s dilute the document outline.
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
AForm Accessibility1 of 4 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #TopnavSearchFormInput | search | Search this site… | aria-label |
| aria-label | |||
| id | text | Name | aria-label |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit">
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
A404 Error PageHTTP 404, custom pagePASS
AFavicon & Branding7 icon(s) detectedPASS
A+Lighthouse Accessibility AuditsScore 97/100 — 1 failing, 35 passedPASS
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
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
We use cookies to personalize content and ads, to provide social media features… body.not-logged-in > div#cc--main > div#cc_div > div#cm |
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.