The Home Depot homedepot.com
Accessibility score
League position
9thof 10
Issues found
10
Audits passed
43
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements must meet minimum color contrast ratio thresholds5 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.
Failing Elements
<span>#1 Home Improvement Retailer</span>
Fix any of the following:
- Element has insufficient color contrast of 3.08 (foreground color: #ffffff, background color: #f96302, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/auth/view/signin?fr..." class="sui-btn sui-btn-prim..." data-testid="button-component-sig...">
Fix any of the following:
- Element has insufficient color contrast of 3.08 (foreground color: #ffffff, background color: #f96302, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/daily-deals" class="sui-btn sui-btn-primary sui-btn-primary-focus sui-w-full sui-btn-primary-active sui-btn-primary-hover sui-font-bold sui-text-base sui-leading-normal sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-font-normal">Shop All Savings</a>
Fix any of the following:
- Element has insufficient color contrast of 3.08 (foreground color: #ffffff, background color: #f96302, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/kids" class="sui-btn sui-btn-secondary sui-btn-secondary-focus sui-w-full sui-btn-secondary-active sui-btn-secondary-hover sui-font-bold sui-text-base sui-leading-normal sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-font-normal">Register Now</a>
Fix any of the following:
- Element has insufficient color contrast of 3.08 (foreground color: #f96302, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<button type="button" class="sui-btn sui-btn-prim..." id="footer-email-button" data-testid="footer-email-button">
Fix any of the following:
- Element has insufficient color contrast of 3.08 (foreground color: #ffffff, background color: #f96302, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousElements must have their visible text as part of their accessible name4 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
Fix any of the following:
- Text inside the element is not included in the accessible name
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
Fix any of the following:
- Text inside the element is not included in the accessible name
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Fix any of the following:
- Text inside the element is not included in the accessible name
<button type="button" class="focus-visible:sui-ou..." data-testid="header-button-Accoun..." aria-label="open drawer to view ...">
Fix any of the following:
- Text inside the element is not included in the accessible name
SeriousForm 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.
Failing Elements
<input type="email" aria-invalid="false" aria-describedby="footer-email-input-m..." autocomplete="off" class="sui-input-base-input..." id="footer-email-input" placeholder="Enter Email Address" required="" style="font:inherit;letter-..." data-testid="footer-email-input">
Fix all of the following:
- Only title used to generate label for form element
SeriousAll touch targets must be 24px large, or leave sufficient space3 elements
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.
Failing Elements
<a class="sui-ml-1 md:sui-underline" href="/c/California_Supply_Chain_Act" title="California Supply Chain Act" alt="California Supply Chain Act">California Supply Chain Act</a>
Fix any of the following:
- Target has insufficient size (147.3px by 15px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 18.8px instead of at least 24px.
<a class="sui-hidden md:sui-block sui-ml-1 md:sui-underline" href="/c/site_map" title="Site Map" alt="Site Map">Site Map</a>
Fix any of the following:
- Target has insufficient size (48px by 7.5px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.6px instead of at least 24px.
<a class="sui-hidden md:sui-block sui-ml-1 md:sui-underline" href="/l/storeDirectory" title="Store Directory" alt="Store Directory">Store Directory</a>
Fix any of the following:
- Target has insufficient size (80.5px by 7.5px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.6px instead of at least 24px.
SeriousText must remain readable when spacing is increased3 elements
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.
Failing Elements
<p class="sui-font-regular sui-min-fit sui-leading-tight sui...">
<p class="sui-font-regular sui-min-fit sui-leading-tight sui...">
<p class="sui-font-regular sui-min-fit sui-leading-tight sui...">
ModerateHeading 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.
Failing Elements
<h5 class="sui-h5-bold sui-line-clamp-3 sui-font-normal sui-text-primary">Appliances</h5>
Fix any of the following:
- Heading order invalid
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">
Fix all of the following:
- Document does not have a main landmark
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">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks45 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>
Fix any of the following:
- Some page content is not contained by landmarks
<span class="sui-grow"><p class="sui-font-bold sui-text-base sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-font-normal sui-text-primary">Sign in for the best experience</p></span>
Fix any of the following:
- Some page content is not contained by landmarks
<section class="sui-mt-1 sui-mb-3">
Fix any of the following:
- Some page content is not contained by landmarks
<section class="sui-flex sui-gap-4 lg:sui-w-96">
Fix any of the following:
- Some page content is not contained by landmarks
<div data-testid="header-adaptive-ui-primary" class="lg:sui-block lg:sui-visible lg:sui-opacity-100 lg:sui-static sui-visible">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="swiper-wrapper" id="swiper-wrapper-7f3598f4d31098978" aria-live="off">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="bento-hero-sponsored-content-wrapper sui-col-span-12 lg:sui-col-span-12 sui-order-2 lg:sui-order-3 lg:sui-cols-4 sui-w-full bento-clip-path-rounded">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="sui-col-span-12 lg:sui-col-span-4 sui-order-3 lg:sui-order-2 lg:sui-aspect-[1.8/1] sui-w-full sui-h-full bento-clip-path-rounded">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="sui-col-span-12 lg:sui-col-span-8 sui-order-5 lg:sui-aspect-[3.6/1] sui-w-full sui-h-full bento-clip-path-rounded">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="sui-col-span-12 lg:sui-col-span-4 sui-order-4 lg:sui-aspect-[1.8/1] sui-w-full sui-h-full bento-clip-path-rounded">
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 45 failing elements.
MinorAlternative text of images should not be repeated as text3 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.
Failing Elements
<img class="sui-object-cover sui..." src="https://dam.thdstati..." alt="Appliances" title="Appliances" loading="lazy" data-contentful-entr...="" data-contentful-fiel...="previewImage">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="sui-object-cover sui..." src="https://dam.thdstati..." alt="Home Decor" title="Home Decor" loading="lazy" data-contentful-entr...="" data-contentful-fiel...="previewImage">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="sui-object-cover sui..." src="https://dam.thdstati..." alt="Outdoor Power" title="Outdoor Power" loading="lazy" data-contentful-entr...="" data-contentful-fiel...="previewImage">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
Passed audits43 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">
<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">
<li> elements must be contained in a <ul> or <ol>61 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="sui-text-sm sui-mb-2 sui-underline"><a alt="Customer Service Center" href="/c/customer_service" title="Customer Service Center">Customer Service Center</a></li>
<li class="sui-text-sm sui-mb-2 sui-underline"><a alt="Check Order Status" href="/myaccount/guest-order-tracking" title="Check Order Status">Check Order Status</a></li>
<li class="sui-text-sm sui-mb-2 sui-underline"><a alt="Pickup, Shipping & Delivery" href="/c/delivery" title="Pickup, Shipping & Delivery">Pickup, Shipping & Delivery</a></li>
<li class="sui-text-sm sui-mb-2 sui-underline"><a alt="Pay Your Credit Card" href="/c/credit-center" title="Pay Your Credit Card">Pay Your Credit Card</a></li>
<li class="sui-text-sm sui-mb-2 sui-underline"><a alt="Order Cancellation" href="/c/Customer_Support_Answers#cancel" title="Order Cancellation">Order Cancellation</a></li>
Showing first 5 of 61 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements5 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="sui-flex sui-flex-col sui-flex-wrap sui-list-none sui-justify-center">
<ul class="sui-flex sui-flex-col sui-flex-wrap sui-list-none sui-justify-center">
<ul class="sui-flex sui-flex-col sui-flex-wrap sui-list-none sui-justify-center">
<ul class="sui-flex sui-flex-row sui-flex-wrap sui-justify-center sui-list-none sui-p-2 sui-p-2px">
<ul class="sui-flex sui-flex-wrap sui-gap-2 sui-leading-3 sui-text-xs sui-text-primary sui-list-none sui-justify-center">
All page content should be contained by landmarks985 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="hfapp" style="display:contents" data-reactroot="">
<div id="header-static" style="display:contents">
<div id="header-tophat" class="sui-relative sui-z-t..." data-component="HeaderTopHat">
<div id="messageBar" class="MessageBar" style="position:static"><span>#1 Home Improvement Retailer</span></div>
<span>#1 Home Improvement Retailer</span>
Showing first 5 of 985 audited elements.
All touch targets must be 24px large, or leave sufficient space129 elements
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 class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<a data-testid="header-thd-logo" href="/">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 129 audited elements.
Alternative text of images should not be repeated as text42 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 src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="Quickly Create Lists..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="high" width="1" height="1">
<img class="_sponsored_banner_image_11fr4_5" alt="sponsored banner" src="https://dam.thdstatic.com/contentful/heroflattenimage/18OCT26-SWB-Gifting-DSK.png">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="Up to 50% off select..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="low" width="1" height="1">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="October2026 Tools" class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="low" width="1" height="1">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="26October2026 Elevat..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="high" width="1" height="1">
Showing first 5 of 42 audited elements.
ARIA attributes must be used as specified for the element's role56 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<svg class="sui-w-11 lg:sui-w-16" aria-label="The Home Depot Logo" viewBox="0 0 64 64" fill="none" xmlns="http://www.w3.org/2000/svg">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 56 audited elements.
ARIA attributes must conform to valid names56 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<svg class="sui-w-11 lg:sui-w-16" aria-label="The Home Depot Logo" viewBox="0 0 64 64" fill="none" xmlns="http://www.w3.org/2000/svg">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 56 audited elements.
ARIA attributes must conform to valid values56 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 class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<svg class="sui-w-11 lg:sui-w-16" aria-label="The Home Depot Logo" viewBox="0 0 64 64" fill="none" xmlns="http://www.w3.org/2000/svg">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 56 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 class="sui-inline-block sui-shrink-0 sui-w-4 sui-h-4 sui-fill-brand" viewBox="0 0 45 52" focusable="false" aria-hidden="true" data-testid="MagicApronIcon">
<svg class="sui-inline-block sui-align-baseline sui-fill-inherit sui-w-4 sui-h-4" viewBox="0 0 24 24" focusable="false" aria-hidden="true" data-testid="CardCvvIcon">
<svg class="sui-inline-block sui-align-baseline sui-fill-inherit sui-w-6 sui-h-6" viewBox="0 0 24 24" focusable="false" aria-hidden="true" data-testid="ArrowBackIcon"><path d="M18.729 1.604 8.444 12l10.284 10.396-1.6 1.582L5.28 12 17.13.02l1.6 1.583Z"></path></svg>
<svg class="sui-inline-block sui-align-baseline sui-fill-inherit sui-w-4 sui-h-4" viewBox="0 0 24 24" focusable="false" aria-hidden="true" data-testid="StoreIcon">
<svg class="sui-inline-block sui-align-baseline sui-fill-inherit sui-w-4 sui-h-4" viewBox="0 0 24 24" focusable="false" aria-hidden="true" data-testid="DeliveryIcon">
Showing first 5 of 38 audited elements.
ARIA role should be appropriate for the element7 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
<input type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<ul class="sui-list-none sui-m-0 sui-px-0 sui-relative" role="listbox" tabindex="-1" id="results-listbox" data-testid="results-listbox"></ul>
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
<div class="swiper-slide sui-shrink-0 [&>*]:sui-h-full sui-touch-pan-y swiper-slide-active" role="group" aria-label="1 / 1" style="width: 800px; margin-right: 16px;">
<span class="sui-swiper-pagination-bullet-core sui-swiper-pagination-bullet-actives sui-swiper-pagination-bullet-actives-main" tabindex="0" role="button" aria-label="Go to slide 1" aria-current="true" style="left: 0px;"></span>
Showing first 5 of 7 audited elements.
ARIA roles used must conform to valid values4 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<input type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
<div class="swiper-slide sui-shrink-0 [&>*]:sui-h-full sui-touch-pan-y swiper-slide-active" role="group" aria-label="1 / 1" style="width: 800px; margin-right: 16px;">
<svg class="sui-fill-brand" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 45 52" height="50%" width="24px" fill="none" role="presentation" data-component="magic-apron:AssistantIcon:v5.4.1" style="min-width: 24px; margin: 2px;">
ARIA tooltip nodes must have an accessible name1 element
Screen reader users cannot understand the purpose of role="tooltip" elements without an accessible name. The name provides the essential context or help text that the tooltip is meant to convey.
Audit Elements
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
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 correctly2 elements
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 type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<input type="email" aria-invalid="false" aria-describedby="footer-email-input-m..." autocomplete="off" class="sui-input-base-input..." id="footer-email-input" placeholder="Enter Email Address" required="" style="font:inherit;letter-..." data-testid="footer-email-input">
Buttons must have discernible text13 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
<button type="button" class="sui-btn sui-btn-prim..." aria-label="Search Field Icon" id="typeahead-search-ico..." color="primary">
Showing first 5 of 13 audited elements.
Content must reflow without two-dimensional scrolling0 elements
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.
Deprecated ARIA roles must not be used4 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<input type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
<div class="swiper-slide sui-shrink-0 [&>*]:sui-h-full sui-touch-pan-y swiper-slide-active" role="group" aria-label="1 / 1" style="width: 800px; margin-right: 16px;">
<svg class="sui-fill-brand" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 45 52" height="50%" width="24px" fill="none" role="presentation" data-component="magic-apron:AssistantIcon:v5.4.1" style="min-width: 24px; margin: 2px;">
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">
Elements marked as presentational should be consistently ignored1 element
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
<svg class="sui-fill-brand" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 45 52" height="50%" width="24px" fill="none" role="presentation" data-component="magic-apron:AssistantIcon:v5.4.1" style="min-width: 24px; margin: 2px;">
Elements must have their visible text as part of their accessible name4 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<button type="button" class="focus-visible:sui-ou..." data-testid="header-button-Shop A..." aria-label="open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-button-Servic..." aria-label="open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-button-DIY" aria-label="open drawer to view ...">
<a href="/cart" class="sui-flex sui-items-center sui-text-center hover:sui-fill-brand hover:sui-no-underline hover:sui-text-brand sui-flex-col sui-w-16 sui-fill-primary" data-testid="header-cart-icon" data-component="HeaderCartIcon" aria-label="Click to redirect to view my cart page">
Elements must meet minimum color contrast ratio thresholds130 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="sui-text-ellipsis">Ask Magic Apron</span>
<p class="sui-font-regular sui-min-fit sui-leading-tight sui-truncate sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-mt-0 sui-text-sm">Home Depot Credit Cards</p>
<p class="sui-font-regular sui-min-fit sui-leading-tight sui-truncate sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-mt-0 sui-text-base sui-max-w-[12.8rem] lg:sui-max-w-[8.9rem]">Santa Clara</p>
<p class="sui-font-bold sui-text-base sui-leading-normal sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-font-normal sui-text-danger">6AM</p>
<p class="sui-font-regular sui-min-fit sui-leading-tight sui-truncate sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-mt-0 sui-text-base">95050</p>
Showing first 5 of 130 audited elements.
Elements must only use permitted ARIA attributes56 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<svg class="sui-w-11 lg:sui-w-16" aria-label="The Home Depot Logo" viewBox="0 0 64 64" fill="none" xmlns="http://www.w3.org/2000/svg">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 56 audited elements.
Elements must only use supported ARIA attributes56 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<svg class="sui-w-11 lg:sui-w-16" aria-label="The Home Depot Logo" viewBox="0 0 64 64" fill="none" xmlns="http://www.w3.org/2000/svg">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
Showing first 5 of 56 audited elements.
Elements should not have tabindex greater than zero25 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
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<div tabindex="-1" data-testid="sentinelStart" style="transition: opacity 225ms cubic-bezier(0.4, 0, 0.2, 1);"></div>
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-label="close">
<div tabindex="-1" data-testid="sentinelEnd"></div>
<a class="sui-lab-btn-base sui-block sui-text-inherit sui-w-full sui-h-full sui-focus-outline focus-visible:sui-rounded-md" tabindex="0" href="https://www.homedepot.com/c/appliance-sales">
Showing first 5 of 25 audited elements.
Focused elements must not be entirely hidden by author-created content49 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
<button class="sui-lab-btn-base sui-font-regular sui-text-sm sui-..." tabindex="0" type="button" aria-controls="magic-apron-assistant-drawer" data-testid="header-b2c-magic-apron" aria-expanded="false">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="header-b2c-credit-service" aria-label="Click to redirect to credit service page">
<a data-testid="header-thd-logo" href="/">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view my store">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to update zip code">
Showing first 5 of 49 audited elements.
Form elements must have labels2 elements
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 type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<input type="email" aria-invalid="false" aria-describedby="footer-email-input-m..." autocomplete="off" class="sui-input-base-input..." id="footer-email-input" placeholder="Enter Email Address" required="" style="font:inherit;letter-..." data-testid="footer-email-input">
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 type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
Form field must not have multiple label elements2 elements
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 type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<input type="email" aria-invalid="false" aria-describedby="footer-email-input-m..." autocomplete="off" class="sui-input-base-input..." id="footer-email-input" placeholder="Enter Email Address" required="" style="font:inherit;letter-..." data-testid="footer-email-input">
Heading levels should only increase by one20 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
<h3 class="sui-h3-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Top Categories</h3>
<h3 class="sui-h3-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Today's Big Savings All in One Place</h3>
<h2 class="sui-h2-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Top Picks</h2>
<h5 class="sui-h5-bold sui-line-clamp-3 sui-font-normal sui-text-primary">Home Decor</h5>
<h5 class="sui-h5-bold sui-line-clamp-3 sui-font-normal sui-text-primary">Heating, Venting & Cooling</h5>
Showing first 5 of 20 audited elements.
Headings should not be empty21 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
<h3 class="sui-h3-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Top Categories</h3>
<h3 class="sui-h3-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Today's Big Savings All in One Place</h3>
<h2 class="sui-h2-bold sui-line-clamp-unset sui-font-normal sui-text-primary">Top Picks</h2>
<h5 class="sui-h5-bold sui-line-clamp-3 sui-font-normal sui-text-primary">Appliances</h5>
<h5 class="sui-h5-bold sui-line-clamp-3 sui-font-normal sui-text-primary">Home Decor</h5>
Showing first 5 of 21 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
<ul class="sui-list-none sui-m-0 sui-px-0 sui-relative" role="listbox" tabindex="-1" id="results-listbox" data-testid="results-listbox"></ul>
<p class="sui-font-regular sui-mt-1 sui-text-xs sui-leading-none sui-text-left" id="footer-email-input-message" data-testid="footer-email-input-message"></p>
Images must have alternative text45 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 src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="Quickly Create Lists..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="high" width="1" height="1">
<img class="_sponsored_banner_image_11fr4_5" alt="sponsored banner" src="https://dam.thdstatic.com/contentful/heroflattenimage/18OCT26-SWB-Gifting-DSK.png">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="Up to 50% off select..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="low" width="1" height="1">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="October2026 Tools" class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="low" width="1" height="1">
<img src="https://dam.thdstati..." srcset="https://dam.thdstati..." sizes="100vw" alt="26October2026 Elevat..." class="sui-w-full sui-h-ful..." data-testid="bay-image-img" fetchpriority="high" width="1" height="1">
Showing first 5 of 45 audited elements.
Inline text spacing must be adjustable with custom stylesheets5 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="hfapp" style="display:contents" data-reactroot="">
<div id="header-static" style="display:contents">
<div id="messageBar" class="MessageBar" style="position:static"><span>#1 Home Improvement Retailer</span></div>
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
<div class="sui-paper sui-shadow-none sui-h-full !sui-rounded-[12px]" id="sbotd-php-MmhXFKEUQivuzgtBYqgEX" data-sui-palette="light" style="--sui-palette-background-primary: var(--sui-palette-); --sui-palette-text-primary: var(--sui-palette-);">
Interactive controls must not be nested58 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button class="sui-lab-btn-base sui..." tabindex="0" type="button" aria-controls="magic-apron-assistan..." data-testid="header-b2c-magic-apr..." aria-expanded="false">
<button type="button" class="focus-visible:sui-ou..." data-testid="header-b2c-credit-se..." aria-label="Click to redirect to...">
<button type="button" class="focus-visible:sui-ou..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view ...">
<button type="button" class="focus-visible:sui-ou..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to updat...">
<button type="button" class="sui-btn sui-btn-prim..." aria-label="Search Field Icon" id="typeahead-search-ico..." color="primary">
Showing first 5 of 58 audited elements.
Interactive elements must have a visible focus indicator50 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
<button class="sui-lab-btn-base sui-font-regular sui-text-sm sui-..." tabindex="0" type="button" aria-controls="magic-apron-assistant-drawer" data-testid="header-b2c-magic-apron" aria-expanded="false">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="header-b2c-credit-service" aria-label="Click to redirect to credit service page">
<a data-testid="header-thd-logo" href="/">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="my-store-button" data-component="HeaderMyStore" aria-label="Open drawer to view my store">
<button type="button" class="focus-visible:sui-outline focus-visible:sui-outlin..." data-testid="delivery-zip-button" data-component="HeaderDeliveryZip" aria-label="Open drawer to update zip code">
Showing first 5 of 50 audited elements.
Links must be distinguishable without relying on color1 element
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a class="sui-underline sui-whitespace-pre" href="/c/Terms_of_Use" title="terms of use" alt="Terms of use">Terms Of Use.</a>
Links must have discernible text125 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 data-testid="header-thd-logo" href="/">
<a href="/auth/view/signin?fr..." class="sui-btn sui-btn-prim..." data-testid="button-component-sig...">
<a href="/auth/view/createaccount?fromReminder=true" class="sui-font-bold sui-text-xs sui-tracking-normal sui-normal-case sui-line-clamp-unset sui-font-normal sui-text-primary focus-visible:sui-bg-focus focus-visible:sui-outline-none sui-underline" data-testid="link-component-signInTest">
<a href="/cart" class="sui-flex sui-items-center sui-text-center hover:sui-fill-brand hover:sui-no-underline hover:sui-text-brand sui-flex-col sui-w-16 sui-fill-primary" data-testid="header-cart-icon" data-component="HeaderCartIcon" aria-label="Click to redirect to view my cart page">
<a aria-label="Navigate to Quickly Create Lists with AI-Powered Project Builder " href="https://www.homedepot.com/list/view/summary?lbai=gift" target="_self" clickid="ip-_-BentoHero-_-aMNkM8Prz417uaX4j9AI0-_-BentoBay-_-1-_-531E2fYfvkrL86wfYayQW7">
Showing first 5 of 125 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">
Required ARIA attributes must be provided4 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<input type="search" required="" class="placeholder:sui-text..." style="font:inherit;letter-..." placeholder="What can we help you..." name="keyword" autocomplete="off" autocorrect="off" id="typeahead-search-fie..." data-testid="typeahead-search-fie..." role="combobox" aria-autocomplete="list" ...>
<div role="tooltip" id="sign-in-bubble" data-testid="popover-component-signInTest" data-component="sign-in-bubble:SignInBubble:v2.10.0" class="sui-z-tooltip sui-group" style="position: absolute; top: 0px; left: 0px; transform: translate(782.933px, 108.8px); z-index: 1000;">
<div class="swiper-slide sui-shrink-0 [&>*]:sui-h-full sui-touch-pan-y swiper-slide-active" role="group" aria-label="1 / 1" style="width: 800px; margin-right: 16px;">
<svg class="sui-fill-brand" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 45 52" height="50%" width="24px" fill="none" role="presentation" data-component="magic-apron:AssistantIcon:v5.4.1" style="min-width: 24px; margin: 2px;">
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">
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">
How does your site stack up against The Home Depot?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Retail & E-commerce
