Skip to content
https://cancer.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode
Icons 2 icon(s)
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
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
8 headings
REVIEW
8 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Improving the lives of all people through cancer research
  • H2 For People Affected by Cancer
  • H2 For Researchers
  • H2 Featured News and Research
  • H2 NCI Welcomes Dr. Anthony Letai as NCI Director
  • H2 NCI FY27 Annual Plan & Professional Judgment Budget
  • H2 Get Answers
  • H2 Our Organization

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h2 Improving the lives of all people throug…
2.35:1
#000000
on
#6B3E2E
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
span News & Events
3.37:1
#000000
on
#516371
needs 4.5:1 (normal text)
16px · above the fold · 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)
ElementRatioRequiredFGBGResult
h2 Improving the lives …2.35:13.0:1
#000000
#6B3E2E
Fail
h2 For People Affected …6.82:13.0:1
#000000
#DF7647
Pass
h2 For Researchers18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Featured News and Re…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 NCI Welcomes Dr. Ant…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 NCI FY27 Annual Plan…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Get Answers18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Our Organization18.43:13.0:1
#000000
#F0F0F0
Pass
title Comprehensive Cancer…18.43:14.5:1
#000000
#F0F0F0
Pass
a Skip to main content19.43:14.5:1
#000000
#F6F6F6
Pass
div An official website …21.00:14.5:1
#000000
#FFFFFF
Pass
a Español21.00:14.5:1
#000000
#FFFFFF
Pass
button Menu21.00:14.5:1
#000000
#FFFFFF
Pass
label Search21.00:14.5:1
#000000
#FFFFFF
Pass
span Search18.60:14.5:1
#000000
#F2F1EF
Pass
span About Cancer15.05:14.5:1
#000000
#DADADD
Pass
span Cancer Types19.77:14.5:1
#000000
#F8F8F8
Pass
span Research14.23:14.5:1
#000000
#CED5E1
Pass
span Grants & Training9.70:14.5:1
#000000
#A1B3BD
Pass
span News & Events3.37:14.5:1
#000000
#516371
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
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
14 images 12 good alt text 1 decorative
IssueCount
too long1 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#nci-header-search__fieldsearchSearchfor/id
#emailemailEnter your email addressfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Linkedin Custom Styling Navigation Homepage Link Search Form
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 27 passed
PASS
97

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
U.S. Department of Health and Human Services div.usa-footer__address > div.usa-footer__contact-info > address > a
National Institutes of Health div.usa-footer__address > div.usa-footer__contact-info > address > a
National Cancer Institute div.usa-footer__address > div.usa-footer__contact-info > address > a
USA.gov div.usa-footer__address > div.usa-footer__contact-info > address > a

These items highlight common accessibility best practices.

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
Find a Cancer Type div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Treatment div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Side Effects div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Causes & Prevention div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Diagnosis & Staging div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Find a Clinical Trial div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Funding Opportunities div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Resources for Researchers div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Apply for a Grant div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
Find a Research Contact div.nci-guide-card__body > ul.nci-card__button-group > li > a.usa-button
New Blood Test May Detect Early Pancreatic Cancer Four-marker blood test could… div.grid-container > ul.nci-card-group > li.nci-card > a
Why Are Cancer Diagnoses Rising in People Under Age 50? Researchers are lookin… div.grid-container > ul.nci-card-group > li.nci-card > a
Predicting Breast Cancer Aggressiveness Substantial changes in breast tissue m… div.grid-container > ul.nci-card-group > li.nci-card > a
Get Started div.tablet-lg:grid-container-widescreen > div.nci-promo-block > div.nci-promo-block__content > a.usa-button
Senior Leaders Information about NCI senior leadership. div.grid-container > ul.nci-card-group > li.nci-card > a
NCI Divisions, Offices, and Centers NCI has 30 divisions, offices, and centers… div.grid-container > ul.nci-card-group > li.nci-card > a
Advisory Boards and Review Groups NCI relies on advisory committees to provide… div.grid-container > ul.nci-card-group > li.nci-card > a
The Power of Improved Data Sharing - Childhood Cancer Data Initiative figure.cgdp-video__figure > div.cgdp-video__media > div#ytplayer-jC8CUIID2HA > div.video-preview--container
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
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
`[aria-hidden="true"]` elements do not contain focusable descendents
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 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
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
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 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.
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.

Send Feedback