Skip to content
https://bankofamerica.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
3
REVIEW
7
PASS
3
INFO
0
Checks
13
3 PASS 7 REVIEW 3 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Main menu" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

B
Heading Hierarchy
50 headings, 1 skip(s)
REVIEW
50 headings, 1 skip(s)
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
Info::
1 hidden heading(s) (aria-hidden)
  • H4 Get the Mobile Banking app
  • H5 Get it on the App Store
  • H5 Or we can text a download link directly to your phone
  • H5 Get it on the App Store
  • H5 Or we can send you a link by email
  • H5 Get it on Google Play
  • H5 Or we can text a download link directly to your phone
  • H5 Our mobile app isn't available for all devices
  • H3 Get the mobile banking app
  • H4 We've sent you a download link
  • H4 We couldn't send the link
  • H1 Menu
  • H1 Do more with the Mobile Banking app duplicate H1
  • H4 Get the Mobile Banking app skipped
  • H5 Get it on the App Store
  • H5 Or we can text a download link directly to your phone
  • H5 Get it on the App Store
  • H5 Or we can send you a link by email
  • H5 Get it on Google Play
  • H5 Or we can text a download link directly to your phone
  • H5 Our mobile app isn't available for all devices
  • H3 Get the mobile banking app
  • H4 We've sent you a download link
  • H4 We couldn't send the link
  • H1 (empty)
  • H1 Security & Help duplicate H1
  • H1 Need help with logging in? duplicate H1
  • H1 Welcome to Online Banking duplicate H1
  • H2 Choose the card that works for you
  • H2 Your financial goals matter
  • H2 Your news and information
  • H3 Level up your account security
  • H3 Convenient banking with our Mobile app
  • H2 Connect with us
  • H1 You're leaving our website duplicate H1
  • H2 Cookie Banner
  • H2 Your Privacy Choices
  • H2 Your Privacy Choices hidden
  • H3 Your Privacy Choices
  • H3 California Notice of Right to Opt-Out from Sale/Sharing
  • H3 Children's Privacy
  • H3 Sharing and Selling of Personal Data
  • H4 Your Privacy Choices
  • H4 Local Privacy Notices and Requirements
  • H4 Marketing Preferences
  • H4 California Residents
  • H4 California Notice of Right to Opt-Out from Sale/Sharing
  • H4 Children's Privacy
  • H4 Sharing and Selling of Personal Data
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Bank of America | Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: only light
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta only light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 30 passed
REVIEW
85

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.column > div.row > div.column > p.card-headline div.column > div.row > div.column > p.card-headline
6% choice category cash back offer div > span.show-for-small-only > a#product1Cta > span.show-for-small-only
div.column > div.row > div.column > p.card-headline div.column > div.row > div.column > p.card-headline
2% unlimited cash back offer div > span.show-for-small-only > a#product2Cta > span.show-for-small-only
div.column > div.row > div.column > p.card-headline div.column > div.row > div.column > p.card-headline
Unlimited 1.5 points for every $1 spent on all purchases div > span.show-for-small-only > a#product3Cta > span.show-for-small-only
div.column > div.row > div.column > p.card-headline div.column > div.row > div.column > p.card-headline
Intro APR offer for 21 billing cycles div > span.show-for-small-only > a#product4Cta > span.show-for-small-only

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEW CHECKING CUSTOMERS Cash offer up to $500 div#depcha2hdda500EnShlCmsCta > div > div.info-box > div.heading
Change the game div#brand0226Fwc26AysAkersEnSHLCta > div > div.info-box > div.heading
6% customized cash back offer div#ca0226CcrHl > div > div.info-box > div.heading
Cash offer up to $500 div#depcha2hdda500EnhlCms > div > div.info-box > div.heading
Custom mobile alerts div#mobileAcquisitionQ1RefreshHl > div > div.info-box > div.heading

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.carousel__content > div.content--wrapper > a#bmhDefaultCreditDebt > img.icon

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AdChoices li > span.gt-footer--nowrap > span > button#footer_bofa_advetising_practices

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Alt Text Quality
1 of 68 images have issues
PASS
1 of 68 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with alt text over 125 characters
Info::
36 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
68 images 30 good alt text 36 decorative 1 missing
IssueCount
missing1 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Accessibility
All 20 controls labeled
PASS
All 20 controls labeled
Info::
20 control(s) properly labeled
20 controls
20 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#nav-search-querytextSearchfor/id
#getAppDeviceSelectselectSelect Your Device *for/id
#phoneNumberFieldiPhonetextPhone Number * In 999-999-9999 Formatfor/id
#emailAddressFieldemailEmail Address *for/id
#phoneNumberFieldAndroidtextPhone Number * In 999-999-9999 Formatfor/id
#getAppDeviceSelectselectSelect Your Device *for/id
#phoneNumberFieldiPhonetextPhone Number * In 999-999-9999 Formatfor/id
#emailAddressFieldemailEmail Address *for/id
#phoneNumberFieldAndroidtextPhone Number * In 999-999-9999 Formatfor/id
#oidtextUser ID *for/id
#prefill-oidselectUser IDfor/id
#passpasswordPassword *for/id
#saveOnlineIDcheckboxSave user ID⁠⁠for/id
#tmt-selectselectTake me tofor/id
#ot-group-id-CCBAcheckboxSharing and Selling of Personal Datafor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Do more with the Mob…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Security & Help21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Need help with loggi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Welcome to Online Ba…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 You're leaving our w…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Choose the card that…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your financial goals…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your news and inform…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cookie Banner21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Privacy Choices21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Privacy Choices21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get the mobile banki…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get the mobile banki…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Level up your accoun…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Convenient banking w…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Privacy Choices21.00:13.0:1
#000000
#FFFFFF
Pass
h3 California Notice of…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Children's Privacy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sharing and Selling …21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback