Citibank citibank.com
Accessibility score
League position
4thof 10
Issues found
2
Audits passed
48
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousContent must reflow without two-dimensional scrolling2 elements
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.
Failing Elements
<div _ngcontent-ssr-c1590736564="" class="journeyLogo">
<div _ngcontent-ssr-c739218679="" id="navigationRight">
ModeratePage 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.
Failing Elements
<html class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
Fix all of the following:
- Page must have a level-one heading
Passed audits48 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 _ngcontent-ssr-c4105219706="" role="img" alt="icon" aria-label="show" class="medium" style="width: 20px; height: 20px;">
<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 class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
<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 class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul _ngcontent-ssr-c739218679="" class="nav-bar-main-ul" style="display: flex; position: static;">
All page content should be contained by landmarks373 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
<app-root ng-version="21.2.19" ng-server-context="ssr">
<cbol-core>
<citi-parent-layout _nghost-ssr-c3213358437="" class="ng-tns-c3213358437-0">
<div _ngcontent-ssr-c3213358437="" class="ng-tns-c3213358437-0 citi-outer-container cbolui-cds">
<citi-header _ngcontent-ssr-c3213358437="" class="ng-tns-c3213358437-0" _nghost-ssr-c2855406740="">
Showing first 5 of 373 audited elements.
Alternative text of images should not be repeated as text9 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 _ngcontent-ssr-c1590736564="" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/citiredesign.svg" alt="Citi" class="ng-star-inserted">
<img _ngcontent-ssr-c1590736564="" alt="Citi FDIC Insured" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Banner_v2.svg" id="fdicLogoA" class="ng-star-inserted">
<img _ngcontent-ssr-c2067562431="" class="product-image PIL_HP22" alt="Manage the Unexpected with a Loan " src="https://aemapi.citi.com/content/dam/cfs/uspb/usmkt/cbol-homepage/en/banners/images/PIL_HP22_Hero.png">
<img _ngcontent-ssr-c4306...="" class="img-responsive HP26_..." alt="A mortgage that work..." data-expand="10" data-src="https://aemapi.citi...." src="https://aemapi.citi....">
<img _ngcontent-ssr-c4306...="" class="img-responsive HP23_..." alt="Save More, Earn More..." data-expand="10" data-src="https://aemapi.citi...." src="https://aemapi.citi....">
Showing first 5 of 9 audited elements.
ARIA attributes must be used as specified for the element's role28 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
<a _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 28 audited elements.
ARIA attributes must conform to valid names28 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
<a _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 28 audited elements.
ARIA attributes must conform to valid values28 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
<a _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 28 audited elements.
ARIA commands must have an accessible name5 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navbankingmainAnchor1" role="button" aria-expanded="false">Banking</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navlendingmainAnchor2" role="button" aria-expanded="false">Lending</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="investingmainAnchor3" role="button" aria-expanded="false">Investing</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="wealthMgmntmainAnchor4" role="button" aria-expanded="false">Wealth Management</a>
ARIA hidden element must not be focusable or contain focusable elements38 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
<img _ngcontent-ssr-c1590736564="" aria-hidden="true" alt="" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Banner_v2.svg">
<img _ngcontent-ssr-c1590736564="" aria-hidden="true" alt="" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Banner_v2.svg">
<img _ngcontent-ssr-c3004274504="" aria-hidden="true" alt="Citi<sup id='reg' aria-hidden='true'>&reg;</sup> Credit Knowledge Center" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Nav_v3.svg" class="ktCenter">
<sup aria-hidden="true">®</sup>
<img _ngcontent-ssr-c3004274504="" aria-hidden="true" alt="Respond to Mail Offer" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Nav_v3.svg" class="mailOffer">
Showing first 5 of 38 audited elements.
ARIA role should be appropriate for the element96 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 _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navcreditCardMainLI">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 96 audited elements.
ARIA roles used must conform to valid values20 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 _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navcreditCardMainLI">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 20 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="">
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
<div _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
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 _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<button _ngcontent-ssr-c739218679="" type="button" name="how can we help button" class="main-links topNavButton howCanWeHelpButton en_US ng-star-inserted"> How can we help? </button>
<button _ngcontent-ssr-c2067562431="" cdscta="primary" customertype="priority" size="large" class="cds-cta px-lg-4 px-xl-5 px-xxl-5 PIL_HP22 cds-cta-lg cds-cta-primary cds-cta-priority" aria-label="Check My Rate: CITI® PERSONAL LOAN ">
<button _ngcontent-ssr-c2067562431="" id="pdpBypassSecondaryCTA" cdscta="tertiary" class="cds-cta text-nowrap cds-cta-md cds-cta-tertiary ng-star-inserted" aria-label="Learn More: CITI® PERSONAL LOAN ">
<button _ngcontent-ssr-c756295117="" type="button" class="cds-input-button cds-input-button-primary" tabindex="0" aria-label="show">
Showing first 5 of 14 audited elements.
Certain ARIA roles must be contained by particular parents8 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 _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navcreditCardMainLI">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navbankingMainLI">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navlendingMainLI">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="investingMainLI">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="wealthMgmntMainLI">
Showing first 5 of 8 audited elements.
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
<div _ngcontent-ssr-c3517354859="" role="contentinfo" class="footer ng-star-inserted"><!----><!----><div _ngcontent-ssr-c3517354859="" style="height: 814px;" class="ng-star-inserted"></div><!----></div>
Deprecated ARIA roles must not be used20 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 _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navcreditCardMainLI">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 20 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 class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
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
<div _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
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
<div _ngcontent-ssr-c3517354859="" role="contentinfo" class="footer ng-star-inserted"><!----><!----><div _ngcontent-ssr-c3517354859="" style="height: 814px;" class="ng-star-inserted"></div><!----></div>
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
<div _ngcontent-ssr-c3209448095="" role="main">
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 class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
Elements must meet minimum color contrast ratio thresholds54 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 _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<span _ngcontent-ssr-c1590736564="">ATM / BRANCH</span>
<span _ngcontent-ssr-c1590736564="" lang="es">ESPAÑOL</span>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navbankingmainAnchor1" role="button" aria-expanded="false">Banking</a>
Showing first 5 of 54 audited elements.
Elements must only use permitted ARIA attributes28 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
<a _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 28 audited elements.
Elements must only use supported ARIA attributes28 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
<a _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 28 audited elements.
Elements should not have tabindex greater than zero12 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 _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navbankingmainAnchor1" role="button" aria-expanded="false">Banking</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navlendingmainAnchor2" role="button" aria-expanded="false">Lending</a>
Showing first 5 of 12 audited elements.
Focused elements must not be entirely hidden by author-created content44 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 _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<a _ngcontent-ssr-c1590736564="" id="atmLink" href="/citibank-location-finder" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
Showing first 5 of 44 audited elements.
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 _ngcontent-ssr-c1530547397="" cdsinput="" type="text" formcontrolname="username" class="cds-input cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" maxlength="50" id="username">
<input _ngcontent-ssr-c1530547397="" cdsinput="" formcontrolname="password" class="cds-input form-control cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" type="password" maxlength="256" id="password" style="padding-right: 64px;">
<input _ngcontent-ssr-c1705620111="" type="checkbox" class="cds-checkbox2-input" value="accepted" id="cds-checkbox2-0" name="remember" aria-describedby="cds-checkbox2-0-desc">
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 _ngcontent-ssr-c1530547397="" cdsinput="" type="text" formcontrolname="username" class="cds-input cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" maxlength="50" id="username">
<input _ngcontent-ssr-c1530547397="" cdsinput="" formcontrolname="password" class="cds-input form-control cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" type="password" maxlength="256" id="password" style="padding-right: 64px;">
<input _ngcontent-ssr-c1705620111="" type="checkbox" class="cds-checkbox2-input" value="accepted" id="cds-checkbox2-0" name="remember" aria-describedby="cds-checkbox2-0-desc">
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 _ngcontent-ssr-c1530547397="" cdsinput="" type="text" formcontrolname="username" class="cds-input cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" maxlength="50" id="username">
<input _ngcontent-ssr-c1530547397="" cdsinput="" formcontrolname="password" class="cds-input form-control cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" type="password" maxlength="256" id="password" style="padding-right: 64px;">
<input _ngcontent-ssr-c1705620111="" type="checkbox" class="cds-checkbox2-input" value="accepted" id="cds-checkbox2-0" name="remember" aria-describedby="cds-checkbox2-0-desc">
Heading levels should only increase by one6 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
<h2 _ngcontent-ssr-c2182770282="" class="headline">A mortgage that works for you </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">Save More, Earn More </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">20,000 bonus points </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">Earn 15,000 AAdvantage<sup>®</sup> Bonus Miles</h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline"><strong>Great for Balance Transfers</strong> </h2>
Showing first 5 of 6 audited elements.
Headings should not be empty6 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 _ngcontent-ssr-c2182770282="" class="headline">A mortgage that works for you </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">Save More, Earn More </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">20,000 bonus points </h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline">Earn 15,000 AAdvantage<sup>®</sup> Bonus Miles</h2>
<h2 _ngcontent-ssr-c2182770282="" class="headline"><strong>Great for Balance Transfers</strong> </h2>
Showing first 5 of 6 audited elements.
IDs used in ARIA and labels must be unique4 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 _ngcontent-ssr-c1530547397="" cdsinput="" type="text" formcontrolname="username" class="cds-input cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" maxlength="50" id="username">
<input _ngcontent-ssr-c1530547397="" cdsinput="" formcontrolname="password" class="cds-input form-control cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" type="password" maxlength="256" id="password" style="padding-right: 64px;">
<input _ngcontent-ssr-c1705620111="" type="checkbox" class="cds-checkbox2-input" value="accepted" id="cds-checkbox2-0" name="remember" aria-describedby="cds-checkbox2-0-desc">
<div _ngcontent-ssr-c1705620111="" class="cds-checkbox2-description" id="cds-checkbox2-0-desc"></div>
Images must have alternative text9 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 _ngcontent-ssr-c1590736564="" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/citiredesign.svg" alt="Citi" class="ng-star-inserted">
<img _ngcontent-ssr-c1590736564="" alt="Citi FDIC Insured" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Banner_v2.svg" id="fdicLogoA" class="ng-star-inserted">
<img _ngcontent-ssr-c2067562431="" class="product-image PIL_HP22" alt="Manage the Unexpected with a Loan " src="https://aemapi.citi.com/content/dam/cfs/uspb/usmkt/cbol-homepage/en/banners/images/PIL_HP22_Hero.png">
<img _ngcontent-ssr-c4306...="" class="img-responsive HP26_..." alt="A mortgage that work..." data-expand="10" data-src="https://aemapi.citi...." src="https://aemapi.citi....">
<img _ngcontent-ssr-c4306...="" class="img-responsive HP23_..." alt="Save More, Earn More..." data-expand="10" data-src="https://aemapi.citi...." src="https://aemapi.citi....">
Showing first 5 of 9 audited elements.
Inline text spacing must be adjustable with custom stylesheets14 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
<html class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
<ul _ngcontent-ssr-c739218679="" class="nav-bar-main-ul" style="display: flex; position: static;">
<div _ngcontent-ssr-c2067562431="" class="heroReskinSection" style="background-image: url("./cbol-hp-static-assets/assets/img/Citi-futuristic-angles-bg-compressed.jpg");"><input _ngcontent-ssr-c1530547397="" cdsinput="" formcontrolname="password" class="cds-input form-control cds-placeholder-text ng-untouched ng-pristine cdk-text-field-autofill-monitored ng-invalid" type="password" maxlength="256" id="password" style="padding-right: 64px;">
<div _ngcontent-ssr-c4105219706="" role="img" alt="icon" aria-label="show" class="medium" style="width: 20px; height: 20px;">
Showing first 5 of 14 audited elements.
Interactive controls must not be nested30 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 _ngcontent-ssr-c1590736564="" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/citiredesign.svg" alt="Citi" class="ng-star-inserted">
<img _ngcontent-ssr-c1590736564="" alt="Citi FDIC Insured" src="https://aemapi.citi.com/content/dam/cfs/mobile/assets/CBOL/IA/Angular/assets/Citi_Icon_Sprite_Banner_v2.svg" id="fdicLogoA" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navbankingmainAnchor1" role="button" aria-expanded="false">Banking</a>
Showing first 5 of 30 audited elements.
Interactive elements must have a visible focus indicator44 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 _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<a _ngcontent-ssr-c1590736564="" id="atmLink" href="/citibank-location-finder" class="ng-star-inserted">
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
Showing first 5 of 44 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination4 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 _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<div _ngcontent-ssr-c3209448095="" role="main">
<div _ngcontent-ssr-c3517354859="" role="contentinfo" class="footer ng-star-inserted"><!----><!----><div _ngcontent-ssr-c3517354859="" style="height: 814px;" class="ng-star-inserted"></div><!----></div>
lang attribute must have a valid value2 elements
Screen readers use language-specific pronunciation libraries that must match the content's language. Invalid language declarations cause screen readers to use the wrong pronunciation library, making content sound confusing or unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<button _ngcontent-ssr-c1590736564="" id="langBtn" data-target="#citi-modalb2" lang="es" aria-label="Haz clic para cambiar la página al español" class="ng-star-inserted">
<span _ngcontent-ssr-c1590736564="" lang="es">ESPAÑOL</span>
Links must have discernible text21 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 _ngcontent-ssr-c2855406740="" aria-live="assertive" class="alternateSkipNav" href="">Skip to Content</a>
<a _ngcontent-ssr-c1590736564="" id="sessionFocusUrl" aria-label="citi-Home" tabindex="0" href="/" class="ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" id="atmLink" href="/citibank-location-finder" class="ng-star-inserted">
<a _ngcontent-ssr-c739218679="" class="main-links mobileRightChevron topNavButton ng-star-inserted" id="navOpenAccmainAnchor8" href="/banking/bank-accounts?intc=citihpmenu_overview_bank-accounts">Open an Account</a>
<a _ngcontent-ssr-c2067562431="" href="https://online.citi.com/US/nga/lendingv2/ntc/application/loan?affcode=CH3&intc=PIL_HP22" target="_blank">
Showing first 5 of 21 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
<div _ngcontent-ssr-c3209448095="" role="main">
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 class="cbolui-ddl" lang="en" data-beasties-container="" style="display: block; visibility: visible;">
Required ARIA attributes must be provided20 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 _ngcontent-ssr-c1590736564="" role="banner" class="banner ng-star-inserted">
<a _ngcontent-ssr-c1590736564="" role="presentation" id="fdicFocusUrl" tabindex="0">
<div _ngcontent-ssr-c739218679="" role="navigation" aria-label="Main" class="navigationParent blueTopNavTheme preLogin ng-star-inserted">
<li _ngcontent-ssr-c739218679="" role="listitem" class="mainListItem ng-star-inserted" id="navcreditCardMainLI">
<a _ngcontent-ssr-c739218679="" tabindex="0" class="main-links mobileRightChevron topNavTabs ng-star-inserted" id="navcreditCardmainAnchor0" role="button" aria-expanded="false">Credit Cards</a>
Showing first 5 of 20 audited elements.
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
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 Citibank?
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
- Fidelity75 out of 100, needs improvement
- Bank of America71 out of 100, needs improvement
- Capital One70 out of 100, needs improvement
- Barclays55 out of 100, poor
- PayPal30 out of 100, poor