Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Form Accessibility

Action

6 of 13 controls have issues

FIX

6 of 13 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="submit" name="op" id="edit-submit">; <input type="submit">; <input type="submit" name="op" id="edit-submit--2">

3 control(s) rely on placeholder only

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

Got: <input type="number">; <input type="number">; <input type="search" name="title">

7 control(s) properly labeled

13 controls

7 labeled

3 placeholder only

3 unlabeled

Control	Type	Label	Method
search	text	Search Audubon	aria-label
#near-me-dropdown-zip-code	text	Zip Code	for/id
#edit-emailaddress	email	To sign up to our email newsletter with the latest programs and initiatives	aria-label
#edit-zip	tel	Zip	for/id
#edit-emailaddress--2	email	To sign up to our email newsletter with the latest programs and initiatives	aria-label
#edit-zip--2	tel	Zip	for/id
#edit-phone	tel	Phone (optional)	for/id
input	number	(Other)	placeholder only
input	number	(Other)	placeholder only
title	search	(Type bird's name to start)	placeholder only
input	submit	(none)	none
#edit-submit	submit	(none)	none
#edit-submit--2	submit	(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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #161b26

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 ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Alt Text Quality

Action

5 of 15 images have issues

REVIEW

5 of 15 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 decorative image(s) correctly marked

3 image(s) with good alt text

15 images 3 good alt text 7 decorative 5 missing

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

Link & Button Quality

Action

2 issue(s) across 200 links and 53 buttons

REVIEW

2 issue(s) across 200 links and 53 buttons

16 link(s) open in new tab without warning

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

Got: https://policies.google.com/privacy; https://policies.google.com/terms; https://act.audubon.org/a/donate-temp?SelectedFrequency=4&ms=digital-fund-web…; https://audubonactionfund.org/; https://act.audubon.org/a/donate-temp?ms=digital-fund-web-website_nas_footer_…; https://legacy.audubon.org/; https://act.audubon.org/a/renew?ms=digital-fund-web-website_nas_footer_202401…; https://www.charitynavigator.org/ein/131624102; https://policies.google.com/privacy; https://policies.google.com/terms (+6 more)

2 button(s) with no accessible text

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

Got: button.js-toggle-filters (#148 on page); button.near-me-dropdown-close-btn (#557 on page)

184 link(s) with descriptive text

200 links

0 empty

0 generic text

16 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://policies.google.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
https://act.audubon.org/a/donate-temp?Se…	Donate	new tab	Add '(opens in new tab)' to text
https://audubonactionfund.org/	Audubon Action Fund	new tab	Add '(opens in new tab)' to text
https://act.audubon.org/a/donate-temp?ms…	Donate Now	new tab	Add '(opens in new tab)' to text
https://legacy.audubon.org/	Legacy Gifts	new tab	Add '(opens in new tab)' to text
https://act.audubon.org/a/renew?ms=digit…	Renew Membership	new tab	Add '(opens in new tab)' to text
https://www.charitynavigator.org/ein/131…	Charity Navigator	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/audubonsociety…	Audubon on Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/NationalAudubon…	Audubon on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/audubonsociety	Audubon on Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/nationa…	Audubon on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@audubonsociety	Audubon on Tiktok	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/audubonsociety…	Audubon on Pinterest	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

235 links and buttons have descriptive text

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

https://policies.google.com/privacy; https://policies.google.com/terms; https://act.audubon.org/a/donate-temp?SelectedFrequency=4&ms=digital-fund-web…; https://audubonactionfund.org/; https://act.audubon.org/a/donate-temp?ms=digital-fund-web-website_nas_footer_…; https://legacy.audubon.org/; https://act.audubon.org/a/renew?ms=digital-fund-web-website_nas_footer_202401…; https://www.charitynavigator.org/ein/131624102; https://policies.google.com/privacy; https://policies.google.com/terms (+6 more)

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.js-toggle-filters (#148 on page); button.near-me-dropdown-close-btn (#557 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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Sorry, We Couldn't Find That Page | Audubon ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

10 icon(s) detected

REVIEW

10 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA

span Get your first monthly gift matched for …

1.22:1

#000000

#161B26

needs 4.5:1 (normal text)

16px · top of page (header area)

span NaN

1.22:1

#000000

#161B26

needs 4.5:1 (normal text)

16px · top of page (header area)

span NaN

1.83:1

#000000

#2F3B46

needs 4.5:1 (normal text)

16px · above the fold

span NaN

1.86:1

#000000

#303C46

needs 4.5:1 (normal text)

16px · above the fold

span NaN

1.85:1

#000000

#2E3C45

needs 4.5:1 (normal text)

16px · above the fold

button Menu

1.80:1

#000000

#2E3A42

needs 4.5:1 (normal text)

16px · above the fold

a Audubon

1.75:1

#000000

#2E383E

needs 4.5:1 (normal text)

16px · above the fold

a Magazine

1.66:1

#000000

#2D343A

needs 4.5:1 (normal text)

16px · above the fold

a Español

1.63:1

#000000

#2E3237

needs 4.5:1 (normal text)

16px · above the fold

button Our Work

1.63:1

#000000

#2F3236

needs 4.5:1 (normal text)

16px · above the fold

button Protecting Bird Habitats

1.67:1

#000000

#343337

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Search Audubon	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Birds Need You Now	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h3 Your Location	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h3 Nearest Centers and …	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h3 Nearest Chapters	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h3 State Office	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h3 More Near You	15.46:1	3.0:1	#000000	#DDDDDD	Pass
title National Audubon Soc…	11.04:1	4.5:1	#000000	#FEAB00	Pass
a Skip to main content	11.04:1	4.5:1	#000000	#FEAB00	Pass
span Get your first month…	1.22:1	4.5:1	#000000	#161B26	Fail
span NaN	1.22:1	4.5:1	#000000	#161B26	Fail
span NaN	1.83:1	4.5:1	#000000	#2F3B46	Fail
span NaN	1.86:1	4.5:1	#000000	#303C46	Fail
span NaN	1.85:1	4.5:1	#000000	#2E3C45	Fail
button Menu	1.80:1	4.5:1	#000000	#2E3A42	Fail
a Audubon	1.75:1	4.5:1	#000000	#2E383E	Fail
a Magazine	1.66:1	4.5:1	#000000	#2D343A	Fail
a Español	1.63:1	4.5:1	#000000	#2E3237	Fail
button Our Work	1.63:1	4.5:1	#000000	#2F3236	Fail
button Protecting Bird Habi…	1.67:1	4.5:1	#000000	#343337	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

3 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Search Audubon
H3 Your Location skipped
H3 Nearest Centers and Sanctuaries
H3 Nearest Chapters
H3 State Office
H3 More Near You
H2 Birds Need You Now

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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: National Audubon Society

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name National Audubon Society ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name National Audubon Society Display Mode standalone Theme Color #161B26 Background Color #FFF9F0 Icons 8 icon(s)

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /themes/custom/nas_theme/css/nas_print.css?tduopy

Print Stylesheet ✓ Print Optimized

Print stylesheet /themes/custom/nas_theme/css/nas_print.css?tduopy ✓Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 28 passed

PASS

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
Privacy Policy `div.np-search-form-widget-form > form#nas-everyaction-subscription-form-36dd8e121dee0dd4fc4f25f22058480d1cea333b9fae7e4f2a537d542a2e58d1 > div.nas-recaptcha-policy-wrapper > a`
Terms of Service `div.np-search-form-widget-form > form#nas-everyaction-subscription-form-36dd8e121dee0dd4fc4f25f22058480d1cea333b9fae7e4f2a537d542a2e58d1 > div.nas-recaptcha-policy-wrapper > a`

These are opportunities to improve the legibility of your content.

Names and labels

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
div.hero-content-wrapper > div.hero-content > div#hero_form > iframe#ea-form-embed `div.hero-content-wrapper > div.hero-content > div#hero_form > iframe#ea-form-embed`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read the issue `div.magazine-card-links > div.magazine-card-wrapper > div.magazine-card-links-read-more > a.button`

○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.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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 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 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.

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.