Cleveland Clinic my.clevelandclinic.org
Accessibility score
League position
6thof 10
Issues found
3
Audits passed
43
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousContent must reflow without two-dimensional scrolling1 element
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Failing Elements
<div data-identity="carousel-container" class="flex" style="transform: translate3d(16px, 0px, 0px);">
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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
Fix all of the following:
- Document does not have a main landmark
ModerateAll page content should be contained by landmarks37 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
<video controlslist="nodownload" autoplay="" disablepictureinpict...="" loop="" muted="" poster="https://assets.cleve..." playsinline="" class="absolute inset-0 w-a...">
Fix any of the following:
- Some page content is not contained by landmarks
<div data-identity="hero-text" class="absolute bottom-rem96px left-0 right-0 container">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="">
Fix any of the following:
- Some page content is not contained by landmarks
<img alt="cancer icon" loading="lazy" width="38" height="38" decoding="async" data-nimg="1" style="color:transparent" srcset="https://assets.cleve..." src="https://assets.cleve...">
Fix any of the following:
- Some page content is not contained by landmarks
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
Fix any of the following:
- Some page content is not contained by landmarks
<p class="my-rem12px text-gray-800 leading-rem24px">Prevention, testing and treatment</p>
Fix any of the following:
- Some page content is not contained by landmarks
<img alt="children's icon" loading="lazy" width="38" height="38" decoding="async" data-nimg="1" style="color:transparent" srcset="https://assets.cleve..." src="https://assets.cleve...">
Fix any of the following:
- Some page content is not contained by landmarks
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
Fix any of the following:
- Some page content is not contained by landmarks
<p class="my-rem12px text-gray-800 leading-rem24px">Well-checks and pediatric care</p>
Fix any of the following:
- Some page content is not contained by landmarks
<img alt="stomach icon" loading="lazy" width="38" height="38" decoding="async" data-nimg="1" style="color:transparent" srcset="https://assets.cleve..." src="https://assets.cleve...">
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 37 failing elements.
Passed audits43 across 1 page
<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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
<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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
<li> elements must be contained in a <ul> or <ol>5 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 class="flex items-baseline text-rem15px leading-rem20px"><a data-identity="ss-link" href="https://my.clevelandclinic.org/providers" class="text-brandBlue-500 hover:text-blue-800 transition py-rem4px px-rem8px" target="_blank" rel="noopener noreferrer">Find a Provider</a></li>
<li class="flex items-baseline text-rem15px leading-rem20px"><a data-identity="ss-link" href="https://my.clevelandclinic.org/locations" class="text-brandBlue-500 hover:text-blue-800 transition py-rem4px px-rem8px" target="_blank" rel="noopener noreferrer">Locations and Directions</a></li>
<li class="flex items-baseline text-rem15px leading-rem20px">
<li class="flex items-baseline text-rem15px leading-rem20px">
<li class="flex items-baseline text-rem15px leading-rem20px">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
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 data-identity="desktop-primary-nav" class="flex items-center gap-x-rem16px bp1400:gap-x-rem24px hidden bp900:flex">
All page content should be contained by landmarks354 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
<div id="d89JF2Fa-exV-5ixaiTVui1y_gqYcnxAVAB0ZZvIj8rs"></div>
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<div class="print:hidden">
<div data-identity="utility-nav" class="w-full bg-gray-300 ">
<div class="w-full flex justify-between items-stretch">
Showing first 5 of 354 audited elements.
Alternative text of images should not be repeated as text32 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 data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img alt="Blue alert icon 1" loading="lazy" width="23" height="23" decoding="async" data-nimg="1" class="w-[23px] h-auto hove..." srcset="/_next/static/media/..." src="/_next/static/media/..." style="color: transparent;">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
Showing first 5 of 32 audited elements.
ARIA attributes must be used as specified for the element's role10 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
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false">Showing first 5 of 10 audited elements.
ARIA attributes must conform to valid names10 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
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false">Showing first 5 of 10 audited elements.
ARIA attributes must conform to valid values10 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
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false">Showing first 5 of 10 audited elements.
ARIA hidden element must not be focusable or contain focusable elements1 element
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<span aria-hidden="true" data-identity="notification-divider" class="self-stretch opacity-0 pointer-events-none transition duration-300 ease-out block w-px bg-gray-400"></span>
ARIA role should be appropriate for the element3 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
<span data-identity="disabled-button" role="button" aria-disabled="true" class="cursor-not-allowed s...">
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
<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" ...>
ARIA roles used must conform to valid values2 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 aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
<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" ...>
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>
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 data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
Buttons must have discernible text17 elements
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 aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button aria-label="Open notification ba..." class="pl-rem8px bp1100:pl-..." data-identity="notification-banner-..." title="Open notification ba...">
Showing first 5 of 17 audited elements.
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 data-identity="footer" class="bg-brandBlue-500 print:bg-transparent ">
Deprecated ARIA roles must not be used2 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 aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
<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" ...>
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 data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
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 data-identity="footer" class="bg-brandBlue-500 print:bg-transparent ">
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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
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 thresholds132 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
<div data-identity="single-line-nav-label" class="flex-none font-bold h-rem40px py-rem8px pl-rem16px bp1400:pl-rem32px">Locations:</div>
<a href="https://www.clevelandclinicabudhabi.ae/en" target="_blank" class="px-rem12px py-rem8px first:pl-rem16px inline-block transition hover:text-blue-600 ">Abu Dhabi</a>
<a href="https://my.clevelandclinic.org/canada" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">Canada</a>
<a href="https://my.clevelandclinic.org/florida" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">Florida</a>
<a href="https://clevelandcliniclondon.uk/" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">London</a>
Showing first 5 of 132 audited elements.
Elements must only use permitted ARIA attributes10 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
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false">Showing first 5 of 10 audited elements.
Elements must only use supported ARIA attributes10 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
<header data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false"><button class="py-rem4px px-rem8px rounded-[0.3125rem] group transition leading-rem23px text-brandBlue-500 hover:text-blue-800 flex justify-between items-center
duration-[380ms] ease-in-out motion-reduce:transition-none " aria-expanded="false">Showing first 5 of 10 audited elements.
Focused elements must not be entirely hidden by author-created content46 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a href="https://www.clevelandclinicabudhabi.ae/en" target="_blank" class="px-rem12px py-rem8px first:pl-rem16px inline-block...">
<a href="https://my.clevelandclinic.org/canada" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://my.clevelandclinic.org/florida" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://clevelandcliniclondon.uk/" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://my.clevelandclinic.org/locations/nevada" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
Showing first 5 of 46 audited elements.
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 one21 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="w-full bp600:w-9/12 bp900:w-1/2 bp1400:w-5/12 text-rem40px leading-rem44px bp900:text-rem48px bp900:leading-rem52px text-white mb-rem40px"><div class="font-black">We’re here when you need us — for every care in the world.<!-- --> </div></h1>
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
Showing first 5 of 21 audited elements.
Headings should not be empty21 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="w-full bp600:w-9/12 bp900:w-1/2 bp1400:w-5/12 text-rem40px leading-rem44px bp900:text-rem48px bp900:leading-rem52px text-white mb-rem40px"><div class="font-black">We’re here when you need us — for every care in the world.<!-- --> </div></h1>
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
<h2 data-identity="headline" class="text-brandBlue-500 font-bold leading-rem30px text-rem25px bp600:text-rem32px bp600:leading-rem38px print:text-rem19px print:leading-rem27px print:font-semibold mt-rem12px">
Showing first 5 of 21 audited elements.
IDs used in ARIA and labels must be unique9 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<h3 data-identity="headline" id="d2b6b72d6f8a" class="text-gray-900 font-bold leading-rem24px text-rem20px bp600:text-rem25px bp600:leading-rem30px print:text-rem15px print:leading-rem20px print:font-bold ">
<h3 data-identity="headline" id="5aaa8154f946" class="text-gray-900 font-bold leading-rem24px text-rem20px bp600:text-rem25px bp600:leading-rem30px print:text-rem15px print:leading-rem20px print:font-bold ">
<h3 data-identity="headline" id="d331d63ff8ae" class="text-gray-900 font-bold leading-rem24px text-rem20px bp600:text-rem25px bp600:leading-rem30px print:text-rem15px print:leading-rem20px print:font-bold ">
<h3 data-identity="headline" id="3cc28e4ca8a0" class="text-gray-900 font-bold leading-rem24px text-rem20px bp600:text-rem25px bp600:leading-rem30px print:text-rem15px print:leading-rem20px print:font-bold ">
<h3 data-identity="headline" id="21de6c8d9079" class="text-gray-900 font-bold leading-rem24px text-rem20px bp600:text-rem25px bp600:leading-rem30px print:text-rem15px print:leading-rem20px print:font-bold ">
Showing first 5 of 9 audited elements.
Images must have alternative text32 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 data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img alt="Blue alert icon 1" loading="lazy" width="23" height="23" decoding="async" data-nimg="1" class="w-[23px] h-auto hove..." srcset="/_next/static/media/..." src="/_next/static/media/..." style="color: transparent;">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
Showing first 5 of 32 audited elements.
Inline text spacing must be adjustable with custom stylesheets28 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
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img alt="Cleveland Clinic log..." loading="lazy" decoding="async" data-nimg="fill" style="position:absolute;he..." sizes="100vw" srcset="https://assets.cleve..." src="https://assets.cleve...">
Showing first 5 of 28 audited elements.
Interactive controls must not be nested49 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 data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="32" height="40" decoding="async" data-nimg="1" class="absolute right-0 top..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
<button aria-label="Open notification banner" class="delay-700 transition duration-300 ease-out opacity-0 pointer-events-none scale-[0.565]" data-identity="notification-banner-icon-button" title="Open notification banner">
<img alt="Blue alert icon 1" loading="lazy" width="23" height="23" decoding="async" data-nimg="1" class="w-[23px] h-auto hove..." srcset="/_next/static/media/..." src="/_next/static/media/..." style="color: transparent;">
<img data-identity="single-line-nav-fade..." alt="Gray gradient" loading="lazy" width="16" height="40" decoding="async" data-nimg="1" class="absolute left-0 top-..." style="color:transparent" srcset="/_next/static/media/..." src="/_next/static/media/...">
Showing first 5 of 49 audited elements.
Interactive elements must have a visible focus indicator50 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a href="https://www.clevelandclinicabudhabi.ae/en" target="_blank" class="px-rem12px py-rem8px first:pl-rem16px inline-block...">
<a href="https://my.clevelandclinic.org/canada" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://my.clevelandclinic.org/florida" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://clevelandcliniclondon.uk/" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
<a href="https://my.clevelandclinic.org/locations/nevada" target="_blank" class="px-rem12px py-rem8px inline-block transition hove...">
Showing first 5 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 data-identity="centered-site-header" aria-label="Site Header" class="relative z-50 bg-white border-b border-gray-400">
<footer data-identity="footer" class="bg-brandBlue-500 print:bg-transparent ">
Links must be distinguishable without relying on color3 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 data-identity="link" href="https://my.cleveland..." class="text-brandBlue-500 p...">
<a data-identity="link" href="https://my.clevelandclinic.org/clinical-trials" class="text-brandBlue-500 print:text-black underline underline-offset-[5px] print:no-underline decoration-1 break-words hover:text-blue-800 transition">clinical trials</a>
<a data-identity="copyright-phone" href="tel:8002232273" class="text-white print:text-black transition">Call: <span class="underline print:no-underline">800.223.2273</span></a>
Links must have discernible text88 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="https://www.clevelandclinicabudhabi.ae/en" target="_blank" class="px-rem12px py-rem8px first:pl-rem16px inline-block transition hover:text-blue-600 ">Abu Dhabi</a>
<a href="https://my.clevelandclinic.org/canada" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">Canada</a>
<a href="https://my.clevelandclinic.org/florida" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">Florida</a>
<a href="https://clevelandcliniclondon.uk/" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">London</a>
<a href="https://my.clevelandclinic.org/locations/nevada" target="_blank" class="px-rem12px py-rem8px inline-block transition hover:text-blue-600 ">Nevada</a>
Showing first 5 of 88 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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
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" class="__variable_a857ad __variable_8bd802 __variable_da479a bg-white">
Required ARIA attributes must be provided2 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 aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
<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" ...>
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
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">
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">
How does your site stack up against Cleveland Clinic?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Healthcare