Skip to main content

Web Accessibility Scoreboard

by A11y Pulse

How accessible is the web you use every day? We scan hundreds of popular websites and rate each one with an accessibility score out of 100.

Get an instant accessibility score for your site.

Back to scoreboard

Wayfairwayfair.com

Screenshot of Wayfair

Accessibility Score

70Needs Improvement

Issues Found

41Serious3Moderate

Issues Found

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

Failing Elements

.px-captcha-refid
<div class="px-captcha-refid">Reference ID 92024da9-41e5-11f1-bf16-fb36fdb55677</div>

Fix any of the following:

  • Element has insufficient color contrast of 1.99 (foreground color: #b1b5b8, background color: #fafbfc, font size: 7.5pt (10px), font weight: normal). Expected contrast ratio of 4.5:1
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

Failing Elements

html
<html lang="en">

Fix all of the following:

  • Document does not have a main landmark
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
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

Failing Elements

#px-captcha-wrapper
<div id="px-captcha-wrapper" dir="auto">

Fix any of the following:

  • Some page content is not contained by landmarks

Passed Audits

<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

.px-captcha-container
<div class="px-captcha-container">
.px-captcha-header
<div class="px-captcha-header">Before we continue...</div>
.px-captcha-message
<div class="px-captcha-message">Press &amp; Hold to confirm you are<br>a human (and not a bot).</div>
br
<br>
#px-captcha
<div id="px-captcha"><div id="px-loader" class="px-loader-wrapper"><div class="px-loading-area" style="margin: auto;"><div class="px-inner-loading-area"></div></div></div></div>
#px-loader
<div id="px-loader" class="px-loader-wrapper"><div class="px-loading-area" style="margin: auto;"><div class="px-inner-loading-area"></div></div></div>
.px-loading-area
<div class="px-loading-area" style="margin: auto;"><div class="px-inner-loading-area"></div></div>
.px-inner-loading-area
<div class="px-inner-loading-area"></div>
.px-captcha-refid
<div class="px-captcha-refid">Reference ID 92024da9-41e5-11f1-bf16-fb36fdb55677</div>
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>
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

.px-captcha-header
<div class="px-captcha-header">Before we continue...</div>
.px-captcha-message
<div class="px-captcha-message">Press &amp; Hold to confirm you are<br>a human (and not a bot).</div>
Inline text spacing must be adjustable with custom stylesheets

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.

Learn more

Audit Elements

.px-loading-area
<div class="px-loading-area" style="margin: auto;"><div class="px-inner-loading-area"></div></div>
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">

Browse results by category