eBayebay.com
Accessibility Score
Issues Found
Issues Found
MinorARIA role should be appropriate for the element1 element
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Failing Elements
<header role="navigation">
Fix any of the following:
- ARIA role navigation is not allowed for given element
Passed Audits
<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" class="font-marketsans">
<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" class="font-marketsans">
<li> elements must be contained in a <ul> or <ol>5 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li class="daily-deals"><a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a></li>
<li><a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a></li>
<li class="sell"><a href="http://csr.ebay.com/cse/sell.jsf" _sp="m46120.l1528">Sell</a></li>
<li class="my-ebay no-spacer">
<li class="cart no-spacer">
<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 class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements2 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="nav left-nav"><li class="daily-deals"><a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a></li><li><a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a></li></ul>
<ul class="nav right-nav">
All page content should be contained by landmarks31 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="content" class="content">
<header role="navigation">
<div class="river">
<a id="logo-text" href="https://www.ebay.com" tabindex="-1">eBay Logo <div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div></a>
<div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
<ul class="nav left-nav"><li class="daily-deals"><a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a></li><li><a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a></li></ul>
<li class="daily-deals"><a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a></li>
<a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a>
<li><a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a></li>
<a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a>
Showing first 10 of 31 audited elements.
ARIA attributes must be used as specified for the element's role3 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
<button class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">ARIA attributes must conform to valid names3 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
<button class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">ARIA attributes must conform to valid values2 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
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">ARIA hidden element must not be focusable or contain focusable elements10 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 aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg>
<svg class="icon icon--search" focusable="false" aria-hidden="true"><use xlink:href="#icon-search"></use></svg>
ARIA role should be appropriate for the element13 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 tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
<div role="menu" class="menu-button__items" id="s0-0-13-2-19-content-menu">
<div href="https://www.ebay.com/myb/Summary" _sp="m46120.l1533" class="menu-button__item" role="menuitem" tabindex="0" data-makeup-index="0"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
<div href="https://www.ebay.com/myb/container?key=recentlyviewed" _sp="m46120.l9225" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="1">
<div href="https://www.ebay.com/myb/BidsOffers" _sp="m46120.l1535" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="2"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
<div href="https://www.ebay.com/myb/WatchList" _sp="m46120.l1534" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="3"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
<div href="https://www.ebay.com/myb/PurchaseHistory" _sp="m46120.l1536" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="4"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
<div href="https://www.ebay.com/mys/overview?MyEbay&gbh=1&CurrentPage=MyeBayAllSelling&ssPageName=STRK:ME:LNLK:MESX" _sp="m46120.l1537" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="5">
<div href="https://www.ebay.com/myb/SavedSearches" _sp="m46120.l9503" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="6"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
<div href="https://www.ebay.com/myb/SavedSellers" _sp="m46120.l9505" class="menu-button__item" role="menuitem" tabindex="-1" data-makeup-index="7"><span></span><svg aria-hidden="true" class="icon icon--tick-small" focusable="false"><use xlink:href="#icon-tick-small"></use></svg></div>
Showing first 10 of 13 audited elements.
ARIA roles used must conform to valid values4 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
<header role="navigation">
<div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<form method="get" action="https://www.ebay.com/sch/i.html" role="search" class="search-bar">
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="static">
Buttons must have discernible text2 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 class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<button data-marko="{"onblur":"handleBlur s0-0-13-2-42 false","onfocus":"handleFocus s0-0-13-2-42 false","onkeydown":"handleKeydown s0-0-13-2-42 false","onclick":"handleClick s0-0-13-2-42 false"}" id="searchbutton" type="submit" class="btn btn--primary" data-ebayui="">Deprecated ARIA roles must not be used4 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
<header role="navigation">
<div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<form method="get" action="https://www.ebay.com/sch/i.html" role="search" class="search-bar">
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" class="font-marketsans">
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
<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" class="font-marketsans">
Elements must meet minimum color contrast ratio thresholds8 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 href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a>
<a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a>
<a href="http://csr.ebay.com/cse/sell.jsf" _sp="m46120.l1528">Sell</a>
<span>My eBay</span>
<h1>Where's all the stuff?</h1>
<h2>Our homepage is down, but the rest of eBay is fine. We'll have it back up in a moment.</h2>
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton"><button data-marko="{"onblur":"handleBlur s0-0-13-2-42 false","onfocus":"handleFocus s0-0-13-2-42 false","onkeydown":"handleKeydown s0-0-13-2-42 false","onclick":"handleClick s0-0-13-2-42 false"}" id="searchbutton" type="submit" class="btn btn--primary" data-ebayui="">Elements must only use permitted ARIA attributes3 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
<button class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">Elements must only use supported ARIA attributes3 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
<button class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<input data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">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
<a id="logo-text" href="https://www.ebay.com" tabindex="-1">eBay Logo <div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div></a>
<div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
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 data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">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 data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">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 data-marko="{"onkeydown":"handle..." data-marko-key="@input s0-0-13-2-39" id="s0-0-13-2-39-textbox" class="textbox__control tex..." type="text" name="_nkw" max-length="300" placeholder="Search for anything...." aria-labelledby="searchbutton">Heading levels should only increase by one2 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>Where's all the stuff?</h1>
<h2>Our homepage is down, but the rest of eBay is fine. We'll have it back up in a moment.</h2>
Headings should not be empty2 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>Where's all the stuff?</h1>
<h2>Our homepage is down, but the rest of eBay is fine. We'll have it back up in a moment.</h2>
IDs used in ARIA and labels must be unique2 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
<span class="menu-button__menu" tabindex="-1" id="nid-dn0-0-content">
<button data-marko="{"onblur":"handleBlur s0-0-13-2-42 false","onfocus":"handleFocus s0-0-13-2-42 false","onkeydown":"handleKeydown s0-0-13-2-42 false","onclick":"handleClick s0-0-13-2-42 false"}" id="searchbutton" type="submit" class="btn btn--primary" data-ebayui="">Interactive controls must not be nested3 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
<button class="menu-button__button btn btn--borderless" aria-expanded="false" aria-haspopup="true" no-toggle-icon="" data-ebayui="" type="button" aria-controls="nid-dn0-0-content"><span>My eBay</span></button>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<button data-marko="{"onblur":"handleBlur s0-0-13-2-42 false","onfocus":"handleFocus s0-0-13-2-42 false","onkeydown":"handleKeydown s0-0-13-2-42 false","onclick":"handleClick s0-0-13-2-42 false"}" id="searchbutton" type="submit" class="btn btn--primary" data-ebayui="">Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 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 role="navigation">
<main>
Links must have discernible text5 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 id="logo-text" href="https://www.ebay.com" tabindex="-1">eBay Logo <div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div></a>
<a href="http://deals.ebay.com" _sp="m46120.l3188">Daily Deals</a>
<a href="http://ocsnext.ebay.com/ocs/home" _sp="m46120.l1545">Help & Contact</a>
<a href="http://csr.ebay.com/cse/sell.jsf" _sp="m46120.l1528">Sell</a>
<a href="https://cart.ebay.com/" _sp="m46120.l2633">
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
<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" class="font-marketsans">
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" class="font-marketsans">
Required ARIA attributes must be provided4 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
<header role="navigation">
<div tabindex="0" role="presentation" alt="eBay Logo" _sp="m46120.l2586" class="logo"></div>
<svg class="icon icon--cart" focusable="false" height="14" width="14" role="img" aria-label="Cart">
<form method="get" action="https://www.ebay.com/sch/i.html" role="search" class="search-bar">
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, user-scalable=yes, minimum-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, user-scalable=yes, minimum-scale=1">