Medicaremedicare.gov
Accessibility Score
Issues Found
Issues Found
SeriousFrames must have an accessible name1 element
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.
Failing Elements
<iframe data-src="https://surveys.cms.gov/jfe/form/SV_9LbdFueyKSYZ2nk?Q_CHL=si&Q_CanScreenCapture=1" width="100%" height="100%" frameborder="0" name="survey-iframe-SI_6tbIx8xW9ShoDfU" data-name="embedded-iframe-SI_6tbIx8xW9ShoDfU"></iframe>
Fix any of the following:
- Element has no title 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's default semantics were not overridden with role="none" or role="presentation"
Passed Audits
<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" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
<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" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
<li> elements must be contained in a <ul> or <ol>27 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>
<a href="/health-drug-plans" rel="noopener" data-drupal-link-system-path="node/110756" data-listener-attached="true">Health & drug plans</a>
</li><li>
<a href="/basics" rel="noopener" data-drupal-link-system-path="node/109186" data-listener-attached="true">Medicare basics</a>
</li><li>
<a href="/providers-services" rel="noopener" data-drupal-link-system-path="node/112781" data-listener-attached="true">Providers & services</a>
</li><li>
<a href="/coverage" rel="noopener" data-drupal-link-system-path="node/113461" data-listener-attached="true">What Medicare covers</a>
</li><li>
<a href="/sitemap" rel="noopener" data-drupal-link-system-path="sitemap" data-listener-attached="true">Site map</a>
</li><li>
<a href="https://www.medicare.gov/plan-compare/" title="Find health & drug plans" rel="noopener" data-listener-attached="true">Find health & drug plans</a>
</li><li>
<a href="/care-compare/" title="Find care providers" rel="noopener" data-listener-attached="true">Find care providers</a>
</li><li>
<a href="/medical-equipment-suppliers/" title="Find medical equipment & suppliers" rel="noopener" data-listener-attached="true">Find medical equipment & suppliers</a>
</li><li>
<a href="/medigap-supplemental-insurance-plans/" title="Find a Medicare Supplement Insurance (Medigap) policy" rel="noopener" data-listener-attached="true">Find a Medicare Supplement Insurance (Medigap) policy</a>
</li><li>
<a href="/publications" title="Find publications" rel="noopener" data-drupal-link-system-path="node/111066" data-listener-attached="true">Find publications</a>
</li>Showing first 10 of 27 audited elements.
<svg> elements with an img role must have alternative text2 elements
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg role="img" aria-labelledby="medicare-gov-logo-simple-footer" width="273" height="39" class="m-c-footer__medicare-logo" xml:space="preserve" preserveAspectRatio="xMidYMid meet" viewBox="0 0 198 29" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg aria-hidden="false" class="ds-c-icon ds-c-icon--hhs-logo m-c-footer__hhs-logo" id="icon--6" viewBox="0 0 252 252" xmlns="http://www.w3.org/2000/svg" aria-labelledby="hhs-gov-logo-simple-footer" role="img">
<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 class="ds-c-list--bare ds-u-flex-direction--row">
All page content should be contained by landmarks357 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
<a href="#content" class="visually-hidden focusable skip-link" data-listener-attached="true">
Skip to main content
</a><div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas="">
<div id="consistent-header">
<div class="region region-consistent-header">
<div id="block-consistentheaderblock" class="block block-consistent-header block-consistent-header-block">
<div id="medicare-header-root" class="notranslate sl_opaque" translate="no" lang="en" lang-toggle-link="https://es.medicare.gov/" login-url="/account/login" logout-url="/sso/signout" enable-live-chat="true">
<div id="ch-root" style="visibility: hidden; height: 92px; max-height: 92px;">
<header aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<div class="usa-accordion">
Showing first 10 of 357 audited elements.
Alternative text of images should not be repeated as text10 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 class="usa-banner__header-f..." src="data:image/png;base6..." alt="U.S. flag">
<img class="medicare-logo" src="https://frontend.medicare.gov/assets/medicare-logo-green-6a40fc58.svg" alt="Medicare.gov">
<img src="https://frontend.medicare.gov/assets/Icon_Chat-f1ad62dd.svg" alt="">
<img src="https://frontend.medicare.gov/assets/Log_In-b51e10d7.svg" alt="">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="264" height="318" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="white senior lady in..." class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="256" height="318" src="/sites/default/files..." alt="Bearded man using ta..." class="image">
<img src="https://gov1.siteintercept.qualtrics.com/WRQualtricsShared/Graphics/siteintercept/popup_shadow_transparent.png" alt="" style="width: 678px; max-width: 678px; height: 786px; top: -65px; left: -56px; position: absolute;">
ARIA attributes must be used as specified for the element's role30 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
Showing first 10 of 30 audited elements.
ARIA attributes must conform to valid names30 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
Showing first 10 of 30 audited elements.
ARIA attributes must conform to valid values30 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
Showing first 10 of 30 audited elements.
ARIA commands must have an accessible name6 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<div aria-label="Close dialog" role="button" tabindex="0"><div aria-hidden="true"><img src="https://gov1.siteintercept.qualtrics.com/static/q-siteintercept/~/img/svg-close-btn-black-7.svg"></div></div>
ARIA hidden element must not be focusable or contain focusable elements28 elements
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
<p class="usa-banner__header-action" aria-hidden="true">Here's how you know</p>
<img class="usa-banner__icon usa-media-block__img" src="https://frontend.medicare.gov/assets/icon-dot-gov-54f6653a.svg" role="img" alt="" aria-hidden="true">
<img class="usa-banner__icon usa-media-block__img" src="https://frontend.medicare.gov/assets/icon-https-912daff9.svg" role="img" alt="" aria-hidden="true">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--hamburger ch-c-button--space-between" focusable="false" id="icon-1" viewBox="2 2 30 30" xmlns="http://www.w3.org/2000/svg" data-testid="veggieburger">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--close ds-c-icon--close-thin " focusable="false" id="icon-2" viewBox="-2 -2 18 18" xmlns="http://www.w3.org/2000/svg">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--arrow ds-c-icon--arrow-right" focusable="false" id="icon-3" viewBox="0 0 320 512" xmlns="http://www.w3.org/2000/svg" direction="right">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--arrow ds-c-icon--arrow-right" focusable="false" id="icon-4" viewBox="0 0 320 512" xmlns="http://www.w3.org/2000/svg" direction="right">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--arrow ds-c-icon--arrow-right" focusable="false" id="icon-5" viewBox="0 0 320 512" xmlns="http://www.w3.org/2000/svg" direction="right">
<svg aria-hidden="true" class="ds-c-icon ds-c-icon--arrow ds-c-icon--arrow-right" focusable="false" id="icon-6" viewBox="0 0 320 512" xmlns="http://www.w3.org/2000/svg" direction="right">
<svg width="12px" height="7px" viewBox="0 0 12 7" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" class="ch-c-caret-fixed-size ch-u-margin-left--4px" aria-hidden="true" focusable="false">
Showing first 10 of 28 audited elements.
ARIA role should be appropriate for the element32 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
<img class="usa-banner__icon usa-media-block__img" src="https://frontend.medicare.gov/assets/icon-dot-gov-54f6653a.svg" role="img" alt="" aria-hidden="true">
<img class="usa-banner__icon usa-media-block__img" src="https://frontend.medicare.gov/assets/icon-https-912daff9.svg" role="img" alt="" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" width="52" height="64" viewBox="0 0 52 64" class="usa-banner__lock-image" role="img" aria-labelledby="banner-lock-title banner-lock-description" focusable="false">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
Showing first 10 of 32 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
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<div class="search-block-form block block-search" data-drupal-selector="search-block-form" id="block-medicare-evo-searchform-2" role="search" data-component-id="medicare_evo:search-block">
<fieldset role="group" aria-label="Signup form for email updates" class="ds-c-fieldset ds-u-margin-top--0 js-form-item form-item js-form-wrapper form-wrapper" data-drupal-selector="edit-step1" id="edit-step1--2">
<ul role="list">
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="path-index path-frontpage page-node-type-layout-homepage ds-base">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input class="ds-c-field form-email required" autocomplete="off" data-drupal-selector="edit-step1-email" type="email" id="edit-step1-email--2" name="step1[email]" value="" size="60" maxlength="254" placeholder="[email protected]" required="required">
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 aria-label="medicare header">
Buttons must have discernible text11 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 class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button aria-expanded="false" aria-controls="search-block-form" class="ds-c-button search-block__toggle">
<button class="link-list__toggle" aria-controls="link-list-block-medicare-evo-sitemenu" aria-expanded="true" disabled="">
<span class="link-list__toggle-icon"></span>
<span class="link-list__title-text">Site Menu</span>
</button><button class="link-list__toggle" aria-controls="link-list-block-medicare-evo-takeaction" aria-expanded="true" disabled="">
<span class="link-list__toggle-icon"></span>
<span class="link-list__title-text">Take Action</span>
</button><button class="link-list__toggle" aria-controls="link-list-block-medicare-evo-cmshhswebsites" aria-expanded="true" disabled="">
<span class="link-list__toggle-icon"></span>
<span class="link-list__title-text">CMS & HHS Websites</span>
</button><button class="link-list__toggle" aria-controls="link-list-block-medicare-evo-helpfullinks" aria-expanded="true" disabled="">
<span class="link-list__toggle-icon"></span>
<span class="link-list__title-text">Helpful Links</span>
</button>Showing first 10 of 11 audited elements.
Certain ARIA roles must be contained by particular parents5 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
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
Certain ARIA roles must contain particular children6 elements
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.
Audit Elements
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<ul role="list">
<ul role="list">
<ul role="list">
<ul role="list">
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 ds-u-fill--gray-lightest ds-u-padding-y--4" aria-label="support menus and email sign-up">
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
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<div class="search-block-form block block-search" data-drupal-selector="search-block-form" id="block-medicare-evo-searchform-2" role="search" data-component-id="medicare_evo:search-block">
<fieldset role="group" aria-label="Signup form for email updates" class="ds-c-fieldset ds-u-margin-top--0 js-form-item form-item js-form-wrapper form-wrapper" data-drupal-selector="edit-step1" id="edit-step1--2">
<ul role="list">
Showing first 10 of 17 audited elements.
Document 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.
Audit Elements
<html lang="en" dir="ltr" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
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 aria-label="medicare 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 ds-u-fill--gray-lightest ds-u-padding-y--4" aria-label="support menus and email sign-up">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main id="content" class="ds-l-col--12 ds-u-padding-x--0 ds-u-md-padding-x--2 primary-content__content">
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" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
Elements marked as presentational should be consistently ignored6 elements
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
<img src="https://frontend.medicare.gov/assets/Icon_Chat-f1ad62dd.svg" alt="">
<img src="https://frontend.medicare.gov/assets/Log_In-b51e10d7.svg" alt="">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="264" height="318" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img src="https://gov1.siteintercept.qualtrics.com/WRQualtricsShared/Graphics/siteintercept/popup_shadow_transparent.png" alt="" style="width: 678px; max-width: 678px; height: 786px; top: -65px; left: -56px; position: absolute;">
Elements must meet minimum color contrast ratio thresholds66 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
<p class="usa-banner__header-text">An official website of the United States government</p>
<span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span>
<a class="ch-c-change-language-link ds-u-text-decoration--underline" data-testid="lng-tgl-btn" href="https://es.medicare.gov/" lang="es" data-listener-attached="true">Cambiar a español</a>
<span class="nav-text nav-text--3">Basics</span>
<span class="nav-text nav-text--3">Health & Drug Plans</span>
<span class="nav-text nav-text--3">Providers & Services</span>
<span class="ch-icon-caption ">Chat</span>
<span class="ch-icon-caption ">Log in</span>
<input title="Enter the terms you ..." data-drupal-selector="edit-keys" class="form-autocomplete fo..." data-autocomplete-pa...="/vertex_autocomplete..." type="search" id="edit-keys" name="keys" value="" size="15" maxlength="128" aria-label="Search Medicare.gov" autocomplete="off" ...>
<input data-drupal-selector="edit-submit" type="submit" id="edit-submit" value="Search" class="button js-form-submit form-submit ds-c-button ds-c-button--solid" aria-label="Submit Search">
Showing first 10 of 66 audited elements.
Elements must only use permitted ARIA attributes30 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
Showing first 10 of 30 audited elements.
Elements must only use supported ARIA attributes30 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
Showing first 10 of 30 audited elements.
Elements should not have tabindex greater than zero4 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
<div tabindex="0" style="top: 0px; left: 0px; position: absolute; z-index: 2000000000; width: 565px; height: 655px; background-color: rgb(255, 255, 255); border-width: 0px; border-color: rgb(105, 105, 105); border-style: solid; border-radius: 0px; display: block; outline: none;">
<div tabindex="0" style="top: 8px; left: 30px; position: absolute; z-index: 2000000001; width: 510px; height: 645px; background-color: rgb(255, 255, 255); border-width: 0px; border-color: transparent; border-style: solid; border-radius: 0px; display: block;">
<div tabindex="0" style="top: 19px; left: 531px; position: absolute; z-index: 2000000002; width: 21px; height: 22px; background-color: transparent; border-width: 0px; border-color: rgb(0, 0, 0); border-style: solid; border-radius: 0px; display: block; opacity: 0.7; cursor: pointer;">
<div aria-label="Close dialog" role="button" tabindex="0"><div aria-hidden="true"><img src="https://gov1.siteintercept.qualtrics.com/static/q-siteintercept/~/img/svg-close-btn-black-7.svg"></div></div>
Form elements must have labels2 elements
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input class="ds-c-field form-email required" autocomplete="off" data-drupal-selector="edit-step1-email" type="email" id="edit-step1-email--2" name="step1[email]" value="" size="60" maxlength="254" placeholder="[email protected]" required="required">
<input class="ds-c-choice form-checkbox required" data-drupal-selector="edit-step1-consent" type="checkbox" id="edit-step1-consent--2" name="step1[consent]" value="1" required="required">
Form elements should have a visible label2 elements
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input class="ds-c-field form-email required" autocomplete="off" data-drupal-selector="edit-step1-email" type="email" id="edit-step1-email--2" name="step1[email]" value="" size="60" maxlength="254" placeholder="[email protected]" required="required">
<input class="ds-c-choice form-checkbox required" data-drupal-selector="edit-step1-consent" type="checkbox" id="edit-step1-consent--2" name="step1[consent]" value="1" required="required">
Form field must not have multiple label elements2 elements
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input class="ds-c-field form-email required" autocomplete="off" data-drupal-selector="edit-step1-email" type="email" id="edit-step1-email--2" name="step1[email]" value="" size="60" maxlength="254" placeholder="[email protected]" required="required">
<input class="ds-c-choice form-checkbox required" data-drupal-selector="edit-step1-consent" type="checkbox" id="edit-step1-consent--2" name="step1[consent]" value="1" required="required">
Frames must have a unique title attribute2 elements
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 allowfullscreen="" class="genesys-mxg-frame genesys-mxg-responsive genesys-mxg-launcher-frame" id="genesys-mxg-frame" title="Messenger Launcher" name="MessengerLauncherFrame" width="100%" scrolling="no" src="https://apps.use2.us-gov-pure.cloud/messenger/messenger.html"></iframe>
<iframe allowfullscreen="" class="genesys-mxg-frame genesys-mxg-responsive genesys-mxg-container-frame" id="genesys-mxg-container-frame" title="Messenger" name="MessengerFrame" width="100%" src="https://apps.use2.us-gov-pure.cloud/messenger/messenger-renderer.html"></iframe>
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 allowfullscreen="" class="genesys-mxg-frame genesys-mxg-responsive genesys-mxg-launcher-frame" id="genesys-mxg-frame" title="Messenger Launcher" name="MessengerLauncherFrame" width="100%" scrolling="no" src="https://apps.use2.us-gov-pure.cloud/messenger/messenger.html"></iframe>
<iframe allowfullscreen="" class="genesys-mxg-frame genesys-mxg-responsive genesys-mxg-container-frame" id="genesys-mxg-container-frame" title="Messenger" name="MessengerFrame" width="100%" src="https://apps.use2.us-gov-pure.cloud/messenger/messenger-renderer.html"></iframe>
Heading levels should only increase by one14 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="homepage-hero__title ">
<span>Welcome to Medicare</span>
</h1><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Log in or create an account
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Find health & drug plans
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Find care providers
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Talk to someone
</h2><h2 class="initiative__title ">
Easier, secure Medicare account options
</h2><h2 class="initiative__title ">
Protect yourself from Medicare fraud
</h2><h2 class="initiative__title ">
New! Take control of your health data with Medicare’s app library
</h2><h2 class="initiative__title ">
Recent court decisions about nondiscrimination
</h2><h2 class="form-block__heading ">
Get important news & updates
</h2>Showing first 10 of 14 audited elements.
Headings should not be empty14 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="homepage-hero__title ">
<span>Welcome to Medicare</span>
</h1><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Log in or create an account
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Find health & drug plans
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Find care providers
</h2><h2 class="tab-icon-card__title ds-u-leading--heading ds-text-heading--xl ">
Talk to someone
</h2><h2 class="initiative__title ">
Easier, secure Medicare account options
</h2><h2 class="initiative__title ">
Protect yourself from Medicare fraud
</h2><h2 class="initiative__title ">
New! Take control of your health data with Medicare’s app library
</h2><h2 class="initiative__title ">
Recent court decisions about nondiscrimination
</h2><h2 class="form-block__heading ">
Get important news & updates
</h2>Showing first 10 of 14 audited elements.
IDs used in ARIA and labels must be unique13 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
<div class="usa-banner__content usa-accordion__content" id="gov-banner" hidden="">
<title id="banner-lock-title">lock</title>
<desc id="banner-lock-description">A locked padlock</desc>
<form action="/search/medicare" method="get" id="search-block-form" accept-charset="UTF-8" role="search" class="search-form search-block-form" aria-hidden="true" data-once="searchPII">
<input title="Enter the terms you ..." data-drupal-selector="edit-keys" class="form-autocomplete fo..." data-autocomplete-pa...="/vertex_autocomplete..." type="search" id="edit-keys" name="keys" value="" size="15" maxlength="128" aria-label="Search Medicare.gov" autocomplete="off" ...>
<input class="ds-c-field form-email required" autocomplete="off" data-drupal-selector="edit-step1-email" type="email" id="edit-step1-email--2" name="step1[email]" value="" size="60" maxlength="254" placeholder="[email protected]" required="required">
<input class="ds-c-choice form-checkbox required" data-drupal-selector="edit-step1-consent" type="checkbox" id="edit-step1-consent--2" name="step1[consent]" value="1" required="required">
<div id="link-list-block-medicare-evo-sitemenu" aria-hidden="false" class="link-list__links">
<div id="link-list-block-medicare-evo-takeaction" aria-hidden="false" class="link-list__links">
<div id="link-list-block-medicare-evo-cmshhswebsites" aria-hidden="false" class="link-list__links">
Showing first 10 of 13 audited elements.
Images must have alternative text10 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 class="usa-banner__header-f..." src="data:image/png;base6..." alt="U.S. flag">
<img class="medicare-logo" src="https://frontend.medicare.gov/assets/medicare-logo-green-6a40fc58.svg" alt="Medicare.gov">
<img src="https://frontend.medicare.gov/assets/Icon_Chat-f1ad62dd.svg" alt="">
<img src="https://frontend.medicare.gov/assets/Log_In-b51e10d7.svg" alt="">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="264" height="318" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="white senior lady in..." class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="" class="image">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="256" height="318" src="/sites/default/files..." alt="Bearded man using ta..." class="image">
<img src="https://gov1.siteintercept.qualtrics.com/WRQualtricsShared/Graphics/siteintercept/popup_shadow_transparent.png" alt="" style="width: 678px; max-width: 678px; height: 786px; top: -65px; left: -56px; position: absolute;">
Inline text spacing must be adjustable with custom stylesheets1 element
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 id="ch-root" style="visibility: hidden; height: 92px; max-height: 92px;">
Input buttons must have discernible text1 element
Screen reader users cannot understand an input type="button"'s purpose without an accessible name. Unnamed button images provide no description of their destination, purpose, or function, leaving users unable to make informed decisions about activating them.
Audit Elements
<input data-drupal-selector="edit-emailsignup-actions-next1" type="submit" id="edit-emailsignup-actions-next1--2" name="op" value="Next Step" class="button button--primary js-form-submit form-submit ds-c-button ds-c-button--solid" data-once="drupal-ajax">
Interactive controls must not be nested20 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 class="usa-banner__header-f..." src="data:image/png;base6..." alt="U.S. flag">
<button class="usa-accordion__button usa-banner__button ds-u-text-decoration--underline" aria-expanded="false" aria-controls="gov-banner" data-testid="how-you-know-btn" type="button"><span class="usa-banner__button-text ds-u-color--secondary">Here's how you know</span></button>
<img class="medicare-logo" src="https://frontend.medicare.gov/assets/medicare-logo-green-6a40fc58.svg" alt="Medicare.gov">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-valign--bottom ch-u-text-hover--none ch-u-text-focus--none" type="button" aria-expanded="false">
<button aria-expanded="false" aria-controls="search-block-form" class="ds-c-button search-block__toggle">
<img loading="lazy" srcset="/sites/default/files..." sizes="(min-width:1040px) 3..." width="356" height="200" src="/sites/default/files..." alt="white senior lady in..." class="image">
<input class="ds-c-choice form-checkbox required" data-drupal-selector="edit-step1-consent" type="checkbox" id="edit-step1-consent--2" name="step1[consent]" value="1" required="required">
Showing first 10 of 20 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination13 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 aria-label="medicare header">
<section class="usa-banner" aria-label="Official government website">
<nav aria-label="Mobile Menu">
<nav aria-label="Main" class="ch-c-navmenu ch-u-remove--md">
<nav aria-label="Personal" class="ch-c-navmenu ch-u-remove--md">
<div class="search-block-form block block-search" data-drupal-selector="search-block-form" id="block-medicare-evo-searchform-2" role="search" data-component-id="medicare_evo:search-block">
<main id="content" class="ds-l-col--12 ds-u-padding-x--0 ds-u-md-padding-x--2 primary-content__content">
<footer class="footer ds-u-fill--gray-lightest ds-u-padding-y--4" aria-label="support menus and email sign-up">
<nav class="link-list " id="block-medicare-evo-sitemenu" data-component-id="medicare_evo:link-list" aria-label="Site Menu">
<nav class="link-list " id="block-medicare-evo-takeaction" data-component-id="medicare_evo:link-list" aria-label="Take Action">
Showing first 10 of 13 audited elements.
lang attribute must have a valid value2 elements
Screen readers use language-specific pronunciation libraries that must match the content's language. Invalid language declarations cause screen readers to use the wrong pronunciation library, making content sound confusing or unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<div id="medicare-header-root" class="notranslate sl_opaque" translate="no" lang="en" lang-toggle-link="https://es.medicare.gov/" login-url="/account/login" logout-url="/sso/signout" enable-live-chat="true">
<a class="ch-c-change-language-link ds-u-text-decoration--underline" data-testid="lng-tgl-btn" href="https://es.medicare.gov/" lang="es" data-listener-attached="true">Cambiar a español</a>
Links 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.
Audit Elements
<a href="/privacy-policy" data-listener-attached="true">data privacy policy</a>
Links must have discernible text47 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="#content" class="visually-hidden focusable skip-link" data-listener-attached="true">
Skip to main content
</a><a class="ch-c-change-language-link ds-u-text-decoration--underline" data-testid="lng-tgl-btn" href="https://es.medicare.gov/" lang="es" data-listener-attached="true">Cambiar a español</a>
<a class="nav-menu-button ds-u-display--flex ds-u-align-items--center" href="https://www.medicare.gov" data-listener-attached="true"><img class="medicare-logo" src="https://frontend.medicare.gov/assets/medicare-logo-green-6a40fc58.svg" alt="Medicare.gov"></a>
<a class="nav-menu-button ds-u-font-size--base ds-u-sans ds-u-display--flex" href="/account/login" data-listener-attached="true">
<a data-component-type="homepage-hero" class="ds-c-button ds-c-button--big ds-c-button--solid homepage-hero__cta" href="/basics/get-started-with-medicare" data-once="homepage-hero-cta-link" data-listener-attached="true">
<a data-component-type="card" class="ds-c-button ds-c-button--solid tab-icon-card__cta-link" href="https://www.medicare.gov/account/login" data-listener-attached="true">Log in/Create Account</a>
<a data-component-type="card" class="ds-c-button ds-c-button--solid tab-icon-card__cta-link" href="https://www.medicare.gov/plan-compare/" data-listener-attached="true">Find Plans Now</a>
<a data-component-type="card" class="ds-c-button ds-c-button--solid tab-icon-card__cta-link" href="https://www.medicare.gov/care-compare/" data-listener-attached="true">Find Providers Near Me</a>
<a data-component-type="card" class="ds-c-button ds-c-button--solid tab-icon-card__cta-link" href="/talk-to-someone" data-listener-attached="true">Get Help</a>
<a class="ds-c-button ds-c-button--solid initiative__cta-link " href="https://www.medicare.gov/account/login" data-once="initiative-cta-link" data-listener-attached="true">Create/Connect Your Account</a>
Showing first 10 of 47 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main id="content" class="ds-l-col--12 ds-u-padding-x--0 ds-u-md-padding-x--2 primary-content__content">
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" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
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" prefix="og: https://ogp.me/ns#" class="js fontawesome-i2svg-active fontawesome-i2svg-complete">
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
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<li class="" role="menuitem">
<ul class="ch-u-no-ul-styles ds-u-display--flex" role="menu">
<li class="" role="menuitem">
<li class="" role="menuitem">
<div class="search-block-form block block-search" data-drupal-selector="search-block-form" id="block-medicare-evo-searchform-2" role="search" data-component-id="medicare_evo:search-block">
<fieldset role="group" aria-label="Signup form for email updates" class="ds-c-fieldset ds-u-margin-top--0 js-form-item form-item js-form-wrapper form-wrapper" data-drupal-selector="edit-step1" id="edit-step1--2">
<ul role="list">
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">