Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 REVIEW 7 FIX

Form Accessibility

Action

4 of 7 controls have issues

FIX

4 of 7 controls have issues

3 control(s) without accessible label

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

Got: <input type="email">; <input type="text" name="person[phone]" id="person_phone">; <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input name="query">

3 control(s) properly labeled

7 controls

3 labeled

1 placeholder only

3 unlabeled

Control	Type	Label	Method
#location-search-text-main-menu	input	Change location	aria-label
#location-search-text-main-menu	input	Change location	aria-label
#footer_search	text	Enter terms to search	for/id
query	input	(Search)	placeholder only
#person_phone	text	(none)	none
input	submit	(none)	none
input	email	(none)	none

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

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

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

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

Link & Button Quality

Action

11 issue(s) across 101 links and 10 buttons

FIX

11 issue(s) across 101 links and 10 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content; a (#470 on page); a (#472 on page); a (#500 on page); a (#502 on page); a (#506 on page); a (#508 on page)

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /topics/international-climate-policy; /topics/international-climate-policy; https://facebook.com/sierraclub; https://instagram.com/sierraclub; https://www.linkedin.com/company/sierraclub/; https://www.youtube.com/user/NationalSierraClub; https://www.threads.net/@sierraclub; https://www.tiktok.com/@sierraclubofficial

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.d-md-block (#157 on page); button.notification-btn (#191 on page); button.btn (#303 on page); button.btn (#458 on page)

86 link(s) with descriptive text

101 links

7 empty

0 generic text

8 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/topics/international-climate-policy	International Climate	new tab	Add '(opens in new tab)' to text
/topics/international-climate-policy	International Climate	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://facebook.com/sierraclub	Find us on facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/sierraclub	Find us on instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/sierrac…	Find us on linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/NationalSie…	Find us on youtube	new tab	Add '(opens in new tab)' to text
https://www.threads.net/@sierraclub	Find us on threads	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sierracluboffici…	Find us on tiktok	new tab	Add '(opens in new tab)' to text
<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
<button>	(empty)	empty	Add button text or aria-label

92 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content; a (#470 on page); a (#472 on page); a (#500 on page); a (#502 on page); a (#506 on page); a (#508 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

/topics/international-climate-policy; /topics/international-climate-policy; https://facebook.com/sierraclub; https://instagram.com/sierraclub; https://www.linkedin.com/company/sierraclub/; https://www.youtube.com/user/NationalSierraClub; https://www.threads.net/@sierraclub; https://www.tiktok.com/@sierraclubofficial

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.d-md-block (#157 on page); button.notification-btn (#191 on page); button.btn (#303 on page); button.btn (#458 on page)

Why this matters

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

Action

12 headings, 2 skip(s)

REVIEW

12 headings, 2 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H5 dotOrg Membership Navigation
H5 dotOrg Primary Navigation
H1 Earth Day 3X Match
H1 Earth Month Takeover 2026 duplicate H1
H3 This Earth Day your support will go 3X as far in protecting our lands and wildlife. skipped
H3 Make 3X the Impact
H2 3X Your Impact
H2 Remind Me Later
H2 About the Sierra Club
H2 Get in Touch
H2 More from The Sierra Club
H6 Can nature count on you? skipped

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

3 of 12 images have issues

REVIEW

3 of 12 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

9 image(s) with good alt text

12 images 9 good alt text 3 missing

Issue	Count
missing	3 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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title SC Logo_Horiz Web Black ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 11 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Earth Day 3X Match	8.84:1	3.0:1	#000000	#66B4BE	Pass
h2 3X Your Impact	8.84:1	3.0:1	#000000	#66B4BE	Pass
h2 Remind Me Later	8.84:1	3.0:1	#000000	#66B4BE	Pass
h2 About the Sierra Clu…	8.84:1	3.0:1	#000000	#66B4BE	Pass
h2 Get in Touch	8.84:1	3.0:1	#000000	#66B4BE	Pass
h2 More from The Sierra…	8.84:1	3.0:1	#000000	#66B4BE	Pass
h3 This Earth Day your …	8.84:1	3.0:1	#000000	#66B4BE	Pass
h3 Make 3X the Impact	8.84:1	3.0:1	#000000	#66B4BE	Pass
title Earth Day 3X Match -…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menu	6.40:1	4.5:1	#000000	#339BA9	Pass
a Madrid, MD	4.54:1	4.5:1	#000000	#108283	Pass
li Displaying stories, …	4.54:1	4.5:1	#000000	#108283	Pass
span Madrid, MD	4.54:1	4.5:1	#000000	#108283	Pass
p Your nearest Sierra …	4.54:1	4.5:1	#000000	#108283	Pass
a International Climat…	4.54:1	4.5:1	#000000	#108283	Pass
a View all chapters	4.54:1	4.5:1	#000000	#108283	Pass
label Change Location:	4.54:1	4.5:1	#000000	#108283	Pass
button Update	4.54:1	4.5:1	#000000	#108283	Pass
a Turn location off	4.54:1	4.5:1	#000000	#108283	Pass
a Login	4.54:1	4.5:1	#000000	#108283	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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 6 failing, 23 passed

REVIEW

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
3X Your Impact Starting today, your Earth Day gift will go three times as far.… `div.container-lg > div.region > div#block-boot5pt-lightboxbootstrapmodalsetatbottomofpage > div#myModal`

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.

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