Wayfair wayfair.com
Accessibility score
League position
8thof 10
Issues found
7
Audits passed
46
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalButtons must have discernible text1 element
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.
Failing Elements
<button type="button" data-hb-id="Button" class="_1xrzzea0 _1xrzzea1 _1xrzzea5 _1xrzzea8 _1xrzzeau" style="width:1em;height:1em;vertical-align:middle;transform:translateY(-0.15em)">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
SeriousInteractive elements must have a visible focus indicator10 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Failing Elements
<a class="_1jsqk240" href="#bd">
<button type="button" data-hb-id="Button" data-test-id="header-my-account-a11y-button" class="_1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 ...">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_332587" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_234274" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_42568" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_231579" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_40867" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_41233" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
<button aria-expanded="false" aria-controls="navigation_list_menu_41631" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9..." style="--_16fu6t13y:var(--_8tzu8828)">
SeriousARIA hidden element must not be focusable or contain focusable elements1 element
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.
Failing Elements
<ul aria-hidden="true">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
ModerateDocument 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.
Failing Elements
<html lang="en" class="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
Fix all of the following:
- Document does not have a main landmark
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
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.
Failing Elements
<nav itemscope="" itemtype="https://www.schema.org/SiteNavigationElement">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html lang="en" class="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks3 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.
Failing Elements
<div class="">
Fix any of the following:
- Some page content is not contained by landmarks
<div data-test-id="BlockBuilderCondensedGridSet" data-synthetic-id="HomepageExperienceBlock" class="_16fu6t15w _16fu6t163 n02vza0" style="--_16fu6t15l:0px;--_16fu6t15s:0px">
Fix any of the following:
- Some page content is not contained by landmarks
<div style="width:100%;height:100%">
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits46 across 1 page
<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="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
<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="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
<li> elements must be contained in a <ul> or <ol>27 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="_1y4lots0">
<li class="_1y4lots0"><a class="_2sufqnb _2sufqn7" href="https://www.wayfair.com/curated/new-arrivals~ev568962.html" style="--_2sufqn0:var(--_8tzu885j);--_2sufqn1:var(--_8tzu885p);--_2sufqn2:0.8;--_2sufqn3:default;--_2sufqn4:4px;--_2sufqn5:150ms"><span class="_2sufqnl">New Arrivals</span></a></li>
<li class="_1y4lots0"><a class="_2sufqnb _2sufqn7" href="https://www.wayfair.com/curated/best-sellers~ev565448.html" style="--_2sufqn0:var(--_8tzu885j);--_2sufqn1:var(--_8tzu885p);--_2sufqn2:0.8;--_2sufqn3:default;--_2sufqn4:4px;--_2sufqn5:150ms"><span class="_2sufqnl">Best Sellers</span></a></li>
<li class="_1y4lots0">
<li class="_1y4lots0">
Showing first 5 of 27 audited elements.
<svg> elements with an img or image role must have alternative text12 elements
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 viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 12 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements3 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="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<ul class="cgps5u0 cgps5u2 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<ul class="vxs1ot0">
All page content should be contained by landmarks897 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 class="_1aho13j0 hb-theme-wayfair">
<div class="_1aho13j0 hb-theme-wayfair _1aho13j1">
<div id="header-experience">
<a class="_1jsqk240" href="#bd">Skip to Main Content</a>
<header data-enzyme-id="Header" data-node-id="BlockBuilderHeaderExperience::6722__R_kr5u9llb_" data-tracking-metadata="{"metadata":{},"index":-1,"pageNumber":-1}" id="store_nav" data-synthetic-id="HeaderExperience">Showing first 5 of 897 audited elements.
Alternative text of images should not be repeated as text30 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 alt="" srcset="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg 50w" src="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
<img alt="" srcset="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg 50w" src="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
<img class="_1ak3u0e1 _1ak3u0e2" alt="72-HR Clearout: Up t..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
<img class="_1ak3u0e1 _1ak3u0e2" alt="The Halloween shop, ..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
<img class="_1ak3u0e1 _1ak3u0e2" alt="A dark wood round di..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
Showing first 5 of 30 audited elements.
ARIA attributes must be used as specified for the element's role92 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 aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
<svg focusable="false" viewBox="0 0 24 24" role="img" aria-label="Search" data-hb-id="pl-icon" class="dxfxel0 dxfxel1">
<ul class="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
Showing first 5 of 92 audited elements.
ARIA attributes must conform to valid names92 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 aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
<svg focusable="false" viewBox="0 0 24 24" role="img" aria-label="Search" data-hb-id="pl-icon" class="dxfxel0 dxfxel1">
<ul class="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
Showing first 5 of 92 audited elements.
ARIA attributes must conform to valid values91 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
<button aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
<svg focusable="false" viewBox="0 0 24 24" role="img" aria-label="Search" data-hb-id="pl-icon" class="dxfxel0 dxfxel1">
<ul class="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
Showing first 5 of 91 audited elements.
ARIA commands must have an accessible name18 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div class="_277bgb0 _277bgb1" aria-label="Save" aria-pressed="false" aria-busy="false" aria-disabled="true" aria-invalid="false" role="button">
<div class="_277bgb0 _277bgb1" aria-label="Save" aria-pressed="false" aria-busy="false" aria-disabled="true" aria-invalid="false" role="button">
<div class="_277bgb0 _277bgb1" aria-label="Save" aria-pressed="false" aria-busy="false" aria-disabled="true" aria-invalid="false" role="button">
<div class="_277bgb0 _277bgb1" aria-label="Save" aria-pressed="false" aria-busy="false" aria-disabled="true" aria-invalid="false" role="button">
<div class="_277bgb0 _277bgb1" aria-label="Save" aria-pressed="false" aria-busy="false" aria-disabled="true" aria-invalid="false" role="button">
Showing first 5 of 18 audited elements.
ARIA hidden element must not be focusable or contain focusable elements38 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg focusable="false" viewBox="2 2 24 24" __typename="HomebaseIcon" aria-hidden="true" data-hb-id="pl-icon" data-enzyme-id="HomebaseIcon" class="dxfxel0 dxfxel1 zwpau97">
<svg focusable="false" viewBox="2 2 24 24" __typename="HomebaseIcon" aria-hidden="true" data-hb-id="pl-icon" data-enzyme-id="HomebaseIcon" class="dxfxel0 dxfxel1 zwpau97">
<svg focusable="false" viewBox="2 2 24 24" __typename="HomebaseIcon" aria-hidden="true" data-hb-id="pl-icon" data-enzyme-id="HomebaseIcon" class="dxfxel0 dxfxel1 zwpau97">
<svg focusable="false" viewBox="2 2 24 24" __typename="HomebaseIcon" aria-hidden="true" data-hb-id="pl-icon" data-enzyme-id="HomebaseIcon" class="dxfxel0 dxfxel1 zwpau97">
<svg focusable="false" viewBox="2 2 24 24" __typename="HomebaseIcon" aria-hidden="true" data-hb-id="pl-icon" data-enzyme-id="HomebaseIcon" class="dxfxel0 dxfxel1 zwpau97">
Showing first 5 of 38 audited elements.
ARIA role should be appropriate for the element51 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
<svg viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 51 audited elements.
ARIA roles used must conform to valid values43 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 viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 43 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body>
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
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 data-enzyme-id="Header" data-node-id="BlockBuilderHeaderExperience::6722__R_kr5u9llb_" data-tracking-metadata="{"metadata":{},"index":-1,"pageNumber":-1}" id="store_nav" data-synthetic-id="HeaderExperience">Buttons must have discernible text50 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 aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<button class="_4stjn24 _4stjn25 _4stjn28 _4stjn29 _4stjn2d" type="submit" data-enzyme-id="OutlinedSearchBar-cta">
<button type="button" data-hb-id="Button" data-test-id="header-my-account-a11y-button" class="_1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae"><span class="_1xrzzead _1xrzzeaf _1xrzzeai _1xrzzeaj _1xrzzeam _1xrzzeap">Open Account Dropdown</span></button>
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
<button class="_2sufqnb _2sufqn7" aria-expanded="false" aria-controls="navigation_list_menu_332587" style="--_2sufqn0:var(--_8tzu885j);--_2sufqn1:var(--_8tzu885p);--_2sufqn2:0.8;--_2sufqn3:default;--_2sufqn4:4px;--_2sufqn5:150ms"><span class="_2sufqnl">Trending</span></button>
Showing first 5 of 50 audited elements.
Content must reflow without two-dimensional scrolling1 element
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.
Audit Elements
<li class="_11m1hm12 _11m1hm11">
Deprecated ARIA roles must not be used43 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 viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 43 audited elements.
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 data-enzyme-id="Header" data-node-id="BlockBuilderHeaderExperience::6722__R_kr5u9llb_" data-tracking-metadata="{"metadata":{},"index":-1,"pageNumber":-1}" id="store_nav" data-synthetic-id="HeaderExperience">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="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
Elements marked as presentational should be consistently ignored2 elements
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
<img alt="" srcset="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg 50w" src="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
<img alt="" srcset="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg 50w" src="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
Elements must meet minimum color contrast ratio thresholds92 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-node-id="BlockBuilderMarketin..." data-tracking-metada...="{"metadata":{"linkUr..." href="https://www.wayfair...." data-test-id="HeaderExperience-Mar..." data-hb-id="BoxV3" class="_16fu6t116t _16fu6t1..." style="--_16fu6t116p:inheri..."><a data-node-id="BlockBuilderMarketin..." data-tracking-metada...="{"metadata":{"linkUr..." href="https://www.wayfair...." data-test-id="HeaderExperience-Mar..." data-hb-id="BoxV3" class="_16fu6t116t _16fu6t1..." style="--_16fu6t116p:#fffff..."><a data-node-id="BlockBuilderMarketin..." data-tracking-metada...="{"metadata":{"linkUr..." href="https://www.wayfair...." data-test-id="HeaderExperience-Mar..." data-hb-id="BoxV3" class="_16fu6t116t _16fu6t1..." style="--_16fu6t116p:#fffff..."><button aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
Showing first 5 of 92 audited elements.
Elements must only use permitted ARIA attributes92 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 aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
<svg focusable="false" viewBox="0 0 24 24" role="img" aria-label="Search" data-hb-id="pl-icon" class="dxfxel0 dxfxel1">
<ul class="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
Showing first 5 of 92 audited elements.
Elements must only use supported ARIA attributes92 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 aria-haspopup="dialog" aria-expanded="false" class="ldlmqp0" data-enzyme-id="FreeShippingButton" data-cy-id="FreeShippingButton" style="color:#ffffff" type="button">Fast & Free Shipping Over $35*</button>
<input autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
<svg focusable="false" viewBox="0 0 24 24" role="img" aria-label="Search" data-hb-id="pl-icon" class="dxfxel0 dxfxel1">
<ul class="cgps5u0 cgps5u3 cgps5u4" aria-label="Department Navigation" data-test-id="DropdownLayout-DepartmentNavigation">
<button aria-expanded="false" aria-controls="navigation_list_menu_142247" type="button" data-hb-id="Button" data-test-id="DropdownLayout-TopLevelNavigationGroup-Button" class="_16fu6t149 _1xrzzea0 _1xrzzea2 _1xrzzea6 _1xrzzea9 _1xrzzea8 _1xrzzeab _1xrzzeae" style="--_16fu6t13y:var(--_8tzu8828)">
Showing first 5 of 92 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
<span tabindex="0" class="_1thsbfh0" data-hb-id="VisuallyHidden"> </span>
<span id="bd" tabindex="-1"></span>
Focused elements must not be entirely hidden by author-created content35 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a class="_1jsqk240" href="#bd">
<a title="AllModern" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Birch Lane" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Joss & Main" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Perigold" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
Showing first 5 of 35 audited elements.
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 autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
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 autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
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 autocomplete="off" role="combobox" aria-expanded="false" aria-haspopup="listbox" aria-autocomplete="list" required="" placeholder="Find anything home....." type="search" id="textInput-_R_anl9akr..." aria-labelledby="_R_1qnl9akr5u9llb_" data-enzyme-id="OutlinedSearchBar" name="keyword" ...>
Heading levels should only increase by one12 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h2 data-hb-id="Heading" class="_16fu6t1133 _16fu6t116t _1vbawaw7 _1vbawawf _1vbawawl" style="--_16fu6t112s:left;--_16fu6t116p:inherit">
<h2 data-hb-id="Heading" class="_16fu6t1133 _16fu6t116t _1vbawaw7 _1vbawawf _1vbawawl" style="--_16fu6t112s:left;--_16fu6t116p:inherit">
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Chiara Farmhouse TV Stand</h2>
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Otero Plush Memory Foam Mattress</h2>
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Glenlee 700GSM Long Staple Combed Cotton 6-Piece Towel Set</h2>
Showing first 5 of 12 audited elements.
Headings should not be empty12 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h2 data-hb-id="Heading" class="_16fu6t1133 _16fu6t116t _1vbawaw7 _1vbawawf _1vbawawl" style="--_16fu6t112s:left;--_16fu6t116p:inherit">
<h2 data-hb-id="Heading" class="_16fu6t1133 _16fu6t116t _1vbawaw7 _1vbawawf _1vbawawl" style="--_16fu6t112s:left;--_16fu6t116p:inherit">
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Chiara Farmhouse TV Stand</h2>
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Otero Plush Memory Foam Mattress</h2>
<h2 data-hb-id="Text" data-test-id="ListingCard-ListingCardName-Text" data-name-id="ListingCardName" class="_16fu6t1bl _16fu6t116t jbgopv1" style="--_16fu6t1ba:var(--_8tzu8885);--_16fu6t116p:var(--_8tzu885j);--jbgopv0:2">Glenlee 700GSM Long Staple Combed Cotton 6-Piece Towel Set</h2>
Showing first 5 of 12 audited elements.
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 id="_R_1qnl9akr5u9llb_" class="gsqsd2w" data-enzyme-id="OutlinedSearchBar-label-label-text">Search</span>
<span id="_R_tbrdakr5u9llb_" class="gsqsd2w" data-enzyme-id="OutlinedSearchBar-label-label-text">Search</span>
Images must have alternative text30 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 alt="" srcset="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg 50w" src="https://assets.wfcdn.com/im/77645905/resize-h50-w50%5Ecompr-r85/3382/338242703/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
<img alt="" srcset="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg 50w" src="https://assets.wfcdn.com/im/52466148/resize-h50-w50%5Ecompr-r85/3675/367574113/default_name.jpg" sizes="50px" data-hb-id="FluidImage" class="_1y0fmcs0">
<img class="_1ak3u0e1 _1ak3u0e2" alt="72-HR Clearout: Up t..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
<img class="_1ak3u0e1 _1ak3u0e2" alt="The Halloween shop, ..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
<img class="_1ak3u0e1 _1ak3u0e2" alt="A dark wood round di..." src="https://assets.wfcdn..." srcset="https://assets.wfcdn..." sizes="">
Showing first 5 of 30 audited elements.
Inline text spacing must be adjustable with custom stylesheets355 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
<div class="_11zhovu1" style="--_11zhovu0:var(--_8tzu883y)">
<div style="background-color:#7B189F;--_7ctzu01:0px;--_7ctzu02:var(--_8tzu8816)" class="_7ctzu04" data-enzyme-id="MarketingBanner">
<div data-hb-id="Wrapper" class="_16fu6t14v _16fu6t15h _2m4tdc0 _2m4tdc1" style="--_16fu6t14k:auto;--_16fu6t156:auto">
<div class="_7ctzu06" style="--_7ctzu00:5fr 8fr">
<div class="_1lnrhv34" style="--_1lnrhv30:unset;--_1lnrhv31:start;--_1lnrhv33:16px">
Showing first 5 of 355 audited elements.
Interactive controls must not be nested109 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 viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 109 audited elements.
Interactive elements must have a visible focus indicator25 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a title="AllModern" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Birch Lane" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Joss & Main" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Perigold" href="https://www.wayfair.com/handover.php?from_store=49..." data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a data-node-id="BlockBuilderMarketingLink::100096__R_1l5akr5u9llb_" data-tracking-metadata="{"metadata":{"linkUrl":"h..." href="https://www.wayfair.com/wayfair-rewards" data-test-id="HeaderExperience-MarketingLink" data-hb-id="BoxV3" class="_16fu6t116t _16fu6t118d _16fu6t11...Showing first 5 of 25 audited elements.
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 data-enzyme-id="Header" data-node-id="BlockBuilderHeaderExperience::6722__R_kr5u9llb_" data-tracking-metadata="{"metadata":{},"index":-1,"pageNumber":-1}" id="store_nav" data-synthetic-id="HeaderExperience"><form class="_1nlquxi0" name="keyword" role="search" data-clio-id="Search::_R_1l9akr5u9llbH1_" data-clio-signals="click,in_view" action="/keyword.php" method="get">
Links must have discernible text66 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="_1jsqk240" href="#bd">Skip to Main Content</a>
<a title="AllModern" href="https://www.wayfair.com/handover.php?from_store=49&url=%2F&to_store=81" data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Birch Lane" href="https://www.wayfair.com/handover.php?from_store=49&url=%2F&to_store=422" data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Joss & Main" href="https://www.wayfair.com/handover.php?from_store=49&url=%2F&to_store=450" data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
<a title="Perigold" href="https://www.wayfair.com/handover.php?from_store=49&url=%2F&to_store=457" data-enzyme-id="StoreLogoLink" class="_2srr0x1" target="_blank" rel="noreferrer">
Showing first 5 of 66 audited elements.
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="hb-theme-wayfair" data-app-name="@wayfair/sf-ui-core-funnel">
Required ARIA attributes must be provided43 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 viewBox="0 0 629.52 150" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 585.1 62.1" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 500 76" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 1398.13 194.87" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
<svg viewBox="0 0 504.6 60" fill="#FFFFFF" xmlns="http://www.w3.org/2000/svg" role="img" height="100%" width="100%" class="_16fu6t1140 _16fu6t11b2 _16fu6t116g _16fu6t1df" style="--_16fu6t11b1:middle;--_16fu6t1d4:100%">
Showing first 5 of 43 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div aria-live="polite" role="group" aria-label="Items Scroller" class="_16fu6t1nj _16fu6t1n..." style="--_16fu6t1n8:calc(10...">
The skip-link target should exist and be focusable1 element
Skip links allow keyboard users to bypass repetitive navigation and jump directly to main content. Without skip links, users must tab through potentially hundreds of navigation links on every page, which is time-consuming and can cause physical pain for users with motor limitations.
Audit Elements
<a class="_1jsqk240" href="#bd">Skip to Main Content</a>
Users should be able to zoom and scale the text up to 500%2 elements
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">
<meta id="viewport" name="viewport" content="initial-scale=1.0, maximum-scale=5.0, width=device-width">
Zooming and scaling must not be disabled2 elements
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">
<meta id="viewport" name="viewport" content="initial-scale=1.0, maximum-scale=5.0, width=device-width">
How does your site stack up against Wayfair?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Retail & E-commerce
