Charles Schwabschwab.com
Accessibility Score
Issues Found
Issues Found
Passed Audits
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements1 element
Screen readers announce definition lists in a specific way that helps users understand term-definition relationships. When definition lists aren't properly marked up with dl, dt, and dd elements, screen readers produce confusing or inaccurate output that prevents users from understanding the content structure.
Audit Elements
<dl class="bcn-accordion-table bcn-accordion-table--default">
<dt> and <dd> elements must be contained by a <dl>6 elements
Definition list items must follow a specific hierarchy: dl as parent, with alternating dt (term) and dd (description) children. Without this proper structure, the list becomes invalid and screen readers cannot inform users they're listening to a list or convey the relationships between terms and their definitions.
Audit Elements
<dt class="bcn-accordion-item" id="bcn-accordion-98846-bcn-accordion-item-98816" data-track="category-lc|adobe-furl_securityguarantee|fireonce" data-dl-component.id="98816" data-dl-component.title="What is the Schwab Security Guarantee?" data-dl-component.type="bcn-accordion-item">
<dt class="bcn-accordion-item" id="bcn-accordion-98846-bcn-accordion-item-98821" data-track="category-lc|adobe-furl_costtowork|fireonce" data-dl-component.id="98821" data-dl-component.title="How much does it cost to work with Schwab?" data-dl-component.type="bcn-accordion-item">
<dt class="bcn-accordion-item" id="bcn-accordion-98846-bcn-accordion-item-98826" data-track="category-lc|adobe-furl_howtoopen|fireonce" data-dl-component.id="98826" data-dl-component.title="How do I open an account?" data-dl-component.type="bcn-accordion-item">
<dt class="bcn-accordion-item" id="bcn-accordion-98846-bcn-accordion-item-98831" data-track="category-lc|adobe-furl_whatproducts|fireonce" data-dl-component.id="98831" data-dl-component.title="What kind of investment products does Schwab offer?" data-dl-component.type="bcn-accordion-item">
<dt class="bcn-accordion-item" id="bcn-accordion-98846-bcn-accordion-item-98836" data-track="category-lc|adobe-furl_howeasytoswitch|fireonce" data-dl-component.id="98836" data-dl-component.title="How easy is it to switch brokerage providers?" data-dl-component.type="bcn-accordion-item">
<dt class="bcn-accordion-item bcn-accordion-item--bank" id="bcn-accordion-98846-bcn-accordion-item-98841" data-track="category-lc|adobe-furl_whybank|fireonce" data-dl-component.id="98841" data-dl-component.title="Why should I bank with Schwab Bank?" data-dl-component.type="bcn-accordion-item">
<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" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
<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" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
<li> elements must be contained in a <ul> or <ol>79 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>
<li>
<li>
<li>
<li>
<li>
<li>
<li>
<li>
<li>
Showing first 10 of 79 audited elements.
<svg> elements with an img role must have alternative text1 element
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements14 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="flex gap-5 items-center">
<ul class="max-lg:hidden flex">
<ul class="cta-panel__body">
<li class="cta-panel--fundspotlight__item">
</li>
</ul><ul class="row cta-panel__body">
<ul class="row cards card-outline-33">
<ul class="row no-gutters cards icon-card-clear-20">
<ul class="footmn-menu-main">
<ul class="footmn-menu-child">
<ul class="footmn-menu-child">
<ul class="footmn-menu-child">
Showing first 10 of 14 audited elements.
All page content should be contained by landmarks650 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 id="skip">
<a class="visually-hidden focusable skip-link" href="#primary-navigation">
Skip to main navigation
</a>
<a class="visually-hidden focusable skip-link" href="#content">
Skip to content
</a>
</div><a class="visually-hidden focusable skip-link" href="#primary-navigation">
Skip to main navigation
</a><a class="visually-hidden focusable skip-link" href="#content">
Skip to content
</a><div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas="">
<div class="page-standard" id="pg__c">
<div id="schwab_header">
<div class="region region-schwab-header">
<div id="block-sch-beacon-retail-chatvars" data-block-plugin-id="block_content:8ac86cfc-a7ee-4677-9a3c-f30c3519d350" class="block block-block-content block-block-content8ac86cfc-a7ee-4677-9a3c-f30c3519d350 block-chat-vars">
<div class="field field--name-body field--type-text-with-summary field--label-hidden field__item"><script>var netHostUrl = "https://client.schwab.com";</script> </div>
<div id="block-cardclearpadding" data-block-plugin-id="block_content:67baeae7-a8b0-4edb-8d14-d8f1fe7d225d" class="block block-block-content block-block-content67baeae7-a8b0-4edb-8d14-d8f1fe7d225d block-card-clear-padding">
Showing first 10 of 650 audited elements.
Alternative text of images should not be repeated as text6 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://www.schwab.com/sites/g/files/eyrktu1401/files/Invest_gradient_Marquee%20%282%29.png" alt="As many ways to invest as there are investors.">
<img src="https://www.schwab.com/sites/g/files/eyrktu1401/files/stockbrokers-number1-overall-broker-2026_908x510.png" alt="Stockbrokers.com 2026 #1 Overall Brokerage, Mobile Trading Apps, and Customer Service awards">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Call%20SVG_0.svg" alt="Call icon">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Chat%20SVG_1.svg" alt="Chat icon">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Visit%20SVG_0.svg" alt="Visit icon">
<img src="/themes/custom/sch_retail/imgs/oyt.png" alt="Own your tomorrow logo">
ARIA attributes must be used as specified for the element's role52 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<nav aria-label="Utility" data-dl-component.title="utility">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
Showing first 10 of 52 audited elements.
ARIA attributes must conform to valid names52 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<nav aria-label="Utility" data-dl-component.title="utility">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
Showing first 10 of 52 audited elements.
ARIA attributes must conform to valid values46 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<nav aria-label="Utility" data-dl-component.title="utility">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<nav class="flex justify-between w-full" id="primary-navigation" aria-label="Primary" data-dl-component.id="meganav_menu" data-dl-component.type="meganav_menu">
<section id="schwab_branch_locator" aria-label="Schwab Branch Locator" class="schwab_near_branch">
Showing first 10 of 46 audited elements.
ARIA hidden element must not be focusable or contain focusable elements27 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
<svg width="24" height="16" viewBox="0 0 24 16" xmlns="http://www.w3.org/2000/svg" class="my-1" focusable="false" aria-hidden="true">
<svg width="16" height="16" viewBox="0 0 17 17" fill="none" focusable="false" aria-hidden="true" role="img" xmlns="http://www.w3.org/2000/svg" style="block-size: 18px; inline-size: 18px;">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true" role="img">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Accounts & Products" data-dl-component.ty...="meganav_menu_l1" id="_r_8_0-flyout" aria-hidden="true" inert="" style="height: 0px;">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Advice" data-dl-component.ty...="meganav_menu_l1" id="_r_9_1-flyout" aria-hidden="true" inert="" style="height: 0px; left: 1...">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Pricing" data-dl-component.ty...="meganav_menu_l1" id="_r_a_2-flyout" aria-hidden="true" inert="" style="height: 0px; left: 3...">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
Showing first 10 of 27 audited elements.
ARIA role should be appropriate for the element25 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
<iframe src="javascript:void(0)" title="" role="presentation" style="width: 0px; height: 0px; border: 0px; display: none;"></iframe>
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 955.8442 955.8442" xmlns="http://www.w3.org/2000/svg" width="100%" class="size-12">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<svg width="16" height="16" viewBox="0 0 17 17" fill="none" focusable="false" aria-hidden="true" role="img" xmlns="http://www.w3.org/2000/svg" style="block-size: 18px; inline-size: 18px;">
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true" role="img">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Accounts & Products" data-dl-component.ty...="meganav_menu_l1" id="_r_8_0-flyout" aria-hidden="true" inert="" style="height: 0px;">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none" focusable="false" aria-hidden="true" role="img" class="z-1 motion-safe:transition-transform rotate-90" style="block-size: 20px; inline-size: 20px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Advice" data-dl-component.ty...="meganav_menu_l1" id="_r_9_1-flyout" aria-hidden="true" inert="" style="height: 0px; left: 1...">
Showing first 10 of 25 audited elements.
ARIA roles used must conform to valid values6 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
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<div class="clearfix main" id="main" role="main">
<svg focusable="false" role="presentation" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 72 72">
<footer id="footer" class="footer" role="contentinfo">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
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="body-sidebars-none alias--home nodetype--pattern_landing_page logged-out node--type-pattern_landing_page normal-layout" data-once="schwab_carousel schwabEditorLinkBehaviorsHandler accordionBehavior location-alert" a-c-at="8e4dfddd7ddc182a50f7fc31f40474a5" v-c-at="latest">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
Buttons must have discernible text15 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" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Accounts & Products" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_8_0-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Advice" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_9_1-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Pricing" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_a_2-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Why Schwab" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_b_3-flyout">
<button class="bcn-button-control sch-plus-2x" type="button" aria-controls="bcn-accordion-98846-bcn-accordion-item-98816--ans" aria-describedby="bcn-accordion-98846-bcn-accordion-item-98816--title" aria-label="Toggle disclosure" aria-expanded="false"> </button>
<button class="bcn-button-control sch-plus-2x" type="button" aria-controls="bcn-accordion-98846-bcn-accordion-item-98821--ans" aria-describedby="bcn-accordion-98846-bcn-accordion-item-98821--title" aria-label="Toggle disclosure" aria-expanded="false"> </button>
Showing first 10 of 15 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
<footer id="footer" class="footer" role="contentinfo">
Deprecated ARIA roles must not be used6 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
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<div class="clearfix main" id="main" role="main">
<svg focusable="false" role="presentation" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 72 72">
<footer id="footer" class="footer" role="contentinfo">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
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" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
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 id="footer" class="footer" role="contentinfo">
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 class="clearfix main" id="main" 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 lang="en" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
Elements marked as presentational should be consistently ignored1 element
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
<svg focusable="false" role="presentation" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 72 72">
Elements must meet minimum color contrast ratio thresholds172 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 data-component="link" class="cursor-pointer !text..." data-dl-link.name="Find a Branch" data-dl-link.type="navigation" href="https://www.schwab.c...">
<span>Contact Us</span>
<span class="ml-1 text-white cursor-pointer hover:underline">Chat</span>
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<span>Log In</span>
<span class="pointer-events-none relative z-1 pt-0.5">Accounts & Products</span>
<span class="pointer-events-none relative z-1 pt-0.5">Advice</span>
<span class="pointer-events-none relative z-1 pt-0.5">Pricing</span>
<span class="pointer-events-none relative z-1 pt-0.5">Why Schwab</span>
<a data-component="link" class="bg-transparent text-..." data-dl-link.name="Learn" data-dl-link.type="navigation" data-dl-site_events="meganav_menu_click" href="https://www.schwab.c...">
Showing first 10 of 172 audited elements.
Elements must only use permitted ARIA attributes52 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<nav aria-label="Utility" data-dl-component.title="utility">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
Showing first 10 of 52 audited elements.
Elements must only use supported ARIA attributes52 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<nav aria-label="Utility" data-dl-component.title="utility">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<input id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
Showing first 10 of 52 audited elements.
Elements should not have tabindex greater than zero2 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<a class="bcn-link-icon bcn-link-icon--lightbackground sch_chat" data-track="category-cce" data-dl-link.name="Get live online assistance 24/7" href="#" data-anchor-chat="chatLinkRef2" tabindex="0">
Form elements must have labels1 element
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 id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
Form elements should have a visible label1 element
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 id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
Form field must not have multiple label elements1 element
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 id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe src="https://sws-gateway-..." allow="publickey-credential..." id="schwablmslogin" title="log in form" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" height="65" width="630" style="border: transparent">
Frames must have an accessible name1 element
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe src="https://sws-gateway-..." allow="publickey-credential..." id="schwablmslogin" title="log in form" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" height="65" width="630" style="border: transparent">
Heading levels should only increase by one27 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="bcn-h1 schfx-text__heading bcn-article-heading--l ">
Manage your wealth, your way.
</h1><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m sr-only" id="heading_how_we_work_together_is_up_to_you.">
How we work together is up to you.
</h2><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_you_deserve_more._we_can_help.">
You deserve more. We can help.
</h2><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
World-class education for every investor.
</h3><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
Transparent pricing and low costs.
</h3><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
Your satisfaction is guaranteed and your security is our priority.
</h3><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_get_started_with_one_of_our_most_popular_accounts.">
Get started with one of our most popular accounts.
</h2><h2>
<div class="field field--name-node-title field--type-ds field--label-hidden field__item"> Take the next step.
</div>
</h2><h2 class="bcn-h2 schfx-text__heading bcn-heading--l " id="heading_schwab_is_the_first_brokerage_to_win_#1_overall,_#1_mobile_apps,_and_#1_customer_service_in_the_same_year_since_2017">
<h2>
<div class="field field--name-node-title field--type-ds field--label-hidden field__item"> Important information about our relationship with you: Client Relationship Summaries
</div>
</h2>Showing first 10 of 27 audited elements.
Headings should not be empty27 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="bcn-h1 schfx-text__heading bcn-article-heading--l ">
Manage your wealth, your way.
</h1><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m sr-only" id="heading_how_we_work_together_is_up_to_you.">
How we work together is up to you.
</h2><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_you_deserve_more._we_can_help.">
You deserve more. We can help.
</h2><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
World-class education for every investor.
</h3><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
Transparent pricing and low costs.
</h3><h3 class="bcn-h3 schfx-text__heading bcn-heading--m-bold ">
Your satisfaction is guaranteed and your security is our priority.
</h3><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_get_started_with_one_of_our_most_popular_accounts.">
Get started with one of our most popular accounts.
</h2><h2>
<div class="field field--name-node-title field--type-ds field--label-hidden field__item"> Take the next step.
</div>
</h2><h2 class="bcn-h2 schfx-text__heading bcn-heading--l " id="heading_schwab_is_the_first_brokerage_to_win_#1_overall,_#1_mobile_apps,_and_#1_customer_service_in_the_same_year_since_2017">
<h2>
<div class="field field--name-node-title field--type-ds field--label-hidden field__item"> Important information about our relationship with you: Client Relationship Summaries
</div>
</h2>Showing first 10 of 27 audited elements.
IDs used in ARIA and labels must be unique37 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 id="_r_5_" placeholder="Search" aria-disabled="false" class="col-start-1 row-star..." type="text" value="" name="searchInput">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Accounts & Products" data-dl-component.ty...="meganav_menu_l1" id="_r_8_0-flyout" aria-hidden="true" inert="" style="height: 0px;">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Advice" data-dl-component.ty...="meganav_menu_l1" id="_r_9_1-flyout" aria-hidden="true" inert="" style="height: 0px; left: 1...">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Pricing" data-dl-component.ty...="meganav_menu_l1" id="_r_a_2-flyout" aria-hidden="true" inert="" style="height: 0px; left: 3...">
<div role="dialog" class="h-0 flex justify-bet..." data-dl-component.ti...="Why Schwab" data-dl-component.ty...="meganav_menu_l1" id="_r_b_3-flyout" aria-hidden="true" inert="" style="height: 0px; left: a...">
<label style="margin: 0px" id="alert-title-215141" for="selectLocation">Location alert</label>
<select class="location-alert__select" id="selectLocation" name="Location" alert="">
<h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m sr-only" id="heading_how_we_work_together_is_up_to_you.">
How we work together is up to you.
</h2><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_you_deserve_more._we_can_help.">
You deserve more. We can help.
</h2><h2 class="bcn-h2 schfx-text__heading bcn-article-heading--m " id="heading_get_started_with_one_of_our_most_popular_accounts.">
Get started with one of our most popular accounts.
</h2>Showing first 10 of 37 audited elements.
Images must have alternative text6 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://www.schwab.com/sites/g/files/eyrktu1401/files/Invest_gradient_Marquee%20%282%29.png" alt="As many ways to invest as there are investors.">
<img src="https://www.schwab.com/sites/g/files/eyrktu1401/files/stockbrokers-number1-overall-broker-2026_908x510.png" alt="Stockbrokers.com 2026 #1 Overall Brokerage, Mobile Trading Apps, and Customer Service awards">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Call%20SVG_0.svg" alt="Call icon">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Chat%20SVG_1.svg" alt="Chat icon">
<img class="cta-panel__item__image" src="https://www.schwab.com/sites/g/files/eyrktu1401/files/2024-09/Visit%20SVG_0.svg" alt="Visit icon">
<img src="/themes/custom/sch_retail/imgs/oyt.png" alt="Own your tomorrow logo">
Inline text spacing must be adjustable with custom stylesheets9 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 lang="en" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
<iframe src="https://sws-gateway-..." allow="publickey-credential..." id="schwablmslogin" title="log in form" frameborder="0" marginheight="0" marginwidth="0" scrolling="no" height="65" width="630" style="border: transparent">
<div class="sch_mixer_component" id="1" data-dl-component.child_index="1" style="display: block;">
<div class="schfx-text__icon" style="background-image:url(https://www.schwab.com/sites/g/files/eyrktu1401/files/ICN-Flat-Light-Grad%20Cap-nobkg%403x.png);"></div>
<div class="schfx-text__link_group" style="position: relative; margin-top: 44.7969px;">
<div class="schfx-text__icon" style="background-image:url(https://www.schwab.com/sites/g/files/eyrktu1401/files/ICN-Flat-Light-USD-nobkg%403x_0.png);"></div>
<div class="schfx-text__link_group" style="position: relative; margin-top: 44.7969px;">
<div class="schfx-text__icon" style="background-image:url(https://www.schwab.com/sites/g/files/eyrktu1401/files/ICN-Flat-Light-Shield%20Lock-nobkg%403x.png);"></div>
<div class="schfx-fab" id="" style="position: fixed; width: 60px;">
Interactive controls must not be nested22 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
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_3_" data-state="closed">
<button type="button" id="chatGlobalHeader" class="!text-2xs !text-whit..." aria-label="Chat Live" questid="FD8206EF-75A9-492F-B..." portid="E8EAB688-933C-4AFD-B..." windowfeatures="width=535,height=610..." data-dl-link.name="chat" data-dl-link.type="modal" data-anchor-chat="chatLinkRef1" ...>
<button id="search" name="search" type="submit" aria-label="Submit search" aria-disabled="false" class="flex shrink-0 items-...">
<button type="button" aria-expanded="false" class="flex items-center !text-2xs !text-white cursor-pointer hover:underline forced-colors:outline" aria-haspopup="dialog" aria-controls="radix-_r_7_" data-state="closed">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Accounts & Products" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_8_0-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Advice" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_9_1-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Pricing" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_a_2-flyout">
<button aria-haspopup="dialog" class="cursor-pointer h-ful..." type="button" data-dl-link.name="Why Schwab" data-dl-link.type="menu" data-dl-site_events="meganav_menu_l1_expa..." aria-expanded="false" aria-controls="_r_b_3-flyout">
<img src="https://www.schwab.com/sites/g/files/eyrktu1401/files/Invest_gradient_Marquee%20%282%29.png" alt="As many ways to invest as there are investors.">
Showing first 10 of 22 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination19 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
<header aria-label="MegaNav" data-dl-component.id="meganav" data-dl-component.type="meganav" class="meganav--drupal">
<nav aria-label="Utility" data-dl-component.title="utility">
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<nav class="flex justify-between w-full" id="primary-navigation" aria-label="Primary" data-dl-component.id="meganav_menu" data-dl-component.type="meganav_menu">
<section id="schwab_branch_locator" aria-label="Schwab Branch Locator" class="schwab_near_branch">
<div class="clearfix main" id="main" role="main">
<section class="schfx-layout schfx-l..." id="fx_deck_tile_233431" aria-labelledby="heading_how_we_work_...">
<section class="schfx-layout schfx-l..." id="fx_deck_232601" aria-labelledby="heading_you_deserve_...">
<section class="schfx-layout schfx-l..." id="fx_deck_tile_232631" aria-labelledby="heading_get_started_...">
<section aria-label="Take the next step." class="container cta-panel__wrapper cta-panel--basic " id="cta-panel--basic-98851" data-dl-component.id="98851" data-dl-component.type="cta-panel" data-dl-component.variation="basic" data-dl-component.title="Take the next step.">
Showing first 10 of 19 audited elements.
Links must be distinguishable without relying on color12 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 href="https://schwab.com/transparency" data-track="category-lc">Learn more at schwab.com/transparency ></a>
<a data-track="category-lc" href="https://advisorservices.schwab.com/why-schwab?ilc=WFJ" target="_blank">Schwab Advisor Services™</a>
<a data-track="category-lc" href="https://franchise.schwab.com/why-schwab?ilc=WFI" target="_blank">Schwab Franchise.</a>
<a data-track="category-lc" href="https://www.schwabfunds.com/welcome9?destination=/" target="_blank">Charles Schwab Investment Management, Inc.</a>
<a data-popup-height="" data-popup-width="" data-stock-symbol="" data-track="" href="https://brokercheck.finra.org/" rel="" target="" title="">FINRA's BrokerCheck</a>
<a href="https://www.schwab.com/resource/schwab-intelligent-portfolios-and-schwab-intelligent-portfolios-premium" title="" type="" target="" data-stock-symbol="" data-popup-height="" data-popup-width="" data-track="" aria-label="" rel="">
<a href="https://www.stockbrokers.com/annual-awards-2026" target="_blank">2026 Annual Awards page</a>
<a href="http://www.sipc.org/" title="" type="" target="_blank" data-stock-symbol="" data-popup-height="" data-popup-width="" data-track="" aria-label="" rel="">Member SIPC</a>
<a href="https://international.schwab.com/" target="_blank">non-U.S. residents</a>
<a href="https://www.schwab.com.hk/" title="" type="" target="_blank" data-stock-symbol="" data-popup-height="" data-popup-width="" data-track="" aria-label="" rel="">Charles Schwab Hong Kong clients</a>
Showing first 10 of 12 audited elements.
Links must have discernible text104 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="visually-hidden focusable skip-link" href="#primary-navigation">
Skip to main navigation
</a><a class="visually-hidden focusable skip-link" href="#content">
Skip to content
</a><a href="/" class="text-primary hover:text-primary/90 size-12 lg:size-24 flex-shrink-0 flex items-center justify-center" aria-label="Charles Schwab Home">
<a data-component="link" class="cursor-pointer !text..." data-dl-link.name="Find a Branch" data-dl-link.type="navigation" href="https://www.schwab.c...">
<a data-component="link" class="bg-transparent text-..." data-dl-link.name="Learn" data-dl-link.type="navigation" data-dl-site_events="meganav_menu_click" href="https://www.schwab.c...">
<a data-component="link" class="text-center rounded-..." data-dl-site_events="call_to_action,open_..." href="https://www.schwab.c...">
<a class="bcn-link-icon bcn-link-icon--lightbackground bcn-body--s-list branch_name--link" id="branch_locator--branch-name" name="&lid=lc_branch_near_me_branch" data-dl-link.name="placeholder" href="/branches/cupertino?branch_id=1007">Cupertino</a>
<a class="bcn-button bcn-button--open-an-account bcn-link-button" data-track="adobe-mixer_cta_button|category-cta" type="_open_an_account" data-dl-link.name="Open an account" data-dl-site_events="call_to_action, open_account" href="/open-an-account">Get started</a>
<a class="schfx-tile schfx-til..." aria-describedby="" id="fx_tile_uid-18249367..." href="https://www.schwab.c..." data-track="linkid-cta_fc_1|cate..." aria-label="Invest on my own">
<a class="schfx-tile schfx-til..." aria-describedby="" id="fx_tile_uid-64176687" href="https://www.schwab.c..." data-track="linkid-cta_fc_2|cate..." aria-label="Trade with thinkorsw...">
Showing first 10 of 104 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 class="clearfix main" id="main" 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 lang="en" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
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" dir="ltr" prefix="content: http://purl..." class=" js" data-once="contactUs lmsLogin f..." style="--theme-family-membe...">
Required ARIA attributes must be provided6 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
<svg id="logo_default" role="img" focusable="false" aria-label="Charles Schwab logo" viewBox="0 0 50 50" xmlns="http://www.w3.org/2000/svg" width="100%">
<form class="flex flex-1 shrink-0" id="search-form" name="search-form" role="search" aria-label="Site" data-dl-component.title="meganav search">
<div class="clearfix main" id="main" role="main">
<svg focusable="false" role="presentation" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 72 72">
<footer id="footer" class="footer" role="contentinfo">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">