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 3 REVIEW 5 FIX

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 ✗

Alt Text Quality

Action

3 of 26 images have issues

REVIEW

3 of 26 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with alt text over 125 characters

3 decorative image(s) correctly marked

19 image(s) with good alt text

26 images 19 good alt text 3 decorative 3 missing

Issue	Count
missing	3 image(s)
too long	1 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

Form Accessibility

2 of 6 controls have issues

REVIEW

2 of 6 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

4 control(s) properly labeled

6 controls

4 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#headerSearchInput	search	Enter your search	for/id
#form-SimpleSignUp-96c3_cons_email_Email	email	Email	for/id
#form-SimpleSignUp-96c3_EmailOptIn_checkbox_Value	checkbox	Yes, I would like to receive email from the Alzheimer's Association. *	for/id
#form-SimpleSignUp-96c3_cons_zip_code_Value	text	Zip Code	for/id
input	submit	(none)	none
#g-recaptcha-response-100000	textarea	(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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Knowledge is power.

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Honor a Loved One with a Tribute

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Be a Part of the Fight to End Alzheimer'…

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Be a Part of the Fight to End Alzheimer'…

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

24px · bottom of viewport

h3 We're Here to Help

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get Involved in Your Community

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Understand Treatment Options

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Take the Brain Tour

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get Educated

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We Provide Care and Support

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We Accelerate Global Research

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We Advocate for Change

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Participate in an Event Near You

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Volunteer with the Association

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Wear Purple to Show Your Support

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Advocate for Public Policy Change

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep Up With Alzheimer's News and Events

1.04:1

#000000

#0F0214

needs 3.0:1 (large text)

19px · bottom of viewport

title Alzheimer's Association | Alzheimer's Di…

1.04:1

#000000

#0F0214

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to Content

1.19:1

#000000

#251508

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Menu

1.45:1

#000000

#332814

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

2 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)

Element	Ratio	Required	FG	BG	Result
h1 Knowledge is power.	1.04:1	3.0:1	#000000	#0F0214	Fail
h2 Honor a Loved One wi…	1.04:1	3.0:1	#000000	#0F0214	Fail
h2 Be a Part of the Fig…	1.04:1	3.0:1	#000000	#0F0214	Fail
h2 Be a Part of the Fig…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 We're Here to Help	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Get Involved in Your…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Understand Treatment…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Take the Brain Tour	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Get Educated	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 We Provide Care and …	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 We Accelerate Global…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 We Advocate for Chan…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Participate in an Ev…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Volunteer with the A…	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Wear Purple to Show …	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Advocate for Public …	1.04:1	3.0:1	#000000	#0F0214	Fail
h3 Keep Up With Alzheim…	1.04:1	3.0:1	#000000	#0F0214	Fail
title Alzheimer's Associat…	1.04:1	4.5:1	#000000	#0F0214	Fail
a Skip to Content	1.19:1	4.5:1	#000000	#251508	Fail
span Menu	1.45:1	4.5:1	#000000	#332814	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.

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 Knowledge is power. Protecting brain health is action.
H2 Play Pickleball to Help End Alzheimer's
H2 Find a Volunteer Opportunity
H2 Be a Part of the Fight to End Alzheimer's
H3 We're Here to Help
H3 Get Involved in Your Community
H3 Understand Treatment Options
H3 Take the Brain Tour
H3 Get Educated
H3 We Provide Care and Support
H3 We Accelerate Global Research
H3 We Advocate for Change
H3 Participate in an Event Near You
H3 Volunteer with the Association
H3 Wear Purple to Show Your Support
H3 Advocate for Public Policy Change
H2 Honor a Loved One with a Tribute
H2 Be a Part of the Fight to End Alzheimer's
H2 Be a Part of the Fight to End Alzheimer's
H3 Keep Up With Alzheimer's News and Events

Link & Button Quality

114 links, 20 buttons — all OK

PASS

114 links, 20 buttons — all OK

14 link(s) open in new tab without warning

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

Got: https://shop.alz.org; https://events.alz.org/pickleballshp26; https://events.alz.org/pickleballshp26; https://shop.alz.org/; https://events.alz.org/event/alz-tributes/home; https://pro.alz.org/; /Security-and-Privacy-Policy; /jobs; https://www.facebook.com/actionalz; https://www.instagram.com/alzassociation/ (+4 more)

100 link(s) with descriptive text

114 links

0 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://shop.alz.org	Shop for the Cause	new tab	Add '(opens in new tab)' to text
https://events.alz.org/pickleballshp26	Play Pickleball to Help End Al…	new tab	Add '(opens in new tab)' to text
https://events.alz.org/pickleballshp26	Get Started	new tab	Add '(opens in new tab)' to text
https://shop.alz.org/	Shop for the Cause	new tab	Add '(opens in new tab)' to text
https://events.alz.org/event/alz-tribute…	Create a Tribute Page	new tab	Add '(opens in new tab)' to text
https://pro.alz.org/	ALZPro™: Professional Resour…	new tab	Add '(opens in new tab)' to text
/Security-and-Privacy-Policy	Privacy Policy	new tab	Add '(opens in new tab)' to text
/jobs	Jobs	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/actionalz	Facebook page	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/alzassociation…	View our instagram page	new tab	Add '(opens in new tab)' to text
https://x.com/alzassociation	Alheimer's Association's offic…	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/alzassociation.…	Bluesky	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/actionalz	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/alzheim…	LinkedIn page	new tab	Add '(opens in new tab)' to text

120 links and buttons have descriptive text

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

https://shop.alz.org; https://events.alz.org/pickleballshp26; https://events.alz.org/pickleballshp26; https://shop.alz.org/; https://events.alz.org/event/alz-tributes/home; https://pro.alz.org/; /Security-and-Privacy-Policy; /jobs; https://www.facebook.com/actionalz; https://www.instagram.com/alzassociation/ (+4 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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title We're Sorry ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 27 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
Donate Now `div.wysiwyg > div.visionRow > p > a.btn`
Learn About Our Efforts and Impact `section.feature-banner > div.section__inner > div.feature-banner__cta > a.btn`
See Our Use of Funds and Finances `section.feature-banner > div.section__inner > div.feature-banner__cta > a.btn`
Search Events `div.card > div.card-footer > div.card-tags > a.btn`
Make a Difference `div.card > div.card-footer > div.card-tags > a.btn`
Shop for the Cause `div.card > div.card-footer > div.card-tags > a.btn`
Become an Advocate `div.card > div.card-footer > div.card-tags > a.btn`
Meet the Alzheimer's Association `section.feature-banner > div.section__inner > div.feature-banner__cta > a.btn`

These are opportunities to improve the legibility of your content.

Names and labels

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
body > img `body > img`

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
Volunteer with Us `div.grid__item > app-feature.feature > div.feature__content > a.feature__cta`
DONATE Make a Donation `div.page > app-footer.footer > div.footer__tools > a.footer__tool`
24/7 HELPLINE 800.272.3900 `div.page > app-footer.footer > div.footer__tools > a.footer__tool`
IN MY AREA Local Resources `div.page > app-footer.footer > div.footer__tools > a.footer__tool`

○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

●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

●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

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

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

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