Skip to content
https://massgeneral.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://massgeneral.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://massgeneral.org/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #213245
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 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.

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::
6 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
17 headings, 2 skip(s)
REVIEW
17 headings, 2 skip(s)
Info::
Single H1 present
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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 The Mass General Difference
  • H2 Conditions & Treatments
  • H2 Patients & Visitors
  • H2 Research & Innovation
  • H1 Our Strength Is Yours
  • H3 U.S. News Honor Roll Hospital skipped
  • H3 Featured Stories
  • H4 Targeted Therapy Improves Long-Term Outcomes for Patients with Rare Mutations Driving Lung Cancer
  • H4 Long Dismissed in Adult Health, the Thymus May Be Critical for Longevity and Cancer Treatment
  • H4 Sean M. Healey & AMG Center for ALS Announces Design with Keros Therapeutics for Upcoming Healey ALS MyMatch Trial
  • H2 Latest from Mass General
  • H4 Gambling Addiction: How to Recognize a Problem and Get Help skipped
  • H4 What Causes Obesity?
  • H4 Driving Progress in Patient Transfers to Expand Access to Care
  • H4 Parkinson's vs. MS
  • H2 In the delivery of our care, through our research and within our communities, Mass General is committed to the well-being of our patients locally and globally.
  • H2 Stay connected with Mass General

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title error ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 19 passed
REVIEW
88

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CLOSE div.col-4 > div.global-header__mobile-nav > div.mobile-search > button.mobile-search__trigger

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
U.S. News Honor Roll Hospital div.hero-area > div.proof-point > div.proof-point__statement > h3
Gambling Addiction: How to Recognize a Problem and Get Help ul > li > div.listing-item > h4.listing-item__title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-12 > div.global-footer__address > a div.row > div.col-12 > div.global-footer__address > a

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
Targeted Therapy Improves Long-Term Outcomes for Patients with Rare Mutations D… li > div.listing-item > h4.listing-item__title > a
Long Dismissed in Adult Health, the Thymus May Be Critical for Longevity and Ca… li > div.listing-item > h4.listing-item__title > a
Sean M. Healey & AMG Center for ALS Announces Design with Keros Therapeutics fo… li > div.listing-item > h4.listing-item__title > a
Explore research at Mass General div.testimonial__text--container > div.testimonial__text > div.testimonial__cta > a.button
Gambling Addiction: How to Recognize a Problem and Get Help li > div.listing-item > h4.listing-item__title > a
What Causes Obesity? li > div.listing-item > h4.listing-item__title > a
Driving Progress in Patient Transfers to Expand Access to Care li > div.listing-item > h4.listing-item__title > a
Learn more div.row > div.col-12 > div.homepage-pillars__pillar > a.button
Learn more div.row > div.col-12 > div.homepage-pillars__pillar > a.button
Learn more div.row > div.col-12 > div.homepage-pillars__pillar > a.button
Learn More div.homepage-featured-pages > div.homepage-featured-pages__inner > div.homepage-featured-pages__page > a.button
FIND A LOCATION nav.global-footer__nav > ul > li.global-footer__link > a
CONTACT US nav.global-footer__nav > ul > li.global-footer__link > a
○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>`
●`[aria-*]` attributes have valid values
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●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.
●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.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
6 <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 "Utility" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
17 image(s) with good alt text
17 images 17 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#mainNavColSearchtextSearcharia-label
#mainNavSearchtextSearcharia-label
#mobileNavSearchtextSearcharia-label
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 Our Strength Is Your…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest from Mass Gen…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In the delivery of o…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stay connected with …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 U.S. News Honor Roll…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Featured Stories21.00:13.0:1
#000000
#FFFFFF
Pass
title Massachusetts Genera…21.00:14.5:1
#000000
#FFFFFF
Pass
a skip to Cookie Notic…21.00:14.5:1
#000000
#FFFFFF
Pass
a skip to Main Navigat…20.82:14.5:1
#000000
#FEFEFE
Pass
a skip to Main Content21.00:14.5:1
#000000
#FFFFFF
Pass
a skip to Footer21.00:14.5:1
#000000
#FFFFFF
Pass
a Find a Doctor21.00:14.5:1
#000000
#FFFFFF
Pass
a Find a Location21.00:14.5:1
#000000
#FFFFFF
Pass
a Appointments & Refer…21.00:14.5:1
#000000
#FFFFFF
Pass
a Patient Gateway21.00:14.5:1
#000000
#FFFFFF
Pass
a Give Now21.00:14.5:1
#000000
#FFFFFF
Pass
button Language21.00:14.5:1
#000000
#FFFFFF
Pass
a English21.00:14.5:1
#000000
#FFFFFF
Pass
a Español21.00:14.5:1
#000000
#FFFFFF
Pass
a 中文21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback