Skip to content
https://mountsinai.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Landmark Structure
Action
19 landmarks
FIX
19 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
7 <nav> landmark(s) found
Warning::
7 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
7 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 404 Page Not Found | Mount Sinai - New York ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 2 pass AA only
p Mount Sinai has reached an agreement wit…
4.35:1
#000000
on
#D80B8C
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Call us at 1-800-MD-…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Call us at21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Choose a Location21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Hospitals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Hospitals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mount Sinai at a Gla…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Facebook21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Facebook21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Facebook21.00:13.0:1
#000000
#FFFFFF
Pass
h2 YouTube21.00:13.0:1
#000000
#FFFFFF
Pass
h2 YouTube21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Instagram21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Over 47,000 Employee…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 400+ Community Locat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 47 Institutes21.00:13.0:1
#000000
#FFFFFF
Pass
title Mount Sinai Health S…15.91:14.5:1
#000000
#E0E0E0
Pass
a Open Accessibility M…6.76:14.5:1
#000000
#DC69B9
Pass
p Mount Sinai has reac…4.35:14.5:1
#000000
#D80B8C
Fail
span Learn more4.83:14.5:1
#FFFFFF
#D80B8C
Pass
a Skip to main content16.21:14.5:1
#000000
#E2E2E2
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
Heading Hierarchy
27 headings
PASS
27 headings
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Get More Control Over Your Health Care with MyMountSinai
  • H1 Find a Doctor, and Schedule Online duplicate H1
  • H1 Newsweek Ranks The Mount Sinai Hospital No. 1 in New York for the 4th Year in a Row duplicate H1
  • H1 Get More Control Over Your Health Care with MyMountSinai duplicate H1
  • H1 Find a Doctor, and Schedule Online duplicate H1
  • H1 Newsweek Ranks The Mount Sinai Hospital No. 1 in New York for the 4th Year in a Row duplicate H1
  • H1 Get More Control Over Your Health Care with MyMountSinai duplicate H1
  • H2 Call us at 1-800-MD-SINAI
  • H2 Call us at 1-800-MD-SINAI
  • H2 Choose a Location
  • H2 Our Services
  • H2 Our Hospitals
  • H2 Our Services
  • H2 Our Services
  • H2 Our Hospitals
  • H2 Our Services
  • H2 Our Services
  • H2 Mount Sinai at a Glance
  • H3 Over 47,000 Employees
  • H3 400+ Community Locations
  • H3 47 Institutes
  • H2 Facebook
  • H2 Facebook
  • H2 Facebook
  • H2 YouTube
  • H2 YouTube
  • H2 Instagram

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

A+
Alt Text Quality
All 35 images OK
PASS
All 35 images OK
Info::
1 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
35 images 34 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 14 controls labeled
PASS
All 14 controls labeled
Info::
14 control(s) properly labeled
14 controls
14 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
querytextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
querytextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
selectselectWidget Language Translatearia-label
search-byradionone
search-byradionone
footer-mapradionone
footer-mapradionone
selectselecthospitalaria-label
selectselecturgent-carearia-label
#goog-gt-votingInputSrcLangtextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
#goog-gt-votingInputTrgLangtextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
#goog-gt-votingInputSrcTexttextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
#goog-gt-votingInputTrgTexttextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
#goog-gt-votingInputVotetextTo make this website accessible to screen reader, press combination of alt and 1 keys. To stop getting this message, press the combination of alt and 2 keys.aria-label
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 28 passed
PASS
90

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.

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
Get Care Now div.hpcards__mobile__container--row > div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--title
Getting care is easy and convenient. Access virtual care or in-person support. div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--desc > p
Book Online div.hpcards__mobile__container--row > div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--title
Book an Appointment now with a Mount Sinai doctor. div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--desc > p
MyMountSinai® App div.hpcards__mobile__container--row > div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--title
Sign in with your MyChart account and take care of your healthcare needs. div.hpcards__mobile__container--content > a.hpcards__mobile__container--a > span.hpcards__mobile__container--content--desc > p
1-800-MD-SINAI div.hpcards__mobile__container--outter > div > h2.section_title > a
Our Services div.listing > h2 > a > span
Cancer div > ul > li > a
Ear, Nose, and Throat div > ul > li > a
Geriatrics div > ul > li > a
Heart - Cardiology and Cardiovascular Surgery div > ul > li > a
Neurology div > ul > li > a
Neurosurgery div > ul.ul-columns > li > a
Orthopedics div > ul.ul-columns > li > a
Spine div > ul.ul-columns > li > a
Surgery div > ul.ul-columns > li > a
Urology div > ul.ul-columns > li > a
View All of Our Services div.listing-img > div.listing-block > div.listing > a.view-more
View All Press Releases div.infobox-panel > div.detail > div > a
Agree to all div#ppms_cm_popup_responsive_wrapper_id > div#ppms-59442d7f-1516-40e2-bbd7-12ad4b9a353e > div#ppms-3cde0edc-dff1-4c19-939f-15c95f4382d6 > button#ppms_cm_agree-to-all
Decline all div#ppms_cm_popup_responsive_wrapper_id > div#ppms-59442d7f-1516-40e2-bbd7-12ad4b9a353e > div#ppms-3cde0edc-dff1-4c19-939f-15c95f4382d6 > button#ppms_cm_reject-all
Adjust cookie settings div#ppms_cm_popup_main_id > div#ppms_cm_popup_responsive_wrapper_id > div#ppms-b7755843-4632-4d35-aa07-c3748012a683 > button#ppms_cm_content_expander_show_btn
Privacy policy div#ppms_cm_popup_main_id > div#ppms_cm_popup_responsive_wrapper_id > div#ppms-b7755843-4632-4d35-aa07-c3748012a683 > a#popup-link

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.full-width > div#fad_container-iframe-outer > div.fad__container--iframe-inner > iframe#myIframe div.full-width > div#fad_container-iframe-outer > div.fad__container--iframe-inner > iframe#myIframe

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○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]`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
●Select elements have associated label elements.
●`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
●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
●No element has a `[tabindex]` value greater than 0
●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
●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 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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Elements with visible text labels have matching accessible names.
○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