Cleveland Clinicmy.clevelandclinic.org
Accessibility Score
Issues Found
Issues Found
CriticalCertain ARIA roles must contain particular children1 element
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Failing Elements
<div class="content-block-faq-panel js-content-block-faq-panel" role="tablist">
Fix any of the following:
- Element has children which are not allowed: hr[tabindex]
CriticalImages must have alternative text1 element
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Failing Elements
<img src="/Assets/imgs/icon-arrow-right.svg">
Fix any of the following:
- Element does not have an alt attribute
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element's default semantics were not overridden with role="none" or role="presentation"
SeriousLinks must be distinguishable without relying on color1 element
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Failing Elements
<a href="tel:800.223.2273">800.223.2273</a>
Fix any of the following:
- The link has insufficient color contrast of 2.55:1 with the surrounding text. (Minimum contrast is 3:1, link text: #0078bf, surrounding text: #363636)
- The link has no styling (such as underline) to distinguish it from the surrounding text
ModerateHeading levels should only increase by one2 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<h3 class="story-panel__title">Our Providers</h3>
Fix any of the following:
- Heading order invalid
<h5 class="footer__title lede">Actions</h5>
Fix any of the following:
- Heading order invalid
ModerateDocument should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Failing Elements
<html lang="en" dir="ltr">
Fix all of the following:
- Document does not have a main landmark
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<nav class="nav--utility js-nav--utility">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateAll page content should be contained by landmarks22 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<section class="hero theme-blue-pattern hero--hasDesktopImage ">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="story-panel__carousel js-story-panel__carousel container story-panel__no-carousel">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="care-widget__title js-care-widget__title">Health Library</div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="care-widget__content">
Fix any of the following:
- Some page content is not contained by landmarks
<section class="cta-panel js-cta-panel" id="aenterprise_home-page">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="container">
<h2 class="container--md">Why Choose Cleveland Clinic?</h2>
</div>Fix any of the following:
- Some page content is not contained by landmarks
<div class="spotlight-panel__container js-spotlight-panel__container container">
Fix any of the following:
- Some page content is not contained by landmarks
<h2 class="story-panel__heading container container--md">Cleveland Clinic Care Near You</h2>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="story-panel__carousel js-story-panel__carousel container story-panel__has-slider" style="height: 269.172px;">
Fix any of the following:
- Some page content is not contained by landmarks
<a class="story-panel__nav-button story-panel__nav-button--next js-story-panel__nav-button--next" style="top: 182.545px;"><img src="/Assets/imgs/icon-arrow-right.svg"></a>
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 22 failing elements.
Passed Audits
[role="img"] elements must have alternative text7 elements
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" dir="ltr">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en" dir="ltr">
<li> elements must be contained in a <ul> or <ol>34 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li>
<li>
<a class="nav--utility__link nav--utility__link--phone" href="tel:800.223.2273">
800.223.2273
</a>
</li><li>
<a class="nav--utility__link " title="MyChart" href="/online-services/mychart" disablewebedit="True">MyChart</a>
</li><li>
<a class="nav--utility__link " title="Need help?" href="/help" disablewebedit="True">Need Help?</a>
</li><li>
<a class="nav--utility__link " href="/professionals" disablewebedit="True">Medical Professionals</a>
</li><li>
<a class="nav--utility__link " href="/giving" disablewebedit="True">Giving</a>
</li><li>
<a class="nav--utility__link " href="https://jobs.clevelandclinic.org/" disablewebedit="True" target="_blank">Careers</a>
</li><li>
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
</li><li>
<a class="nav--secondary__link " href="/providers" disablewebedit="True">Find a Provider</a>
</li><li>
<a class="nav--secondary__link " href="/locations" disablewebedit="True">Locations & Directions</a>
</li>Showing first 10 of 34 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements6 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul>
<ul>
<ul class="story-panel__cards-container js-story-panel__cards-container story-panel__full-width">
<ul class="care-widget__ul">
<ul class="story-panel__cards-container js-story-panel__cards-container" style="margin-left: 0%; width: 200%;">
<ul class="contact-box">
All page content should be contained by landmarks348 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<section class="notification-banner js-notification-banner">
<header class="notification-banner__header">
<span class="notification-banner__icon">
<a href="#notification-banner__lightbox-popup" class="notification-banner__link--expand js-notification-banner__link--expand js-lightbox-popup">
<img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
</a><img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
<span class="notification-banner__title">
<a href="#notification-banner__lightbox-popup" class="js-lightbox-popup">
Important Updates
</a>
</span><a href="#notification-banner__lightbox-popup" class="js-lightbox-popup">
Important Updates
</a><div class="notification-banner__action">
<button class="notification-banner__action-icon js-notification-banner__action-icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
</button>
</div><button class="notification-banner__action-icon js-notification-banner__action-icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
</button><img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
Showing first 10 of 348 audited elements.
Alternative text of images should not be repeated as text23 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
<img src="/Assets/imgs/icon-alert--blue.svg" alt="exclamation icon">
<img src="/-/scassets/images/org/logo/logo-ccf.svg?h=48&la=en&w=300&hash=F5231F16526C9ED33D180771275ED4B7E42C2018" alt="Cleveland Clinic logo" width="300" height="48" disablewebedit="True">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/find-a-doctor-card.jpg" width="634" height="356" alt="Find a Doctor">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/locations-card.jpg" width="634" height="356" alt="Locations">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/appointments-card.jpg" width="634" height="356" alt="Appointments">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-appointments-dark-blue.svg" alt="Getting an appointment at Cleveland Clinic is easy. Schedule using any of these convenient options.">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-stay-healthy-light-blue.svg" alt="Find health and wellness information to help you and your family live a bit healthier each day.">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-need-help-green.svg" alt="Have a question? We want to make it easy to find what you're looking for. Get answers online fast.">
Showing first 10 of 23 audited elements.
ARIA attributes must be used as specified for the element's role9 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
ARIA attributes must conform to valid names9 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
ARIA attributes must conform to valid values9 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
ARIA role should be appropriate for the element17 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<div class="content-block-faq-panel js-content-block-faq-panel" role="tablist">
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
Showing first 10 of 17 audited elements.
ARIA roles used must conform to valid values17 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div class="content-block-faq-panel js-content-block-faq-panel" role="tablist">
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
Showing first 10 of 17 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="health">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header id="site-header" class="header js-site-header site-header__open-banner site-header__has-banner">
Buttons must have discernible text1 element
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="notification-banner__action-icon js-notification-banner__action-icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
</button>Certain ARIA roles must be contained by particular parents8 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="footer js-footer">
Deprecated ARIA roles must not be used17 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div class="content-block-faq-panel js-content-block-faq-panel" role="tablist">
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
Showing first 10 of 17 audited elements.
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="notification-banner__header">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer class="footer js-footer">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en" dir="ltr">
Elements marked as presentational should be consistently ignored1 element
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<iframe src="https://oc-cdn-ocpro..." name="Microsoft_Omnichanne..." id="Microsoft_Omnichanne..." title="Chat Widget" allow="microphone *; camera..." allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscree...="true" height="0px" width="0px" role="presentation" ...>
Elements must meet minimum color contrast ratio thresholds122 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<a href="#notification-banner__lightbox-popup" class="js-lightbox-popup">
Important Updates
</a><a class="nav--utility__link nav--utility__link--phone" href="tel:800.223.2273">
800.223.2273
</a><a class="nav--utility__link " title="MyChart" href="/online-services/mychart" disablewebedit="True">MyChart</a>
<a class="nav--utility__link " title="Need help?" href="/help" disablewebedit="True">Need Help?</a>
<a class="nav--utility__link " href="/professionals" disablewebedit="True">Medical Professionals</a>
<a class="nav--utility__link " href="/giving" disablewebedit="True">Giving</a>
<a class="nav--utility__link " href="https://jobs.clevelandclinic.org/" disablewebedit="True" target="_blank">Careers</a>
<a class="nav--secondary__link " href="/providers" disablewebedit="True">Find a Provider</a>
<a class="nav--secondary__link " href="/locations" disablewebedit="True">Locations & Directions</a>
<a class="nav--secondary__link " href="/services" disablewebedit="True">Services</a>
Showing first 10 of 122 audited elements.
Elements must only use permitted ARIA attributes9 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
Elements must only use supported ARIA attributes9 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
<i class="icon-social-twitter" role="img" aria-label="Twitter Icon"></i>
<i class="icon-social-youtube" role="img" aria-label="YouTube Icon"></i>
<i class="icon-social-instagram" role="img" aria-label="Instagram Icon"></i>
<i class="icon-social-linkedin" role="img" aria-label="LinkedIn Icon"></i>
<i class="icon-social-pinterest" role="img" aria-label="Pinterest Icon"></i>
<i class="icon-social-snapchat" role="img" aria-label="Snapchat Icon"></i>
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
Elements should not have tabindex greater than zero8 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe src="https://oc-cdn-ocpro..." name="Microsoft_Omnichanne..." id="Microsoft_Omnichanne..." title="Chat Widget" allow="microphone *; camera..." allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscree...="true" height="0px" width="0px" role="presentation" ...>
Frames must have an accessible name2 elements
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe id="bigidcmp-banner-widget" aria-label="BigID CMP Widget" style="border: 0px; z-index: 2147483647; height: 0px; width: 0px; position: fixed; left: 50%; bottom: -180px; transition: 300ms linear; transform: translate(-50%, 0px);"></iframe>
<iframe src="https://oc-cdn-ocpro..." name="Microsoft_Omnichanne..." id="Microsoft_Omnichanne..." title="Chat Widget" allow="microphone *; camera..." allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscree...="true" height="0px" width="0px" role="presentation" ...>
Heading levels should only increase by one24 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="hero__title">We're here when you need us — for every care in the world.</h1>
<h3 class="story-panel__title">Locations & Directions</h3>
<h3 class="story-panel__title">Appointments</h3>
<h2 class="cta-panel__card-header" style="height: auto;">Get Care</h2>
<h2 class="cta-panel__card-header" style="height: 44px;">Live Healthier</h2>
<h2 class="cta-panel__card-header" style="height: 44px;">Need Help?</h2>
<h2 class="container--md">Why Choose Cleveland Clinic?</h2>
<h3>Patient-centered care:</h3>
<h3>National recognition:</h3>
<h3>Collaborative providers:</h3>
Showing first 10 of 24 audited elements.
Headings should not be empty26 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="hero__title">We're here when you need us — for every care in the world.</h1>
<h3 class="story-panel__title">Our Providers</h3>
<h3 class="story-panel__title">Locations & Directions</h3>
<h3 class="story-panel__title">Appointments</h3>
<h2 class="cta-panel__card-header" style="height: auto;">Get Care</h2>
<h2 class="cta-panel__card-header" style="height: 44px;">Live Healthier</h2>
<h2 class="cta-panel__card-header" style="height: 44px;">Need Help?</h2>
<h2 class="container--md">Why Choose Cleveland Clinic?</h2>
<h3>Patient-centered care:</h3>
<h3>National recognition:</h3>
Showing first 10 of 26 audited elements.
Images must have alternative text22 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
<img src="/Assets/imgs/icon-alert--blue.svg" alt="exclamation icon">
<img src="/-/scassets/images/org/logo/logo-ccf.svg?h=48&la=en&w=300&hash=F5231F16526C9ED33D180771275ED4B7E42C2018" alt="Cleveland Clinic logo" width="300" height="48" disablewebedit="True">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/find-a-doctor-card.jpg" width="634" height="356" alt="Find a Doctor">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/locations-card.jpg" width="634" height="356" alt="Locations">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/appointments-card.jpg" width="634" height="356" alt="Appointments">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-appointments-dark-blue.svg" alt="Getting an appointment at Cleveland Clinic is easy. Schedule using any of these convenient options.">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-stay-healthy-light-blue.svg" alt="Find health and wellness information to help you and your family live a bit healthier each day.">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-need-help-green.svg" alt="Have a question? We want to make it easy to find what you're looking for. Get answers online fast.">
Showing first 10 of 22 audited elements.
Inline text spacing must be adjustable with custom stylesheets25 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div class="story-panel__card js-story-panel__card" style="height: 433.953px;">
<div class="story-panel__card js-story-panel__card" style="height: 433.953px;">
<div class="story-panel__card js-story-panel__card" style="height: 433.953px;">
<h2 class="cta-panel__card-header" style="height: auto;">Get Care</h2>
<p style="height: auto;">Getting an appointment at Cleveland Clinic is easy. Schedule using any of these convenient options.</p>
<div class="js-cta-panel__links" style="height: auto;">
<h2 class="cta-panel__card-header" style="height: 44px;">Live Healthier</h2>
<p style="height: 128px;">Find health and wellness information to help you and your family live a bit healthier each day.</p>
<div class="js-cta-panel__links" style="height: 187px;">
<h2 class="cta-panel__card-header" style="height: 44px;">Need Help?</h2>
Showing first 10 of 25 audited elements.
Interactive controls must not be nested50 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
<button class="notification-banner__action-icon js-notification-banner__action-icon">
<img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
</button><img src="/Assets/imgs/icon-close--blue.svg" alt="close button">
<img src="/Assets/imgs/icon-alert--blue.svg" alt="exclamation icon">
<img src="/-/scassets/images/org/logo/logo-ccf.svg?h=48&la=en&w=300&hash=F5231F16526C9ED33D180771275ED4B7E42C2018" alt="Cleveland Clinic logo" width="300" height="48" disablewebedit="True">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/find-a-doctor-card.jpg" width="634" height="356" alt="Find a Doctor">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/locations-card.jpg" width="634" height="356" alt="Locations">
<img class="js-story-panel__image" src="/-/scassets/images/org/locations/home/appointments-card.jpg" width="634" height="356" alt="Appointments">
<img src="/-/scassets/images/org/icons/care-pages/call-to-action/icon-appointments-dark-blue.svg" alt="Getting an appointment at Cleveland Clinic is easy. Schedule using any of these convenient options.">
<hr>
Showing first 10 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<header id="site-header" class="header js-site-header site-header__open-banner site-header__has-banner">
<footer class="footer js-footer">
Links must be distinguishable without relying on color4 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a href="/staff">our providers</a>
<a href="https://my.clevelandclinic.org/departments/patient-experience/depts/quality-patient-safety/treatment-outcomes">excellent outcomes</a>
<a href="/research">research</a>
<a href="/clinical-trials">clinical trials</a>
Links must have discernible text112 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="#notification-banner__lightbox-popup" class="notification-banner__link--expand js-notification-banner__link--expand js-lightbox-popup">
<img src="/-/scassets/images/org/icons/icon-emergency-circle.svg" alt="Emergency icon">
</a><a href="#notification-banner__lightbox-popup" class="js-lightbox-popup">
Important Updates
</a><a href="#notification-banner__lightbox-popup" class="nav--utility__link nav--utility__link--emergency-notification js-nav--utility__link--emergency-notification nav--hide js-lightbox-popup">
<a class="nav--utility__link nav--utility__link--phone" href="tel:800.223.2273">
800.223.2273
</a><a class="nav--utility__link " title="MyChart" href="/online-services/mychart" disablewebedit="True">MyChart</a>
<a class="nav--utility__link " title="Need help?" href="/help" disablewebedit="True">Need Help?</a>
<a class="nav--utility__link " href="/professionals" disablewebedit="True">Medical Professionals</a>
<a class="nav--utility__link " href="/giving" disablewebedit="True">Giving</a>
<a class="nav--utility__link " href="https://jobs.clevelandclinic.org/" disablewebedit="True" target="_blank">Careers</a>
<a href="/search" aria-label="Search" aria-controls="search-box" class="button--small button--search" disablewebedit="True" aria-expanded="false">Search</a>
Showing first 10 of 112 audited elements.
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" dir="ltr">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en" dir="ltr">
Required ARIA attributes must be provided17 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div class="content-block-faq-panel js-content-block-faq-panel" role="tablist">
<h3 tabindex="0" role="tab" id="institutes-departmen">Institutes & Departments</h3>
<h3 tabindex="0" role="tab" id="join-our-nursing-tea">Join Our Nursing Team</h3>
<h3 tabindex="0" role="tab" id="careers">Careers</h3>
<h3 tabindex="0" role="tab" id="refer-a-patient">Refer a Patient</h3>
<h3 tabindex="0" role="tab" id="consultqd">ConsultQD</h3>
<h3 tabindex="0" role="tab" id="education">Education</h3>
<h3 tabindex="0" role="tab" id="research">Research</h3>
<h3 tabindex="0" role="tab" id="view-all-resources-f">View All Resources for Providers</h3>
<i class="icon-social-facebook" role="img" aria-label="Facebook Icon"></i>
Showing first 10 of 17 audited elements.
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">