Skip to content
https://mdanderson.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Alt Text Quality
Action
11 of 19 images have issues
FIX
11 of 19 images have issues
Critical::
11 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
11 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
7 image(s) with good alt text
19 images 7 good alt text 11 missing
IssueCount
missing11 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Form Accessibility
Action
7 of 11 controls have issues
FIX
7 of 11 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="tfa_23" id="tfa_23">; <input type="text" name="tfa_38" id="tfa_38">; <input type="email" name="tfa_20" id="tfa_20">
Info::
4 control(s) properly labeled
11 controls
4 labeled
3 placeholder only
4 unlabeled
ControlTypeLabelMethod
#site-searchtextSearchfor/id
#nav-search-form-svp-inputtextSearch UT MD Andersonfor/id
#search-cancer-types-fieldinputSearch by type of cancer or conditionfor/id
#search-clinical-trials-fieldtextSearch Clinical Trialsfor/id
#tfa_23text(First Name *)placeholder only
#tfa_38text(Last Name *)placeholder only
#tfa_20email(Email Address *)placeholder only
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">

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.

<input type="text" name="tfa_23" id="tfa_23">; <input type="text" name="tfa_38" id="tfa_38">; <input type="email" name="tfa_20" id="tfa_20">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
C
Heading Hierarchy
Action
28 headings, 2 skip(s)
REVIEW
28 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The healing power of art
  • H3 Donate blood. Save a life. skipped
  • H3 Search Cancer Types
  • H3 Search Clinical Trials
  • H3 Plan Your Care
  • H4 Prepare for your first visit
  • H4 Check Insurance Coverage
  • H4 Plan Travel and Lodging
  • H1 Why Choose UT MD Anderson duplicate H1
  • H3 Art provides healing for patients and caregivers skipped
  • H2 UT MD Anderson Highlights
  • H3 Top cancer hospital
  • H3 Annual Report
  • H3 Rare leukemia survivor
  • H3 Personalized treatment
  • H3 Recognizing dehydration
  • H3 Cold sensitivity tips
  • H3 Only Possible Here
  • H3 Y-90 for liver cancer
  • H3 myCancerConnection
  • H3 One-on-One Counseling
  • H3 Find Our Locations
  • H3 Read Our Blog
  • H3 Ask a Question
  • H2 Help #EndCancer
  • H3 Give Now
  • H3 Donate Blood
  • H3 Shop UT MD Anderson

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error Page - 404 | UT MD Anderson ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Navigation UX
Action
3 navigation pattern(s)
REVIEW
3 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
5 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The healing power of…4.32:13.0:1
#000000
#DA291C
Pass
h1 Why Choose4.32:13.0:1
#000000
#DA291C
Pass
h2 UT MD Anderson Hig…4.32:13.0:1
#000000
#DA291C
Pass
h2 Help #EndCancer4.32:13.0:1
#000000
#DA291C
Pass
h3 Donate blood. Save a…4.32:13.0:1
#000000
#DA291C
Pass
h3 Search Cancer Types4.32:13.0:1
#000000
#DA291C
Pass
h3 Search Clinical Tria…4.32:13.0:1
#000000
#DA291C
Pass
h3 Plan Your Care4.32:13.0:1
#000000
#DA291C
Pass
h3 Art provides healing…4.32:13.0:1
#000000
#DA291C
Pass
h3 and caregivers4.32:13.0:1
#000000
#DA291C
Pass
h3 Top cancer hospital4.32:13.0:1
#000000
#DA291C
Pass
h3 Annual Report4.32:13.0:1
#000000
#DA291C
Pass
h3 Rare leukemia surviv…4.32:13.0:1
#000000
#DA291C
Pass
h3 Personalized treatme…4.32:13.0:1
#000000
#DA291C
Pass
h3 Recognizing dehydrat…4.32:13.0:1
#000000
#DA291C
Pass
h3 Cold sensitivity tip…4.32:13.0:1
#000000
#DA291C
Pass
h3 Only Possible Here4.32:13.0:1
#000000
#DA291C
Pass
h3 Y-90 for liver cance…4.32:13.0:1
#000000
#DA291C
Pass
h3 myCancerConnection4.32:13.0:1
#000000
#DA291C
Pass
h3 One-on-One Counselin…4.32:13.0:1
#000000
#DA291C
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 6 failing, 26 passed
REVIEW
85

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.module > div.search-block > div.search-wrapper > ul.search-results div.module > div.search-block > div.search-wrapper > ul.search-results
div.module > div.search-block > div.search-wrapper > ul.search-results div.module > div.search-block > div.search-wrapper > ul.search-results

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.

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
div.search-block > div.search-wrapper > form#search-cancer-types > input#search-cancer-types-field div.search-block > div.search-wrapper > form#search-cancer-types > input#search-cancer-types-field
div.search-block > div.search-wrapper > form#search-clinical-trials > input#search-clinical-trials-field div.search-block > div.search-wrapper > form#search-clinical-trials > input#search-clinical-trials-field
Learn more about UT MD Anderson div.rte-container > p > span.cta > a
UT MD Anderson p > span.cta > a > span.nowrap
Art provides healing for patients and caregivers div.media-inner > div.media-body > div.media-body-text > h3

