Skip to content
https://cancer.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title The requested page was not found | American Cancer Society ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A
Landmark Structure
19 landmarks
PASS
19 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "navigation" SEARCH MAIN CONTENTINFO footer

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

A
Heading Hierarchy
27 headings, 1 skip(s)
PASS
27 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Info::
1 hidden heading(s) (aria-hidden)
  • H1 Every cancer. Every life.
  • H4 Featured skipped
  • H3 Cancer Information and Resources
  • H2 Services for You
  • H2 Overall Impact of the American Cancer Society
  • H3 Help us continue our work
  • H2 Risk, Prevention, and Screening
  • H2 Supporting Families and Caregivers
  • H2 Volunteer and Fundraise
  • H2 Volunteer and Fundraising Impact
  • H3 Participate in a Volunteer or Fundraising Activity
  • H2 Research That Saves Lives
  • H2 Survivor Journeys
  • H2 Sign Up for American Cancer Society Emails
  • H2 Cookie Preference Center
  • H2 Cookie Preference Center hidden
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Vendors List

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+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
7 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
49 images 42 good alt text 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 16 controls labeled
PASS
All 16 controls labeled
Info::
16 control(s) properly labeled
16 controls
16 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-desktoptextSearchfor/id
qtextSearcharia-label
#search-MobiletextSearcharia-label
qtextSearcharia-label
#txt_TabooForm_FirstNametextFirst Name *for/id
#txt_TabooForm_LastNametextLast Name *for/id
#txt_TabooForm_EmailAddresstextEmail *for/id
#g-recaptcha-responsetextarearecaptchaaria-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Every cancer. Every …19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Services for You19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Overall Impact of th…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Risk, Prevention, an…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Supporting Families …19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Volunteer and Fundra…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Volunteer and Fundra…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Research That Saves …19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Survivor Journeys19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Sign Up for American…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Cookie Preference Ce…19.79:13.0:1
#000000
#F6F8FF
Pass
h2 Cookie Preference Ce…19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Cancer Information a…19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Help us continue our…19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Participate in a Vol…19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Your Privacy19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Strictly Necessary C…19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Performance Cookies19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Functional Cookies19.79:13.0:1
#000000
#F6F8FF
Pass
h3 Targeting Cookies19.79:13.0:1
#000000
#F6F8FF
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.

A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 passed
PASS
94

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
Cancer Information div.aem-Grid > div.list > div.list-item-wrap > div.list-heading
ACS Fundraisers div.aem-Grid > div.list > div.list-item-wrap > div.list-heading
About ACS div.aem-Grid > div.list > div.list-item-wrap > div.list-heading
About ACS Programs & Services div.aem-Grid > div.list > div.list-item-wrap > div.list-heading
More ACS Sites div.aem-Grid > div.list > div.list-item-wrap > div.list-heading

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

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Featured div.aem-Grid > div.title > div#title-f671bd8bc6 > h4.cmp-title__text

These are opportunities to improve keyboard navigation in your application.

○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
●`[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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback