Wells Fargowellsfargo.com
Accessibility Score
Issues Found
Issues Found
SeriousInteractive elements must have a visible focus indicator22 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.
Failing Elements
<input type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in..." name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signo..." name="j_password" maxlength="32" autocomplete="off">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
<input type="submit" name="btnSignon" id="btnSignon" class="ps-btn-primary" data-mrkt-tracking-id="3d6c76ba-9d34-4def-977d-a79cb8afc738" value="Sign On">
<a href="/privacy-security/?linkLoc=signon">
<a aria-label="Get started. Craft the foundation for your future." href="/financial-goals/?utm_source=wfhp&utm_medium=1..." data-presentation="2" class="ps-btn-secondary">
<a aria-label="Explore borrowing. Designed for every step of your..." href="/financial-goals/borrow/?utm_source=wfhp&utm_m..." data-presentation="2" class="ps-btn-secondary">
<a role="button" data-exit="true" class="ps-button-applestore" aria-label="Download on the App Store opens a dialog" data-href-id="1224111702" href="#">
<a href="/about/" class="ps-btn-secondary" data-cid="tcm:84-224409-16" data-ctid="tcm:91-223644-32" data-presentation="2">
Showing first 10 of 22 failing elements.
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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
<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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
<li> elements must be contained in a <ul> or <ol>41 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="/locator/">ATMs/Locations</a></li>
<li><a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a></li>
<li><a href="/es/" xml:lang="es" id="langPrefToggle" class="spTogglePersonal" name="langPrefToggle" lang="es">Español</a></li>
<li class="ps-search-item"><a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a></li>
<li class="ps-sign-on-item">
<li class="ps-fat-nav-item active">
<li class="ps-fat-nav-subitem"><a href="/checking/" class="">Checking</a></li>
<li class="ps-fat-nav-subitem"><a href="/savings-cds/" class="">Savings & CDs</a></li>
<li class="ps-fat-nav-subitem"><a href="https://creditcards.wellsfargo.com/?sub_channel=WEB&vendor_code=WF&linkLoc=FNMC&lang=en" data-platform="creditCardsWF">Credit Cards</a></li>
<li class="ps-fat-nav-subitem"><a href="/mortgage/" class="">Home Loans</a></li>
Showing first 10 of 41 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements9 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul>
<ul>
<ul class="ps-fat-nav-l2 expanded">
<ul>
<ul>
</ul><ul class="contact-bar-links">
<ul>
<ul>
<ul>
accesskey attribute value should be unique3 elements
Duplicate accesskey values create unpredictable keyboard shortcuts that confuse users who rely on keyboard navigation. Each accesskey must be unique and not conflict with browser or screen reader shortcuts. Keyboard users with vision impairments depend on these shortcuts to navigate efficiently without using a mouse.
Audit Elements
<input type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
All page content should be contained by landmarks371 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="#skip" class="hidden">Skip to main content</a>
<div class="ps-body-container app-preload-container data-app-preload-desktop" data-pid="702-224111-64" data-ptid="tcm:702-223692-128">
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<div class="ps-masthead-wrapper">
<div class="new_logoOuter">
<div class="ps-logo-home">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
</div>
</div><div class="ps-logo-home">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
</div><img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
<nav class="ps-right-nav" aria-label="Header Navigation">
<ul>
Showing first 10 of 371 audited elements.
Alternative text of images should not be repeated as text15 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
<img fetchpriority="high" alt="Enjoy $325" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/target/1700x700/4a_hppb_marquee_banner_1700x700.jpg">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wf_ic_currency-us-dollar_con-gra_hpps_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wfi000_ic_b-wf_icon_ui_card_gradient_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/creditcard_color_gradient_64x64x.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/first_time_experience-account_summary.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/lpromo/wfi000_ph_bc_1600x700.jpg" alt="">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1184079607-financialgoals_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/smlpromo/wfi_ph_g_1421526094-borrowing_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1472303553-lifesync_hpsp_616x353.jpg">
Showing first 10 of 15 audited elements.
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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<nav class="ps-right-nav" aria-label="Header Navigation">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a aria-label="Get Started and find out how to get a $325 checking bonus." enrollmentid="5016" href="https://accountoffers.wellsfargo.com/checkingoffer/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPBQ226test" data-presentation="2" class="ps-btn-secondary">Get started >></a>
<a aria-label="Get started and earn a $125 bonus." href="https://accountoffers.wellsfargo.com/checking125/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPST1551" data-presentation="1" class="c7">Get started</a>
<a enrollmentid="3845" aria-label="Earn up to 40,000 bonus points with the Choice Privileges Mastercard Credit Cards. Terms apply. Learn more." href="https://creditcards.wellsfargo.com/wells-fargo-choice-privileges-credit-cards/" data-presentation="1" class="c7">Learn more</a>
<a enrollmentid="3845" aria-label="Earn 60,000 bonus po..." href="https://creditcards...." data-presentation="1" class="c7">
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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<nav class="ps-right-nav" aria-label="Header Navigation">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a aria-label="Get Started and find out how to get a $325 checking bonus." enrollmentid="5016" href="https://accountoffers.wellsfargo.com/checkingoffer/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPBQ226test" data-presentation="2" class="ps-btn-secondary">Get started >></a>
<a aria-label="Get started and earn a $125 bonus." href="https://accountoffers.wellsfargo.com/checking125/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPST1551" data-presentation="1" class="c7">Get started</a>
<a enrollmentid="3845" aria-label="Earn up to 40,000 bonus points with the Choice Privileges Mastercard Credit Cards. Terms apply. Learn more." href="https://creditcards.wellsfargo.com/wells-fargo-choice-privileges-credit-cards/" data-presentation="1" class="c7">Learn more</a>
<a enrollmentid="3845" aria-label="Earn 60,000 bonus po..." href="https://creditcards...." data-presentation="1" class="c7">
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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<nav class="ps-right-nav" aria-label="Header Navigation">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a aria-label="Get Started and find out how to get a $325 checking bonus." enrollmentid="5016" href="https://accountoffers.wellsfargo.com/checkingoffer/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPBQ226test" data-presentation="2" class="ps-btn-secondary">Get started >></a>
<a aria-label="Get started and earn a $125 bonus." href="https://accountoffers.wellsfargo.com/checking125/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPST1551" data-presentation="1" class="c7">Get started</a>
<a enrollmentid="3845" aria-label="Earn up to 40,000 bonus points with the Choice Privileges Mastercard Credit Cards. Terms apply. Learn more." href="https://creditcards.wellsfargo.com/wells-fargo-choice-privileges-credit-cards/" data-presentation="1" class="c7">Learn more</a>
<a enrollmentid="3845" aria-label="Earn 60,000 bonus po..." href="https://creditcards...." data-presentation="1" class="c7">
Showing first 10 of 30 audited elements.
ARIA hidden element must not be focusable or contain focusable elements70 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
<span aria-hidden="true" class="contact-bar-location-icon"></span>
<span aria-hidden="true" class="collapsible-icon collapsible-icon-collapse"></span>
<div aria-hidden="true" class="contact-bar-content contact-bar-content-hidden" id="find_location_block">
<span aria-hidden="true" class="contact-bar-appointment-icon"></span>
<span aria-hidden="true" class="collapsible-icon collapsible-icon-collapse"></span>
<div aria-hidden="true" class="contact-bar-content contact-bar-call-desc contact-bar-content-hidden" id="quick_help_block">
<span aria-hidden="true" class="right-chevron"></span>
<span aria-hidden="true" class="right-chevron"></span>
<span aria-hidden="true" class="right-chevron"></span>
<span aria-hidden="true" class="right-chevron"></span>
Showing first 10 of 70 audited elements.
ARIA role should be appropriate for the element42 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a aria-controls="find_location_block" aria-expanded="false" class="contact-bar-collapsible contact-bar-location" href="#" role="button" tabindex="0">
<span aria-level="3" class="contact-bar-select" role="heading"> Find a location </span>
<a aria-controls="quick_help_block" aria-expanded="false" class="contact-bar-collapsible contact-bar-call" href="#" role="button" tabindex="0">
<span aria-level="3" class="contact-bar-select" role="heading"> Quick help</span>
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<button class="ps-btn-alt go-btn" id="rates-go-btn" role="button" type="submit">Go</button>
<a class="check-rates-wrapper" id="check-rates-wrapper" aria-label="Check rates opens dropdown" role="button" href="#" data-goto="/help/rates/">
Showing first 10 of 42 audited elements.
ARIA roles used must conform to valid values12 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a class="check-rates-wrapper" id="check-rates-wrapper" aria-label="Check rates opens dropdown" role="button" href="#" data-goto="/help/rates/">
<a role="button" data-exit="true" class="ps-button-applestore" aria-label="Download on the App Store opens a dialog" data-href-id="1224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/App_Store_Badge.png" alt=""></a>
<a role="button" data-exit="true" class="ps-button-googleplay" aria-label="Get it on Google Play opens a dialog" data-href-id="3224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/GooglePlay_Badge.png" alt=""></a>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-location contact-bar-location-header" aria-expanded="false">
<span role="heading" aria-level="3" class="contact-bar-select">Find a location</span>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-call" aria-expanded="false">
Showing first 10 of 12 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>
autocomplete attribute must be used correctly2 elements
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 type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
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 class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
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="ps-footer-homepage">
Deprecated ARIA roles must not be used12 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a class="check-rates-wrapper" id="check-rates-wrapper" aria-label="Check rates opens dropdown" role="button" href="#" data-goto="/help/rates/">
<a role="button" data-exit="true" class="ps-button-applestore" aria-label="Download on the App Store opens a dialog" data-href-id="1224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/App_Store_Badge.png" alt=""></a>
<a role="button" data-exit="true" class="ps-button-googleplay" aria-label="Get it on Google Play opens a dialog" data-href-id="3224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/GooglePlay_Badge.png" alt=""></a>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-location contact-bar-location-header" aria-expanded="false">
<span role="heading" aria-level="3" class="contact-bar-select">Find a location</span>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-call" aria-expanded="false">
Showing first 10 of 12 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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
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="ps-footer-homepage">
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 class="ps-body-wrapper" style="padding-top: 57px;">
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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
Elements marked as presentational should be consistently ignored13 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://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wf_ic_currency-us-dollar_con-gra_hpps_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wfi000_ic_b-wf_icon_ui_card_gradient_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/creditcard_color_gradient_64x64x.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/first_time_experience-account_summary.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/lpromo/wfi000_ph_bc_1600x700.jpg" alt="">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1184079607-financialgoals_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/smlpromo/wfi_ph_g_1421526094-borrowing_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1472303553-lifesync_hpsp_616x353.jpg">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/Fargo-Spending-Insights-Wells-Fargo-Mobile-App-2025.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/App_Store_Badge.png" alt="">
Showing first 10 of 13 audited elements.
Elements must meet minimum color contrast ratio thresholds80 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<a href="/locator/">ATMs/Locations</a>
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="/es/" xml:lang="es" id="langPrefToggle" class="spTogglePersonal" name="langPrefToggle" lang="es">Español</a>
<a href="https://connect.secure.wellsfargo.com/auth/login/present?origin=cob&LOB=CONS" class="ps-sign-on-text" data-platform="applicationhost" data-host="Login App Host">Sign On</a>
<input class="contact-bar-input-box" id="supportDropDownLocator" name="qp" placeholder="" aria-label="City, State or ZIP" type="text">
<a data-platform="publicsite" href="/" exitdestination="" exitdisclaimer="" data-newbrowser="" enrollmentid="" data-rottracking="" class="" data-params="" data-responsive-params="" data-destinationtype="none" data-nativelinktype="none">
<a href="/checking/" class="">Checking</a>
<a href="/savings-cds/" class="">Savings & CDs</a>
<a href="https://creditcards.wellsfargo.com/?sub_channel=WEB&vendor_code=WF&linkLoc=FNMC&lang=en" data-platform="creditCardsWF">Credit Cards</a>
<a href="/mortgage/" class="">Home Loans</a>
Showing first 10 of 80 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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<nav class="ps-right-nav" aria-label="Header Navigation">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a aria-label="Get Started and find out how to get a $325 checking bonus." enrollmentid="5016" href="https://accountoffers.wellsfargo.com/checkingoffer/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPBQ226test" data-presentation="2" class="ps-btn-secondary">Get started >></a>
<a aria-label="Get started and earn a $125 bonus." href="https://accountoffers.wellsfargo.com/checking125/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPST1551" data-presentation="1" class="c7">Get started</a>
<a enrollmentid="3845" aria-label="Earn up to 40,000 bonus points with the Choice Privileges Mastercard Credit Cards. Terms apply. Learn more." href="https://creditcards.wellsfargo.com/wells-fargo-choice-privileges-credit-cards/" data-presentation="1" class="c7">Learn more</a>
<a enrollmentid="3845" aria-label="Earn 60,000 bonus po..." href="https://creditcards...." data-presentation="1" class="c7">
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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<nav class="ps-right-nav" aria-label="Header Navigation">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a aria-label="Get Started and find out how to get a $325 checking bonus." enrollmentid="5016" href="https://accountoffers.wellsfargo.com/checkingoffer/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPBQ226test" data-presentation="2" class="ps-btn-secondary">Get started >></a>
<a aria-label="Get started and earn a $125 bonus." href="https://accountoffers.wellsfargo.com/checking125/?sub_channel=WEB&vendor_code=WF&collateral_code=HPPST1551" data-presentation="1" class="c7">Get started</a>
<a enrollmentid="3845" aria-label="Earn up to 40,000 bonus points with the Choice Privileges Mastercard Credit Cards. Terms apply. Learn more." href="https://creditcards.wellsfargo.com/wells-fargo-choice-privileges-credit-cards/" data-presentation="1" class="c7">Learn more</a>
<a enrollmentid="3845" aria-label="Earn 60,000 bonus po..." href="https://creditcards...." data-presentation="1" class="c7">
Showing first 10 of 30 audited elements.
Elements should not have tabindex greater than zero2 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
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-location contact-bar-location-header" aria-expanded="false">
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-call" aria-expanded="false">
Form elements must have labels3 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 type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
Form elements should have a visible label3 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 type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
Form field must not have multiple label elements3 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 type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
Heading levels should only increase by one19 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="hidden" id="skip">Wells Fargo</h1>
<h2 id="sign-on-header">Good evening</h2>
<h2>$325 checking bonus on us</h2>
<h2>College students: say hello to a $125 bonus</h2>
<h2>Earn 40,000 bonus points</h2>
<h2>Earn 60,000 bonus points</h2>
<h2 class="ps-marketing-text-heading ">Interest rates today</h2>
<h2>Earn 60,000 bonus points</h2>
<h2 class="ps-mid-page-title">Financial guidance and support</h2>
<h3 class="title2-SemiBold">Your dreams, your plan</h3>
Showing first 10 of 19 audited elements.
Headings should not be empty19 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="hidden" id="skip">Wells Fargo</h1>
<h2 id="sign-on-header">Good evening</h2>
<h2>$325 checking bonus on us</h2>
<h2>College students: say hello to a $125 bonus</h2>
<h2>Earn 40,000 bonus points</h2>
<h2>Earn 60,000 bonus points</h2>
<h2 class="ps-marketing-text-heading ">Interest rates today</h2>
<h2>Earn 60,000 bonus points</h2>
<h2 class="ps-mid-page-title">Financial guidance and support</h2>
<h3 class="title2-SemiBold">Your dreams, your plan</h3>
Showing first 10 of 19 audited elements.
IDs used in ARIA and labels must be unique28 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 aria-hidden="true" class="contact-bar-content contact-bar-content-hidden" id="find_location_block">
<input class="contact-bar-input-box" id="supportDropDownLocator" name="qp" placeholder="" aria-label="City, State or ZIP" type="text">
<div aria-hidden="true" class="contact-bar-content contact-bar-call-desc contact-bar-content-hidden" id="quick_help_block">
<input type="text" accesskey="U" id="userid" class="form-element formElementText login_field signon-in" name="j_username" maxlength="14" value="" autocomplete="off">
<input type="password" accesskey="P" id="password" class="form-element formElementPassword login_field signon-in pmask" name="j_password" maxlength="32" autocomplete="off">
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
<select name="dropdown" id="check_rates_dropdown" aria-label="Check rates">
<input type="text" aria-label="City, State or ZIP" placeholder="" id="contactBarLocator" name="qp" class="contact-bar-input-box">
<p tabindex="1" id="headerTextAppStore">You are leaving the Wells Fargo website</p>
<p tabindex="1" id="headerTextGooglePlay">You are leaving the Wells Fargo website</p>
Showing first 10 of 28 audited elements.
Images must have alternative text15 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
<img fetchpriority="high" alt="Enjoy $325" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/target/1700x700/4a_hppb_marquee_banner_1700x700.jpg">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wf_ic_currency-us-dollar_con-gra_hpps_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/wfi000_ic_b-wf_icon_ui_card_gradient_64x64.png" alt="">
<img src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/64x64/creditcard_color_gradient_64x64x.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/first_time_experience-account_summary.png" alt="">
<img src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/lpromo/wfi000_ph_bc_1600x700.jpg" alt="">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1184079607-financialgoals_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/assets/images/contextual/responsive/smlpromo/wfi_ph_g_1421526094-borrowing_hpsp_616x353.jpg">
<img alt="" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/616x353/wfi_ph_g_1472303553-lifesync_hpsp_616x353.jpg">
Showing first 10 of 15 audited elements.
Inline text spacing must be adjustable with custom stylesheets2 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
<main class="ps-body-wrapper" style="padding-top: 57px;">
<div class="cmsDefault" data-placement-name="WF_CON_HP_LRG_PROMO" data-presentation-order="1" data-placement-presentation-order="WF_CON_HP_LRG_PROMO-1" lang="en" style="display: block !important">
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 type="submit" name="btnSignon" id="btnSignon" class="ps-btn-primary" data-mrkt-tracking-id="3d6c76ba-9d34-4def-977d-a79cb8afc738" value="Sign On">
Interactive controls must not be nested11 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<img src="https://www17.wellsfargomedia.com/assets/images/rwd/wf_logo_220x23.png" alt="Wells Fargo Home Page">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<input type="checkbox" accesskey="S" id="saveusername" class="c29link" name="saveusername" data-content-id="c29content-save-username" triggerhover="false" isclickable="true">
<input type="submit" name="btnSignon" id="btnSignon" class="ps-btn-primary" data-mrkt-tracking-id="3d6c76ba-9d34-4def-977d-a79cb8afc738" value="Sign On">
<img fetchpriority="high" alt="Enjoy $325" src="https://www17.wellsfargomedia.com/mkt/marketing/digital-containers/images/target/1700x700/4a_hppb_marquee_banner_1700x700.jpg">
<a class="check-rates-wrapper" id="check-rates-wrapper" aria-label="Check rates opens dropdown" role="button" href="#" data-goto="/help/rates/">
<a role="button" data-exit="true" class="ps-button-applestore" aria-label="Download on the App Store opens a dialog" data-href-id="1224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/App_Store_Badge.png" alt=""></a>
<a role="button" data-exit="true" class="ps-button-googleplay" aria-label="Get it on Google Play opens a dialog" data-href-id="3224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/GooglePlay_Badge.png" alt=""></a>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-location contact-bar-location-header" aria-expanded="false">
Showing first 10 of 11 audited elements.
Interactive elements must have a visible focus indicator40 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="#skip" class="hidden">
<a href="/locator/">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">
<a href="/es/" xml:lang="es" id="langPrefToggle" class="spTogglePersonal" name="langPrefToggle" lang="es">
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog.">
<a href="https://connect.secure.wellsfargo.com/auth/login/p..." class="ps-sign-on-text" data-platform="applicationhost" data-host="Login App Host">
<a data-platform="publicsite" href="/" exitdestination="" exitdisclaimer="" data-newbrowser="" enrollmentid="" data-rottracking="" class="" data-params="" data-responsive-params="" data-destinationtype="none" data-nativelinktype="none">
<a href="/checking/" class="">
<a href="/savings-cds/" class="">
<a href="https://creditcards.wellsfargo.com/?sub_channel=WE..." data-platform="creditCardsWF">
Showing first 10 of 40 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination7 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
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<nav class="ps-right-nav" aria-label="Header Navigation">
<nav class="ps-fat-nav-wrapper" aria-label="Main Navigation">
<main class="ps-body-wrapper" style="padding-top: 57px;">
<footer class="ps-footer-homepage">
<nav role="navigation" aria-label="Footer Navigation">
lang attribute must have a valid value12 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
<a href="/es/" xml:lang="es" id="langPrefToggle" class="spTogglePersonal" name="langPrefToggle" lang="es">Español</a>
<div class="marquee-container-wrap iaRendered aem-exo-rendered dispositionElement" data-offer-id="EXO_chk_acq_gro_digcashbonus1549_marquee85" lang="en" data-placement-name="WF_CON_HP_PRIMARY_BNR" data-presentation-order="1" conversation-id="326868-7" source="AEM">
<div class="ps-marketing-small-p..." data-offer-id="CE_chk_acq_gro_start..." lang="en" data-placement-name="WF_CON_HP_SML_PRIMAR..." data-presentation-or...="1" conversation-id="8181fb66-42ba-42f6-a..." source="CEE">
<div class="ps-marketing-small-promo-item iaRendered presentedElement dispositionElement" data-offer-id="CE_ccd_acq_tk1choicehotels_toolbelt" lang="en" data-placement-name="WF_CON_HP_SML_PRIMARY" data-presentation-order="2" conversation-id="903fcef1-7f62-40be-8be5-2dc9158bc3bb-2" source="CEE">
<div class="ps-marketing-small-promo-item iaRendered presentedElement dispositionElement" data-offer-id="CE_ccd_acq_mt_tk1journey_1499_toolbelt" lang="en" data-placement-name="WF_CON_HP_SML_PRIMARY" data-presentation-order="3" conversation-id="9bfb50a1-26df-4efa-8308-e3186114e291-2" ...>
<div class="ps-marketing-small-promo-item presentedElement" lang="en">
<div class="cmsDefault" data-placement-name="WF_CON_HP_LRG_PROMO" data-presentation-order="1" data-placement-presentation-order="WF_CON_HP_LRG_PROMO-1" lang="en" style="display: block !important">
<div class="ps-large-promo-full" lang="en">
<div class="iaRendered enhanced-txt-cm mid-size-promo three-card-content" data-offer-id="CE_oth_lifeevents1578_smallpromo" lang="en" data-placement-name="WF_CON_HP_SML_PROMO" data-presentation-order="1" conversation-id="c43303bc-2fb8-4847-8780-29db054ab9bc-2" source="CEE">
<div class="iaRendered enhanced-txt-cm mid-size-promo three-card-content" data-offer-id="CE_oth_retirement1580alt2_smallpromo" lang="en" data-placement-name="WF_CON_HP_SML_PROMO" data-presentation-order="2" conversation-id="3718efb7-c121-40cf-a7f7-79a3936e9c90-2" source="CEE">
Showing first 10 of 12 audited elements.
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 data-exit="true" aria-label="hyperlink text opens dialogue" target="_blank" data-href-id="13224300702" href="#">SIPC</a>
Links must have discernible text58 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="#skip" class="hidden">Skip to main content</a>
<a href="/locator/">ATMs/Locations</a>
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="/es/" xml:lang="es" id="langPrefToggle" class="spTogglePersonal" name="langPrefToggle" lang="es">Español</a>
<a href="#" class="ps-nxgSearchIcon" id="nxgSearchButton" aria-label="Search, Opens a dialog."> </a>
<a href="https://connect.secure.wellsfargo.com/auth/login/present?origin=cob&LOB=CONS" class="ps-sign-on-text" data-platform="applicationhost" data-host="Login App Host">Sign On</a>
<a data-platform="publicsite" href="/" exitdestination="" exitdisclaimer="" data-newbrowser="" enrollmentid="" data-rottracking="" class="" data-params="" data-responsive-params="" data-destinationtype="none" data-nativelinktype="none">
<a href="/checking/" class="">Checking</a>
<a href="/savings-cds/" class="">Savings & CDs</a>
<a href="https://creditcards.wellsfargo.com/?sub_channel=WEB&vendor_code=WF&linkLoc=FNMC&lang=en" data-platform="creditCardsWF">Credit Cards</a>
Showing first 10 of 58 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 class="ps-body-wrapper" style="padding-top: 57px;">
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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
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 xmlns="http://www.w3.org/1999/xhtml" class="" lang="en">
Required ARIA attributes must be provided12 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div class="ps-emergency-message" role="region" aria-label="Alerts and Notifications"> </div>
<header class="ps-masthead presentedElement" role="banner" data-cid="tcm:84-224274-16" data-ctid="tcm:91-223647-32">
<a href="#" class="ps-masthead-help" role="button" aria-expanded="false">Help</a>
<a href="#" id="password-visible-text" class="show-password password-visible-icon" role="button" aria-label="Show password">Show</a>
<a class="check-rates-wrapper" id="check-rates-wrapper" aria-label="Check rates opens dropdown" role="button" href="#" data-goto="/help/rates/">
<a role="button" data-exit="true" class="ps-button-applestore" aria-label="Download on the App Store opens a dialog" data-href-id="1224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/App_Store_Badge.png" alt=""></a>
<a role="button" data-exit="true" class="ps-button-googleplay" aria-label="Get it on Google Play opens a dialog" data-href-id="3224111702" href="#"><img src="https://www17.wellsfargomedia.com/assets/images/rwd/GooglePlay_Badge.png" alt=""></a>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-location contact-bar-location-header" aria-expanded="false">
<span role="heading" aria-level="3" class="contact-bar-select">Find a location</span>
<a href="#" role="button" tabindex="0" class="contact-bar-collapsible contact-bar-call" aria-expanded="false">
Showing first 10 of 12 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">