Bank of America bankofamerica.com
Accessibility score
League position
7thof 10
Issues found
6
Audits passed
49
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalElements must only use supported ARIA attributes1 element
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.
Failing Elements
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
SeriousElements must meet minimum color contrast ratio thresholds3 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.
Failing Elements
<div class="heading">6% customized<br>cash back offer</div>
Fix any of the following:
- Element has insufficient color contrast of 4.32 (foreground color: #e31837, background color: #f5f5f5, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="heading">Cash offer up to $500</div>
Fix any of the following:
- Element has insufficient color contrast of 4.32 (foreground color: #e31837, background color: #f5f5f5, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="heading">Custom mobile alerts</div>
Fix any of the following:
- Element has insufficient color contrast of 4.32 (foreground color: #e31837, background color: #f5f5f5, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<nav class="spa-tab__control-wrapper" aria-label="main">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateAll page content should be contained by landmarks42 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<div id="fdicConsumer">
Fix any of the following:
- Some page content is not contained by landmarks
<div id="gt-nav-unauth-main-module" class="gt-nav-unauth-main-wrapper">
Fix any of the following:
- Some page content is not contained by landmarks
<label class="spa-input-label" for="nav-search-query"> <span class="ada-hidden"> Search </span> </label>
Fix any of the following:
- Some page content is not contained by landmarks
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Fix any of the following:
- Some page content is not contained by landmarks
<label class="spa-input-label" for="oid"> User ID<span class="spa-input-label--asterisk"> *</span> <span class="ada-hidden"> </span> </label>
Fix any of the following:
- Some page content is not contained by landmarks
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Fix any of the following:
- Some page content is not contained by landmarks
<label class="spa-input-label" for="pass"> Password<span class="spa-input-label--asterisk"> *</span> <span class="ada-hidden"> </span> </label>
Fix any of the following:
- Some page content is not contained by landmarks
<input type="password" aria-describedby="pass_errorMessage pa..." data-mobile-input-ty...="password" data-default-input-t...="password" data-android-input-t...="password" data-mobile-pattern="" data-default-pattern="" class="spa-input-text" autocomplete="off" data-gis-mask="false" id="pass" ...>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="spa-input-options-wrapper">
Fix any of the following:
- Some page content is not contained by landmarks
<div id="footer-links-section" class="footer-links">
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 42 failing elements.
MinorARIA role should be appropriate for the element8 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.
Failing Elements
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-q2-CSXb35d6c2d.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_4953168_icon_gc_d-CSX7684a6de.svg" alt=" " role="presentation">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-new-CSX71f0a17b.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_3782311_icon_gc_c-CSX182beee.svg" alt=" " role="presentation">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-3-q2-CSX872fbcfc.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_7701865_icon_gc_c-CSX55809c59.svg" alt=" " role="presentation">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-4-new-CSX88717b40.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Fix any of the following:
- ARIA role presentation is not allowed for given element
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_3782311_icon_gc_a-CSXe06a7caa.svg" alt=" " role="presentation">
Fix any of the following:
- ARIA role presentation is not allowed for given element
MinorHeadings should not be empty1 element
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.
Failing Elements
<h1></h1>
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
Passed audits49 across 1 page
[role="img"] and [role="image"] elements must have alternative text1 element
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<div class="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<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-US" layoutversion="">
<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-US" layoutversion="">
<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 class="spa-tab__tab-list-item spa-tab__panel-wrapper"><a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a><!----></li>
<li class="spa-tab__tab-list-item spa-tab__panel-wrapper"><a class="spa-tab__tab-element" id="tab-topnav_wealth_management_id" href="https://www.ml.com/wealthmanagement.html"><span>Wealth Management</span><!----><!----></a><!----></li>
<li class="spa-tab__tab-list-item spa-tab__panel-wrapper"><a class="spa-tab__tab-element" id="tab-topnav_business_id" href="https://www.bankofamerica.com/business"><span>Business</span><!----><!----></a><!----></li>
<li class="spa-tab__tab-list-item spa-tab__panel-wrapper"><a class="spa-tab__tab-element" id="tab-topnav_corporations_institutions_id" href="https://business.bofa.com/content/boaml/en_us/home.html"><span>Corporations & Institutions</span><!----><!----></a><!----></li>
<li class="spa-tab__tab-list-item spa-tab__panel-wrapper"><a class="spa-tab__tab-element" id="tab-topnav_security_id" href="https://www.bankofamerica.com/security-center/overview/"><span>Security</span><!----><!----></a><!----></li>
Showing first 5 of 41 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements3 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 class="show-for-large-up" id="bmhLarge">
<ul class="footer-links">
<ul>
All page content should be contained by landmarks594 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div data-sparta-container="homepage" data-page-level-content-state="DISABLED" class="flex-grid-nest spa-contextroot-homepage spa-site-homepage">
<a class="ada-hidden ada-visible-focus" href="#mastheadContainerModule" id="ada-skip-link">Skip to main content</a>
<div class="spa-layout-container spa-layout-container--flex-grid-nest">
<div data-component="layout" data-layout="@sparta.global-tenants.templates/gt-unauth-bofa-site-template" data-version="" class="sparta-layout flex-grid-layout" id="top">
<div name="siteTemplateLayout"></div>
Showing first 5 of 594 audited elements.
Alternative text of images should not be repeated as text12 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://secure2.bac-assets.com/spa/widgets/gt-nav-unauth-secure-bofa-widget/1.0.0/spa-assets/images/assets-images-global-fdic-fdic-digital-sign-CSX37f66a3e.svg" alt="FDIC-Insured - Backed by the full faith and credit of the U.S. Government" class="fdic-digital-sign">
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="A map location marker">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-q2-CSXb35d6c2d.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_4953168_icon_gc_d-CSX7684a6de.svg" alt=" " role="presentation">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-new-CSX71f0a17b.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Showing first 5 of 12 audited elements.
ARIA attributes must be used as specified for the element's role34 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<nav class="spa-tab__control-wrapper" aria-label="main">
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<nav class="spa-tab__control-wrapper" aria-label="main">
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Showing first 5 of 34 audited elements.
ARIA attributes must conform to valid names34 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<nav class="spa-tab__control-wrapper" aria-label="main">
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<nav class="spa-tab__control-wrapper" aria-label="main">
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Showing first 5 of 34 audited elements.
ARIA attributes must conform to valid values34 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<nav class="spa-tab__control-wrapper" aria-label="main">
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<nav class="spa-tab__control-wrapper" aria-label="main">
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Showing first 5 of 34 audited elements.
ARIA commands must have an accessible name1 element
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
<span role="button" class="spa-btn spa-btn--primary spa-btn--medium masthead-cta-btn">Let's talk<span class="ada-hidden"> Click let's talk to learn more about a new center near you.</span></span>
ARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Audit Elements
<div role="dialog" aria-label="Cookie Banner ">
ARIA hidden element must not be focusable or contain focusable elements82 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
<button type="button" class="spa-tab__control spa-tab__control--hidden spa-tab spa-tab__control--prev" tabindex="-1" aria-hidden="true" data-tab-control-speed="20" data-tab-control-increment="25" aria-label="Slide left">
<button type="button" class="spa-tab__control spa-tab__control--hidden spa-tab spa-tab__control--next" tabindex="-1" aria-hidden="true" data-tab-control-speed="20" data-tab-control-increment="25" aria-label="Slide right">
<button type="button" class="spa-tab__control spa-tab__control--hidden spa-tab spa-tab__control--prev" tabindex="-1" aria-hidden="true" data-tab-control-speed="20" data-tab-control-increment="25" aria-label="Slide left">
<button type="button" class="spa-tab__control spa-tab__control--hidden spa-tab spa-tab__control--next" tabindex="-1" aria-hidden="true" data-tab-control-speed="20" data-tab-control-increment="25" aria-label="Slide right">
<div class="spa-input-error-message spa-icon--error" id="nav-search-query_errorMessage" aria-hidden="true"></div>
Showing first 5 of 82 audited elements.
ARIA role should be appropriate for the element68 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<span id="global-search-input-close-link" class="spa-icon icon-close" tabindex="0" role="button" style="display: none;">
<span class="ada-hidden">clear search text</span>
</span><svg xmlns="http://www.w3.org/2000/svg" width="24px" height="24px" role="img" viewBox="0 0 24 24" focusable="false" aria-hidden="true">
Showing first 5 of 68 audited elements.
ARIA roles used must conform to valid values22 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<span role="button" class="spa-btn spa-btn--primary spa-btn--medium masthead-cta-btn">Let's talk<span class="ada-hidden"> Click let's talk to learn more about a new center near you.</span></span>
Showing first 5 of 22 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 data-sparta-version="6.9.2" data-build-id="303833" data-sparta-wrapper="homepage" class="xsmall small xsmall-up small-up smallMid smallMid-up smallPlus smallPlus-up medium medium-up large large-up large-only landscape standard" data-detectedprerender="false" style="visibility: visible;">
autocomplete attribute must be used correctly3 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" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="password" aria-describedby="pass_errorMessage pa..." data-mobile-input-ty...="password" data-default-input-t...="password" data-android-input-t...="password" data-mobile-pattern="" data-default-pattern="" class="spa-input-text" autocomplete="off" data-gis-mask="false" id="pass" ...>
Buttons must have discernible text14 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 type="button" class="spa-circle-btn-wrapper submit track-me spa-global-search-btn " id="global-search-button" firstclick="true" aria-expanded="false" aria-label="search icon" data-bactmln="global-search-button" name="global-search-button">
<button class="spa-tab__tab-element" id="tab-checking_id" type="button" aria-expanded="false">
<button class="spa-tab__tab-element" id="tab-savings_and_CDs_id" type="button" aria-expanded="false">
<button class="spa-tab__tab-element" id="tab-credit_cards_id" type="button" aria-expanded="false">
<button class="spa-tab__tab-element" id="tab-home_loans_id" type="button" aria-expanded="false">
Showing first 5 of 14 audited elements.
Certain ARIA roles must be contained by particular parents6 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="gt-footer__box-item" role="listitem">Are Not FDIC Insured</li>
<li class="gt-footer__box-item" role="listitem">Are Not Bank Guaranteed</li>
<li class="gt-footer__box-item" role="listitem">May Lose Value</li>
<li class="gt-footer__box-item" role="listitem">Are Not Deposits</li>
<li class="gt-footer__box-item" role="listitem">Are Not Insured by Any Federal Government Agency</li>
Showing first 5 of 6 audited elements.
Certain ARIA roles must contain particular children4 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="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="gt-footer__box-container" role="list">
Content must reflow without two-dimensional scrolling1 element
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="column large-8 large-push-4 small-12 small-push-1 ...">
Deprecated ARIA roles must not be used22 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<span role="button" class="spa-btn spa-btn--primary spa-btn--medium masthead-cta-btn">Let's talk<span class="ada-hidden"> Click let's talk to learn more about a new center near you.</span></span>
Showing first 5 of 22 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-US" layoutversion="">
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>
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-US" layoutversion="">
Elements marked as presentational should be consistently ignored10 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://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-q2-CSXb35d6c2d.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_4953168_icon_gc_d-CSX7684a6de.svg" alt=" " role="presentation">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-new-CSX71f0a17b.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_3782311_icon_gc_c-CSX182beee.svg" alt=" " role="presentation">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-3-q2-CSX872fbcfc.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Showing first 5 of 10 audited elements.
Elements must meet minimum color contrast ratio thresholds94 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
<span class="text-preamble">Bank of America deposit products: </span>
<select id="getAppDeviceSelect" name="getAppDeviceSelect" noemptyoption="true" autocomplete="off" class="spa-input-select" value="" data-val="" required="" aria-required="true" aria-invalid="false" aria-describedby="getAppDeviceSelect_errorMessage">
<input type="text" aria-describedby="phoneNumberFieldiPho..." pattern="^\d{3}-\d{3}-\d{4}$" data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="tel" data-mobile-pattern="^\d{3}-\d{3}-\d{4}$" data-default-pattern="^\d{3}-\d{3}-\d{4}$" autocomplete="off" ...><input type="email" aria-describedby="emailAddressField_er..." data-mobile-input-ty...="email" data-default-input-t...="email" data-android-input-t...="email" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="email" autocorrect="off" autocapitalize="off" autocomplete="off" ...>
<input type="text" aria-describedby="phoneNumberFieldAndr..." pattern="^\d{3}-\d{3}-\d{4}$" data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="tel" data-mobile-pattern="^\d{3}-\d{3}-\d{4}$" data-default-pattern="^\d{3}-\d{3}-\d{4}$" autocomplete="off" ...>Showing first 5 of 94 audited elements.
Elements must only use permitted ARIA attributes34 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<nav class="spa-tab__control-wrapper" aria-label="main">
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<nav class="spa-tab__control-wrapper" aria-label="main">
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
Showing first 5 of 34 audited elements.
Elements must only use supported ARIA attributes33 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<nav class="spa-tab__control-wrapper" aria-label="main">
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<nav class="spa-tab__control-wrapper" aria-label="main">
<button type="button" class="spa-circle-btn-wrapper submit track-me spa-global-search-btn " id="global-search-button" firstclick="true" aria-expanded="false" aria-label="search icon" data-bactmln="global-search-button" name="global-search-button">
Showing first 5 of 33 audited elements.
Elements should not have tabindex greater than zero7 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 id="ah-first-factor-error-container" class="columns large-12" tabindex="-1" aria-live="polite"> </div>
<div id="mastheadPartialContent" class="partial-container standard" data-update-container="masthead-update-container" tabindex="-1" data-ad-container="BOA_HOME_SIGNON_BANNER">
<div id="engagementBannerPartialContent" class="banner-partial-container banner-icon-text-link" tabindex="-1" data-ad-container="BOA_HOME_SIGNON_ENGAGEMENTBANNER">
<div class="spa-card spa-card--medium block spa-card--clickable spa-card--overlay spa-card__dismissible--none" data-clickable-target="appointmentLink" tabindex="-1">
<div class="spa-card spa-card--medium block spa-card--clickable spa-card--overlay spa-card__dismissible--none" data-clickable-target="findLocation" tabindex="-1">
Showing first 5 of 7 audited elements.
Focused elements must not be entirely hidden by author-created content2 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a href="https://web.bankofamerica.com/en/privacy" target="_blank">
<button class="onetrust-close-btn-handler onetrust-close-btn-ui b..." aria-label="Close" style="background-image: url("https://cdn.cookielaw....">
Form elements must have labels4 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" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="password" aria-describedby="pass_errorMessage pa..." data-mobile-input-ty...="password" data-default-input-t...="password" data-android-input-t...="password" data-mobile-pattern="" data-default-pattern="" class="spa-input-text" autocomplete="off" data-gis-mask="false" id="pass" ...>
<input type="checkbox" aria-describedby="saveOnlineID_errorMessage saveOnlineID-hint-text" id="saveOnlineID" name="saveOnlineID" value="1" class="spa-input-option spa-input-option--checkbox">
Form elements should have a visible label4 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" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="password" aria-describedby="pass_errorMessage pa..." data-mobile-input-ty...="password" data-default-input-t...="password" data-android-input-t...="password" data-mobile-pattern="" data-default-pattern="" class="spa-input-text" autocomplete="off" data-gis-mask="false" id="pass" ...>
<input type="checkbox" aria-describedby="saveOnlineID_errorMessage saveOnlineID-hint-text" id="saveOnlineID" name="saveOnlineID" value="1" class="spa-input-option spa-input-option--checkbox">
Form field must not have multiple label elements4 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" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<input type="password" aria-describedby="pass_errorMessage pa..." data-mobile-input-ty...="password" data-default-input-t...="password" data-android-input-t...="password" data-mobile-pattern="" data-default-pattern="" class="spa-input-text" autocomplete="off" data-gis-mask="false" id="pass" ...>
<input type="checkbox" aria-describedby="saveOnlineID_errorMessage saveOnlineID-hint-text" id="saveOnlineID" name="saveOnlineID" value="1" class="spa-input-option spa-input-option--checkbox">
Heading levels should only increase by one8 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></h1>
<h2 class="cnx-regular headline ">
A new financial center in your neighborhood
</h2><h2>Your financial goals matter</h2>
<h2 class="heading main">Your news and information</h2>
<h3 class="heading upper">Level up your account security</h3>
Showing first 5 of 8 audited elements.
Headings should not be empty7 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
<h2 class="cnx-regular headline ">
A new financial center in your neighborhood
</h2><h2>Your financial goals matter</h2>
<h2 class="heading main">Your news and information</h2>
<h3 class="heading upper">Level up your account security</h3>
<h3 class="heading lower">Convenient banking with our Mobile app</h3>
Showing first 5 of 7 audited elements.
IDs used in ARIA and labels must be unique47 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
<input type="text" aria-describedby="nav-search-query_err..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<p id="nav-search-query-hint-text" class="spa-input-hint"></p>
<div class="spa-input-error-message spa-icon--error" id="nav-search-query_errorMessage" aria-hidden="true"></div>
<input type="text" aria-describedby="oid_errorMessage oid..." data-mobile-input-ty...="text" data-default-input-t...="text" data-android-input-t...="text" data-mobile-pattern="" data-default-pattern="" data-sparta-input-fo...="name" autocorrect="off" class="spa-input-text" autocomplete="off" ...>
<p id="oid-hint-text" class="spa-input-hint"></p>
Showing first 5 of 47 audited elements.
Images must have alternative text12 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://secure2.bac-assets.com/spa/widgets/gt-nav-unauth-secure-bofa-widget/1.0.0/spa-assets/images/assets-images-global-fdic-fdic-digital-sign-CSX37f66a3e.svg" alt="FDIC-Insured - Backed by the full faith and credit of the U.S. Government" class="fdic-digital-sign">
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="A map location marker">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-q2-CSXb35d6c2d.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
<img class="icon" src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-icons-ent_edu_bac_4953168_icon_gc_d-CSX7684a6de.svg" alt=" " role="presentation">
<img src="https://www2.bac-assets.com/homepage/spa-assets/images/assets-images-site-homepage-bmh-module-default-education-bac-edu-tile-319x363-desktop-1-new-CSX71f0a17b.jpg" alt=" " role="presentation" class="bmh-tile-image" loading="lazy">
Showing first 5 of 12 audited elements.
Inline text spacing must be adjustable with custom stylesheets11 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
<body data-sparta-version="6.9.2" data-build-id="303833" data-sparta-wrapper="homepage" class="xsmall small xsmall-up small-up smallMid smallMid-up smallPlus smallPlus-up medium medium-up large large-up large-only landscape standard" data-detectedprerender="false" style="visibility: visible;">
<div id="gt-nav-unauth-widget-container" class="sparta-widget-loader-v6" style="height: auto; visibility: visible;">
<div class="sparta-widget-contai..." data-version="1.0.0" data-sparta-containe...="gt-nav-unauth-secure..." data-sparta-widget="" data-sparta-lang="en-US" data-page-level-cont...="DISABLED" data-sparta-options="{"jcrData":{},"witho..." style="visibility: visible;"><div id="searchContainer" class="gt-nav-unauth-bofa-search" style="display: block;">
<div id="gt-unauth-header-nav-space" class="gt-unauth-nav-space" style="height: 0px;"></div>
Showing first 5 of 11 audited elements.
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 src="https://secure2.bac-assets.com/spa/widgets/gt-nav-unauth-secure-bofa-widget/1.0.0/spa-assets/images/assets-images-global-fdic-fdic-digital-sign-CSX37f66a3e.svg" alt="FDIC-Insured - Backed by the full faith and credit of the U.S. Government" class="fdic-digital-sign">
<div class="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<button type="button" class="spa-circle-btn-wrapper submit track-me spa-global-search-btn " id="global-search-button" firstclick="true" aria-expanded="false" aria-label="search icon" data-bactmln="global-search-button" name="global-search-button">
<button class="spa-tab__tab-element" id="tab-checking_id" type="button" aria-expanded="false">
<button class="spa-tab__tab-element" id="tab-savings_and_CDs_id" type="button" aria-expanded="false">
Showing first 5 of 20 audited elements.
Interactive elements must have a visible focus indicator2 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a href="https://web.bankofamerica.com/en/privacy" target="_blank">
<button class="onetrust-close-btn-handler onetrust-close-btn-ui b..." aria-label="Close" style="background-image: url("https://cdn.cookielaw....">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<nav aria-label="Footer">
Links must be distinguishable without relying on color3 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a class="spa-ui-layer-link sp..." data-bactmtrack="" data-options="{"interstitialType":..." id="footer_sipc" href="http://www.sipc.org/" data-bactmln="Footer-_-Hyperlink-_..."><a class="spa-fn spa-boa-windo..." id="equalHousingLender" href="https://www.bankofam..." data-options="{"menubar":true,"scr..." data-popup-event-att...="true" data-bactmln="Footer-_-Hyperlink-_..."><a href="https://web.bankofamerica.com/en/privacy" target="_blank">Privacy Notices</a>
Links must have discernible text56 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 class="ada-hidden ada-visible-focus" href="#mastheadContainerModule" id="ada-skip-link">Skip to main content</a>
<a class="spa-tab__tab-element unauth-personal-tab" id="tab-topnav_personal_id" href="#" aria-label="Personal Selected "><span>Personal</span><!----><!----></a>
<a class="spa-tab__tab-element" id="tab-topnav_wealth_management_id" href="https://www.ml.com/wealthmanagement.html"><span>Wealth Management</span><!----><!----></a>
<a class="spa-tab__tab-element" id="tab-topnav_business_id" href="https://www.bankofamerica.com/business"><span>Business</span><!----><!----></a>
<a class="spa-tab__tab-element" id="tab-topnav_corporations_institutions_id" href="https://business.bofa.com/content/boaml/en_us/home.html"><span>Corporations & Institutions</span><!----><!----></a>
Showing first 5 of 56 audited elements.
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en-US" layoutversion="">
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-US" layoutversion="">
Required ARIA attributes must be provided22 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="gtnav-logo-img " role="img" aria-label="Bank of America"></div>
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<ul class="spa-tab__tab-wrapper" role="list">
<span role="button" class="spa-btn spa-btn--primary spa-btn--medium masthead-cta-btn">Let's talk<span class="ada-hidden"> Click let's talk to learn more about a new center near you.</span></span>
Showing first 5 of 22 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">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width,initial-scale=1">
How does your site stack up against Bank of America?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Banking & Finance
- HSBC95 out of 100, good
- Charles Schwab85 out of 100, needs improvement
- Wells Fargo85 out of 100, needs improvement
- Chase75 out of 100, needs improvement
- Citibank75 out of 100, needs improvement
- Fidelity75 out of 100, needs improvement
- Capital One70 out of 100, needs improvement
- Barclays55 out of 100, poor
- PayPal30 out of 100, poor