Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-xkx3d1

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://livestrong.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://livestrong.com/manifest.json

Manifest contains invalid JSON.

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: #ece3c9

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.

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 ✗

Link & Button Quality

1 issue(s) across 77 links and 7 buttons

REVIEW

1 issue(s) across 77 links and 7 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://livestrong.org/resources/blog/breast-cancer-at-26-lashaes-journey/ ("Read more")

5 link(s) open in new tab without warning

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

Got: https://impact.livestrong.org/event/first-responder-ride-for-resilience?utm_m…; https://livestrong.org/how-we-help/cancerfit/; https://livestrong.org/resources/; https://policies.google.com/privacy; https://policies.google.com/terms

71 link(s) with descriptive text

77 links

0 empty

1 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://impact.livestrong.org/event/firs…	Join the Ride for Resilience	new tab	Add '(opens in new tab)' to text
https://livestrong.org/how-we-help/cance…	CancerFit	new tab	Add '(opens in new tab)' to text
https://livestrong.org/resources/	Resources	new tab	Add '(opens in new tab)' to text
https://livestrong.org/resources/blog/br…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Breast Cancer At 26 Lashaes Journey
https://policies.google.com/privacy	Google Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Google Terms of Service	new tab	Add '(opens in new tab)' to text

78 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://livestrong.org/resources/blog/breast-cancer-at-26-lashaes-journey/ ("Read more")

Why this matters

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

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

https://impact.livestrong.org/event/first-responder-ride-for-resilience?utm_m…; https://livestrong.org/how-we-help/cancerfit/; https://livestrong.org/resources/; https://policies.google.com/privacy; https://policies.google.com/terms

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

h3 343 Miles, 1 Promise: Never Forget.

1.00:1

#000000

needs 3.0:1 (large text)

19px · top of page (header area)

title Livestrong Cancer Support - Homepage

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Close search

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p Honor the 25th anniversary of 9/11 by ri…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Join the Ride for Resilience

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Livestrong

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span How We Help

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cancer survivors nee…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PEOPLE FIRST,	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ALWAYS.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How We Help	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your Voices,	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your Stories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How you can get invo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join the Family	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 343 Miles, 1 Promise…	1.00:1	3.0:1	#000000	#000000	Fail
h3 LaShae's Story	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Join Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Donate	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Connect	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Livestrong Cancer Su…	1.00:1	4.5:1	#000000	#000000	Fail
span Close search	1.00:1	4.5:1	#000000	#000000	Fail
p Honor the 25th anniv…	1.00:1	4.5:1	#000000	#000000	Fail
span Join the Ride for Re…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
span Livestrong	1.00:1	4.5:1	#000000	#000000	Fail
span How We Help	1.00:1	4.5:1	#000000	#000000	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.

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 27 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WHAT CAN WE HELP YOU WITH TODAY? Close search Search in https://livestrong.org/… `body.home > header.livestrong-header > div.livestrong-max-width--large > div.livestrong-header__search`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
HOW WE HELP How We Help Livestrong Fertility Livestrong at the YMCA CancerFit f… `header.livestrong-header > div.livestrong-max-width--large > div.livestrong-header__wrapper > div.livestrong-header__menu`
div.tab-group > div.tab-group__nav-container > sl-icon-button.tab-group__scroll-button `div.tab-group > div.tab-group__nav-container > sl-icon-button.tab-group__scroll-button`

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close search `div#livestrong-push-down__modal_18079 > div.livestrong-padding > div.livestrong-max-width--large > button.livestrong-close-button`

These are opportunities to improve keyboard navigation in your application.

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
Ask `div.floating-bar`

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●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

●`[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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●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

○`[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 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 buttons have discernible text.

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

○Identical links have the same purpose.

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

Landmark Structure

3 landmarks

PASS

3 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

12 headings

PASS

12 headings

Single H1 present

H3 343 Miles, 1 Promise: Never Forget.
H1 We ensure everyone affected by cancer has the resources they need to thrive
H2 Cancer survivors need your support.
H2 PEOPLE FIRST, ALWAYS.
H2 How We Help
H2 Your Voices, Your Stories
H3 LaShae's Story
H2 How you can get involved
H3 Join Events
H3 Donate
H3 Connect
H2 Join the Family

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

1 decorative image(s) correctly marked

22 image(s) with good alt text

23 images 22 good alt text 1 decorative

All images have appropriate alt text.

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#input_2_1	text	First Name	for/id
#input_2_3	text	Last Name	for/id
#input_2_6	email	Email Address	for/id
#choice_2_7_1	checkbox	I agree to receive marketing information from Livestrong in the future.	for/id
#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

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