Skip to content
https://wellsfargo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
5
REVIEW
1
PASS
7
INFO
0
Checks
13
7 PASS 1 REVIEW 5 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
Dark Mode Support
Action
Theme color only
FIX
Theme color only
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: #f9f7f6
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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.
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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
A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Header Navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H2 How can we help?
  • H2 Popular FAQs
  • H3 BANKING SERVICES
  • H3 DIGITAL BANKING
  • H3 BANKING SERVICES
  • H3 DIGITAL BANKING
  • H3 CREDIT CARD SERVICES
  • H3 EDUCATION & TOOLS
  • H3 MORTGAGE SERVICES
  • H3 EDUCATION & TOOLS
  • H3 PERSONAL LOAN SERVICES
  • H3 EDUCATION & TOOLS
  • H3 AUTO LOAN SERVICES
  • H3 EDUCATION & TOOLS
  • H3 BANKING SERVICES
  • H3 DIGITAL BANKING
  • H1 Wells Fargo
  • H2 Good evening
  • H2 Checking that fits perfectly
  • H2 Find mortgage happiness
  • H2 Check all the boxes on checking
  • H2 Find a credit card
  • H2 Interest rates today
  • H2 A home of your own
  • H2 Financial guidance and support
  • H3 Your dreams, your plan
  • H3 Borrowing built around you
  • H3 Your shield against scams
  • H2 Need help? Ask Fargo®
  • H2 Need help? Ask Fargo®
  • H2 Serving our customers and communities
  • H3 Who we are
  • H3 Why we're committed to communities
  • H2 How can we help?
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
11 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
15 images 4 good alt text 11 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="btnSignon" id="btnSignon">
Info::
6 control(s) properly labeled
7 controls
6 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#supportDropDownLocatortextCity, State or ZIParia-label
#useridtextUsernamefor/id
#passwordpasswordPasswordfor/id
#saveusernamecheckboxSave username Notice - For your security, we do not recommend using this feature on a shared device.for/id
#check_rates_dropdownselectCheck ratesaria-label
#contactBarLocatortextCity, State or ZIParia-label
#btnSignonsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="btnSignon" id="btnSignon">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Wells Fargo - Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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 Wells Fargo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How can we help?18.53:13.0:1
#000000
#F4F0ED
Pass
h2 Popular FAQs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Good evening21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Checking that fits p…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find mortgage happin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Check all the boxes …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find a credit card21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Interest rates today21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A home of your own21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Financial guidance a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Need help? Ask Fargo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Need help? Ask Fargo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Serving our customer…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How can we help?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 BANKING SERVICES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DIGITAL BANKING21.00:13.0:1
#000000
#FFFFFF
Pass
h3 BANKING SERVICES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DIGITAL BANKING21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CREDIT CARD SERVICES21.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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 28 passed
PASS
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more div.ps-promo-full-item > div.ps-promo-full-content > div.ps-promo-full-links > a.ps-btn-secondary
SIPC div.ps-footer-wrapper > div.ps-footnote-text > p > a
○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○ARIA IDs are unique
○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
○Form elements have associated labels
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback