Skip to main content

eBay ebay.com

Screenshot of the eBay home page

Accessibility score

95 out of 100, goodGood±0 vs September

League position

1stof 10

Issues found

1

Audits passed

17

Accessibility score over time

weekly scans · last 6 months
  • Good · 90+
  • Needs improvement · 70–89
  • Poor · Below 70

This month's scan

Issues found

1Moderate
Page should contain a level-one heading

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.

Learn more

Failing Elements

html
<html lang="en">

Fix all of the following:

  • Page must have a level-one heading
Passed audits17 across 1 page
<html> element must have a lang attribute

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.

Learn more

Audit Elements

html
<html lang="en">
<html> element must have a valid value for the lang attribute

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.

Learn more

Audit Elements

html
<html lang="en">
All page content should be contained by landmarks

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.

Learn more

Audit Elements

main
<main class="main-content">
.status--container
<div class="status--container">
.error-header
<div class="error-header"><div class="error-header__text-block"><p class="error-header__headline">SORRY</p><div id="error-info"><p>Something went wrong on our end</p><hr><p class="reference-id">0.4760d017.1793066684.78126065</p><hr><p>Please go back and try again.</p></div></div></div>
.error-header__text-block
<div class="error-header__text-block"><p class="error-header__headline">SORRY</p><div id="error-info"><p>Something went wrong on our end</p><hr><p class="reference-id">0.4760d017.1793066684.78126065</p><hr><p>Please go back and try again.</p></div></div>
.error-header__headline
<p class="error-header__headline">SORRY</p>

Showing first 5 of 13 audited elements.

aria-hidden="true" must not be present on the document body

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.

Learn more

Audit Elements

body
<body>
Content must reflow without two-dimensional scrolling

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.

Learn more

Contentinfo landmark should not be contained in another landmark

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.

Learn more

Audit Elements

#glbfooter
<footer id="glbfooter"><p>Copyright © 1995-2026 eBay Inc. All Rights Reserved.</p></footer>
Document should have one main landmark

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.

Learn more

Audit Elements

html
<html lang="en">
Document should not have more than one contentinfo landmark

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.

Learn more

Audit Elements

#glbfooter
<footer id="glbfooter"><p>Copyright © 1995-2026 eBay Inc. All Rights Reserved.</p></footer>
Document should not have more than one main landmark

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.

Learn more

Audit Elements

main
<main class="main-content">
Documents must have <title> element to aid in navigation

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.

Learn more

Audit Elements

html
<html lang="en">
Elements must meet minimum color contrast ratio thresholds

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.

Learn more

Audit Elements

#glbfooter > p
<p>Copyright © 1995-2026 eBay Inc. All Rights Reserved.</p>
Interactive controls must not be nested

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.

Learn more

Audit Elements

hr:nth-child(2)
<hr>
hr:nth-child(4)
<hr>
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

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.

Learn more

Audit Elements

main
<main class="main-content">
#glbfooter
<footer id="glbfooter"><p>Copyright © 1995-2026 eBay Inc. All Rights Reserved.</p></footer>
Main landmark should not be contained in another landmark

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.

Learn more

Audit Elements

main
<main class="main-content">
Text must remain readable when spacing is increased

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.

Learn more

Users should be able to zoom and scale the text up to 500%

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.

Learn more

Audit Elements

meta[name="viewport"]
<meta name="viewport" content="width=device-width,initial-scale=1">
Zooming and scaling must not be disabled

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.

Learn more

Audit Elements

meta[name="viewport"]
<meta name="viewport" content="width=device-width,initial-scale=1">

How does your site stack up against eBay?

Run the same automated WCAG 2.2 checks we run on the scoreboard.

Free scan. No signup. See where you'd rank.

More in Retail & E-commerce