Walmart walmart.com
Accessibility score
League position
3rdof 10
Issues found
1
Audits passed
33
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousInteractive elements must have a visible focus indicator4 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 link-identifier="Generic Name" class="no-underline db br3" data-testid="visual-nav-link" aria-label="Beauty" data-dca-aid="L:7D7166B3B0" href="https://www.walmart.com/shop/deals/top-100-beauty">
<a link-identifier="Generic Name" class="no-underline db br3" data-testid="visual-nav-link" aria-label="Tech" data-dca-aid="L:7D7166B3B0" href="https://www.walmart.com/shop/deals/electronics">
<a link-identifier="Generic Name" class="no-underline db br3" data-testid="visual-nav-link" aria-label="Toys" data-dca-aid="L:7D7166B3B0" href="https://www.walmart.com/shop/deals/toys">
<a link-identifier="Generic Name" class="no-underline db br3" data-testid="visual-nav-link" aria-label="Auto" data-dca-aid="L:7D7166B3B0" href="https://www.walmart.com/shop/deals/auto">
Passed audits33 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-US">
<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-US">
Accessible names must not be code or placeholder text2 elements
Screen reader users hear a control's accessible name in place of what sighted users see. When the name is a class name like "quantity-selector", a script value like "undefined" or an unrendered template like "{{title}}", they hear noise and cannot tell what the control does. Every check that only asks whether a name exists passes these, because the name is there.
Audit Elements
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
All page content should be contained by landmarks22 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="__next">
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div>
<div data-testid="dialog-modal" class="">
Showing first 5 of 22 audited elements.
All touch targets must be 24px large, or leave sufficient space1 element
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
ARIA attributes must be used as specified for the element's role4 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
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
ARIA attributes must conform to valid names4 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
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
ARIA attributes must conform to valid values4 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
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
ARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Audit Elements
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
ARIA hidden element must not be focusable or contain focusable elements147 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
<script id="__NEXT_DATA__" type="application/json" nonce="" aria-hidden="true">
<script id="release-metadata" type="application/json" nonce="" aria-hidden="true">{"appVersion":"usweb-1.326.7-9a0c1c5471c678e0566691ed2c3502439fa0a7b3-O61131r","dataCenter":"eus2"}</script><noscript aria-hidden="true"><img src="https://www.walmart.com/akam/13/pixel_45c5d799?a=dD02NWEzYmVlMzg0YTBiZDQzZjBmMGRmNjgxNzVmYmVjNjEwYTFkZmNhJmpzPW9mZg==" style="visibility: hidden; position: absolute; left: -999px; top: -999px;" /></noscript>
<iframe name="q7k2m8010129" aria-hidden="true" tabindex="-1" style="display: none;"></iframe>
<iframe src="https://js.crcldu.co..." data-frame-token="d-kwnzc5fml-17947082..." referrerpolicy="strict-origin-when-c..." aria-hidden="true" tabindex="-1" role="presentation" title="" style="position: absolute; ...">
Showing first 5 of 147 audited elements.
ARIA role should be appropriate for the element34 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
<form action="/search" autocomplete="off" aria-label="Walmart Site-Wide" role="search" class="flex flex-auto items-center justify-center pl3 justify-start-hdkp pa0-hdkp ml4-hdkp static" data-testid="search-form">
<input aria-label="Search" role="combobox" aria-expanded="false" aria-controls="typeahead-listbox" class="flex-auto lh-solid s..." name="q" placeholder="Search everything at..." type="search" aria-autocomplete="list" aria-haspopup="listbox" autocomplete="off" value="" ...>
<a link-identifier="Reorder my items" class="flex items-center no..." aria-haspopup="true" aria-expanded="false" data-dca-name="Reorder my items" role="button" data-dca-aid="L:87A208F9E9" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" href="/my-items" ...>
<a link-identifier="Account" class="flex items-center no..." aria-haspopup="true" aria-expanded="false" data-dca-name="Account" role="button" data-dca-aid="L:87A208F9E9" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" href="https://identity.wal..." ...>
<a link-identifier="horizontalScrollerNext" class="z-5 bg-white br-100 pa0 pointer db" aria-label="Next carousel card" data-testid="horizontal-scroller-next" tabindex="0" role="button" data-dca-aid="L:E0344097FE" data-dca-intent="swipeRight" data-dca-verb="unknown">
Showing first 5 of 34 audited elements.
ARIA roles used must conform to valid values1 element
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
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
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 style="overflow: hidden;">
Buttons 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.
Audit Elements
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
Deprecated ARIA roles must not be used1 element
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
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
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-US">
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-US">
Elements must meet minimum color contrast ratio thresholds40 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
<span class="b f5">Pickup or delivery?</span>
<input aria-label="Search" role="combobox" aria-expanded="false" aria-controls="typeahead-listbox" class="flex-auto lh-solid s..." name="q" placeholder="Search everything at..." type="search" aria-autocomplete="list" aria-haspopup="listbox" autocomplete="off" value="" ...>
<button class="ld_i ld_k ld_o f5 hover-bg-navy" type="button" data-dca-aid="B:E8F169852A" data-dca-intent="open" style="height: 52px;">
<div class="lh-title f6" style="height: 20px;">Reorder</div>
<div class="b f5 lh-copy" style="margin-top: -4px;">My Items</div>
Showing first 5 of 40 audited elements.
Elements must only use permitted ARIA attributes4 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
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
Elements must only use supported ARIA attributes4 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
<span class="ld_Ec" aria-live="assertive" data-live-announcer="true"></span>
<span class="ld_Ec" aria-live="polite" data-live-announcer="true"></span>
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
<button aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
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
<div data-focus-guard="true" tabindex="0" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div data-focus-guard="true" tabindex="0" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
Focused elements must not be entirely hidden by author-created content34 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
<div id="px-captcha" class="flex justify-center" style="display: block; min-width: 310px;">
<a link-identifier="Generic Name" class="slider skip-main bg-white-90" data-dca-aid="L:E76549B6E8" data-dca-intent="select" href="#maincontent">
<a link-identifier="walmartLogoDesktop" class="header-navigation flex-hdkp items-center no-underl..." aria-label="Walmart Homepage" data-dca-aid="L:B3A89AD3F3" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" href="/" style="border-radius: 37px; transition: 100ms cubic-bezie.....
<input aria-label="Search" role="combobox" aria-expanded="true" aria-controls="typeahead-listbox" class="flex-auto lh-solid sans-serif search-bar f5 search..." name="q" placeholder="Search everything at Walmart online and in store" type="search" aria-autocomplete="list" aria-haspopup="listbox" autoc...
<button aria-label="Search" class="absolute bn br-100 hover-bg-navy search-icon-redes..." data-dca-aid="B:961A365941" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" style="cursor: pointer;">
Showing first 5 of 34 audited elements.
Heading levels should only increase by one1 element
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 class="ld_E4 ld_E8 ld_E6 ld_G4" id="react-aria1378021314-:r1:">Robot or human?</h2>
Headings should not be empty1 element
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 class="ld_E4 ld_E8 ld_E6 ld_G4" id="react-aria1378021314-:r1:">Robot or human?</h2>
IDs used in ARIA and labels must be unique77 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
<a link-identifier="" class="absolute fill-focus ..." title="Black Friday Deals a..." id="linkcard--PrismAdjus..." aria-labelledby="linkcard--PrismAdjus..." aria-hidden="false" tabindex="0" data-dca-aid="L:F24E6BF757" data-dca-intent="select" data-dca-verb="unknown" ...>
<p class="b f2 f10-hdkp lh-105 ma0 w-100" id="heading-PrismAdjustableCardCarousel-contentZone3--card-1" style="color: rgb(255, 255, 255); margin-bottom: 0px;">Up to 30% off holiday musts</p>
<a link-identifier="Shop Deals" class="z-2 relative nowrap ..." id="link-ShopDeals-Prism..." aria-labelledby="link-ShopDeals-Prism..." data-dca-intent="select" data-dca-aid="L:FC6DB059E6" data-dca-verb="unknown" data-dca-extras="{"ids":{"containerId..." href="https://www.walmart...." ...><a link-identifier="Shop Deals" class="absolute fill-focus ..." title="Red stand mixer on b..." id="linkcard-ShopDeals-P..." aria-labelledby="linkcard-ShopDeals-P..." aria-hidden="true" tabindex="-1" data-dca-aid="L:F24E6BF757" data-dca-intent="select" data-dca-verb="unknown" ...>
<p class="b f2 f10-hdkp lh-105 ma0 w-100" id="heading-PrismAdjustableCardCarousel-contentZone3--card-2" style="color: rgb(255, 255, 255); margin-bottom: 0px;">You’re invited: Deals on hosting</p>
Showing first 5 of 77 audited elements.
Inline text spacing must be adjustable with custom stylesheets1 element
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
<body style="overflow: hidden;">
Interactive controls must not be nested1 element
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 aria-label="Close dialog" class="ld_A7 ld_A9 ld_BB" type="button" data-dca-aid="ui_dialog:close_button" data-dca-intent="close" data-dca-name="ItemUnnamedDialogCloseButton">
Interactive elements must have a visible focus indicator37 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
<div id="px-captcha" class="flex justify-center" style="display: block; min-width: 310px;">
<a link-identifier="Generic Name" class="slider skip-main bg-white-90" data-dca-aid="L:E76549B6E8" data-dca-intent="select" href="#maincontent">
<a link-identifier="walmartLogoDesktop" class="header-navigation flex-hdkp items-center no-underl..." aria-label="Walmart Homepage" data-dca-aid="L:B3A89AD3F3" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" href="/" style="border-radius: 37px; transition: 100ms cubic-bezie.....
<input aria-label="Search" role="combobox" aria-expanded="true" aria-controls="typeahead-listbox" class="flex-auto lh-solid sans-serif search-bar f5 search..." name="q" placeholder="Search everything at Walmart online and in store" type="search" aria-autocomplete="list" aria-haspopup="listbox" autoc...
<button aria-label="Search" class="absolute bn br-100 hover-bg-navy search-icon-redes..." data-dca-aid="B:961A365941" data-dca-intent="__DCA_INTENT_TBD__" data-dca-event="__DCA_EVENT_TBD__" style="cursor: pointer;">
Showing first 5 of 37 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-US">
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-US">
Required ARIA attributes must be provided1 element
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
<div class="ld_Gv ld_Gw" role="dialog" aria-labelledby="react-aria1378021314-:r1:">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1, interactive-widget=resizes-content">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1, interactive-widget=resizes-content">
How does your site stack up against Walmart?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Retail & E-commerce