These are opportunities to improve the legibility of your content.

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
Art provides healing for patients and caregivers div.media-inner > div.media-body > div.media-body-text > h3

These are opportunities to improve keyboard navigation in your application.

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
a.carousel-item-link > div.carousel-image > picture > img a.carousel-item-link > div.carousel-image > picture > img
a.carousel-item-link > div.carousel-image > picture > img a.carousel-item-link > div.carousel-image > picture > img
a#patients_family_carouselitem_annual_report > div.carousel-image > picture > img a#patients_family_carouselitem_annual_report > div.carousel-image > picture > img
a#patients_family_carouselitem_rare_leukemia_s > div.carousel-image > picture > img a#patients_family_carouselitem_rare_leukemia_s > div.carousel-image > picture > img
a#patients_family_carouselitem_personalized_tr > div.carousel-image > picture > img a#patients_family_carouselitem_personalized_tr > div.carousel-image > picture > img
a#patients_family_carouselitem_recognizing_deh > div.carousel-image > picture > img a#patients_family_carouselitem_recognizing_deh > div.carousel-image > picture > img
a#patients_family_carouselitem_cold_sensitivit > div.carousel-image > picture > img a#patients_family_carouselitem_cold_sensitivit > div.carousel-image > picture > img
a#patients_family_carouselitem_only_possible_h > div.carousel-image > picture > img a#patients_family_carouselitem_only_possible_h > div.carousel-image > picture > img
a#patients_family_carouselitem_y_90_for_liver_ > div.carousel-image > picture > img a#patients_family_carouselitem_y_90_for_liver_ > div.carousel-image > picture > img
a.carousel-item-link > div.carousel-image > picture > img a.carousel-item-link > div.carousel-image > picture > 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.

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
1 div.carousel-group > ul.slick-dots > li.slick-active > button
2 div.carousel-group > ul.slick-dots > li > button
3 div.carousel-group > ul.slick-dots > li > button
4 div.carousel-group > ul.slick-dots > li > button
5 div.carousel-group > ul.slick-dots > li > button
6 div.carousel-group > ul.slick-dots > li > button
7 div.carousel-group > ul.slick-dots > li > button
8 div.carousel-group > ul.slick-dots > li > button

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
MENU header.mda-nav > div.mda-nav-top > div.mda-nav-mobile-menu > button.mda-nav-mobile-menu-button
Bringing comfort and courage to patients through art. div.carousel-body-inner > div.carousel-body-content > div.left-aligned-cta > a.cta-block
Top cancer hospital div.slick-list > div.slick-track > div.carousel-item > a#patients_family_carouselitem_top_cancer_hosp
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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.
○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.
A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN ASIDE CONTENTINFO footer
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback