Targettarget.com
Accessibility Score
Issues Found
Issues Found
SeriousARIA 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.
Failing Elements
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
Fix any of the following:
- 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
ModerateAll page content should be contained by landmarks1 element
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
<label class="styles_ndsLabel__l_gym styles_animated__PkmjO" for="email-address">Email address<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span></label>
Fix any of the following:
- Some page content is not contained by landmarks
MinorUsers 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.
Failing Elements
<meta content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=2, interactive-widget=overlays-content" name="viewport" data-next-head="">
Fix any of the following:
- <meta> tag limits zooming on mobile devices
Passed Audits
<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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
<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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
All page content should be contained by landmarks83 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">
<div>
<div id="@web/component-header" class="sc-d3088906-1 fMwCNf">
<nav aria-label="Primary">
<div class="styles_primaryHeader__GEZwX">
<div class="styles_styledRef__PWS89" data-test="@web/HeaderPrimaryNav" id="headerPrimary">
<div class="styles_searchWrapper__35ZXZ">
<form class="styles_searchForm__MIBJO " action="/s" method="get">
<div class="styles_inputWrapper__uXZ0D styles_ndsTextField___KUmb">
<label class="styles_ndsLabel__l_gym styles_animated__PkmjO" for=""><span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span></label>
Showing first 10 of 83 audited elements.
ARIA attributes must be used as specified for the element's role7 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
<nav aria-label="Primary">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
ARIA attributes must conform to valid names7 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
<nav aria-label="Primary">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
ARIA attributes must conform to valid values6 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
<nav aria-label="Primary">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
ARIA hidden element must not be focusable or contain focusable elements27 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
<button aria-hidden="true" id="staticShellLink" tabindex="-1" class="styles_ndsLink__GUaai styles_onLight__QKcK7 h-display-flex" type="button" data-floating-ui-inert=""></button>
<div class="styles_burgerMenuContainer__r2C0j" data-floating-ui-inert="" aria-hidden="true">
<a aria-label="Target home" class="styles_ndsLink__GUaai styles_onLight__QKcK7 styles_logoLink__UhPnL" href="/" data-floating-ui-inert="" aria-hidden="true">
<input autocapitalize="none" autocomplete="on" autocorrect="off" id="" type="hidden" placeholder=" " name="prehydrateSearch" value="true" data-floating-ui-inert="" aria-hidden="true">
<a aria-expanded="false" aria-label="Account" data-test="@web/AccountLinkMobile" class="styles_ndsLink__GUaai styles_onLight__QKcK7 styles_neverDecorate__heNCW sc-1be40a8-1 sc-40e81479-0 bYlmHW gbXRph" href="/account?prehydrateClick=true" data-floating-ui-inert="" aria-hidden="true">
<svg class="styles_shadowArrow__6Zifx" aria-hidden="true" width="26" height="24" viewBox="0 0 24 24" style="position: absolute; pointer-events: none; left: 211.5px; bottom: 100%; transform: rotate(180deg);" data-floating-ui-inert="">
<input class="styles_searchInput__W2xFo" data-test="@web/SearchInputMobile" id="searchMobile" placeholder="What can we help you find?" tabindex="-1" type="text" name="searchTerm" value="" data-floating-ui-inert="" aria-hidden="true">
<input autocapitalize="none" autocomplete="on" autocorrect="off" id="" type="hidden" placeholder=" " name="prehydrateSearch" value="true" data-floating-ui-inert="" aria-hidden="true">
<h3 class="styles_ndsHeading__phw6r styles_fontSize3__AoSnd styles_x2Margin__ZKMpf styles_signUpHeading__QxOHU" data-floating-ui-inert="" aria-hidden="true">Get top deals, latest trends, and more.</h3>
<footer data-floating-ui-inert="" aria-hidden="true"><h2 class="h-sr-only" id="footerHeader" tabindex="-1">Footer</h2><div id="embedded-chat"></div><div></div></footer>
Showing first 10 of 27 audited elements.
ARIA role should be appropriate for the element38 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
<div class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div aria-label="Carousel" class="l-container l-container-standard" data-test="@web/SlingshotComponents/ProductsCarousel" role="region">
<div class="styles_ndsCarousel__yMTV9 h-padding-t-tight" aria-label="Carousel" role="region">
<button class="styles_btn__1hjpW styles_base__CPnMk styles_md__QaqTQ styles_ndsButtonSecondary__9gTTK h-margin-v-default" type="button" role="link" data-test="storycard--staticButton"><span>spring home sale</span></button>
<div aria-label="Carousel" class="l-container l-container-standard" data-test="@web/SlingshotComponents/ProductsCarousel" role="region">
<div class="styles_ndsCarousel__yMTV9 h-padding-t-tight" aria-label="Carousel" role="region">
<svg xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Target circle™" viewBox="0 0 122 33">
<svg xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Target circle™" viewBox="0 0 122 33">
<svg xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Target circle™" viewBox="0 0 122 33">
<svg xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Target circle™" viewBox="0 0 122 33">
Showing first 10 of 38 audited elements.
ARIA roles used must conform to valid values5 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
<div class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<div class="styles_content__XGoOV" role="status">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" role="alert">Loading content</span>
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 class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
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 spellcheck="false" style="--scrollbar-width: 0px; overflow: hidden; --floating-ui-scrollbar-width: 0px;">
Buttons must have discernible text2 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="styles_btn__1hjpW styles_base__3f8L_ styles_md__Jpg6t styles_ndsButton__XOOOH styles_md__Yc3tr styles_filled___MOAP styles_fullWidth__8m0Wc" type="button">Sign in or create account</button>
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
Deprecated ARIA roles must not be used5 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
<div class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<div class="styles_content__XGoOV" role="status">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" role="alert">Loading content</span>
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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
Elements must meet minimum color contrast ratio thresholds107 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="styles_styledNameSpan__tzkJR " data-test="@web/ZipCodeButton/ZipCodeNumber">Ship to 95051</span>
<span class="styles_styledStoreNameSpan__l8eeV">Santa Clara</span>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Target Circle" data-test="@web/GlobalHeader/UtilityHeader/TargetCircle" id="utilityNav-circle" href="/circle">Target Circle™</a>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Target Circle Card" data-test="@web/GlobalHeader/UtilityHeader/TargetCircleCard" id="utilityNav-circleCardLI" href="/circlecard">Target Circle™ Card</a>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Target Circle 360" data-test="@web/GlobalHeader/UtilityHeader/TargetCircle360" id="utilityNav-circle360" href="/l/target-circle-360/-/N-2rguk">Target Circle 360™</a>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Registry" data-test="@web/GlobalHeader/UtilityHeader/Registry" id="utilityNav-registries" href="/gift-registry">Registry & Wish List</a>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Weekly Ad" data-test="@web/GlobalHeader/UtilityHeader/WeeklyAd" id="utilityNav-weeklyAd" href="/weekly-ad">Weekly Ad</a>
<a class="styles_utilityLink__Bh2js" data-ff-lnk-nav-click-text="Find Stores" data-test="@web/GlobalHeader/UtilityHeader/FindStores" id="utilityNav-findStores" href="/store-locator/find-stores">Find Stores</a>
<a aria-expanded="false" aria-label="Categories" data-test="@web/Header/MainMenuLink" class="styles_ndsLink__GUaai styles_onLight__QKcK7 styles_neverDecorate__heNCW sc-1be40a8-1 sc-1be40a8-3 bYlmHW cvtjWg h-margin-l-wide" href="/c/shop-all-categories/-/N-5xsxf?prehydrateClick=true">
<a aria-expanded="false" aria-label="Deals" data-test="@web/Header/MainMenuLink" class="styles_ndsLink__GUaai styles_onLight__QKcK7 styles_neverDecorate__heNCW sc-1be40a8-1 sc-1be40a8-3 bYlmHW cvtjWg" href="/c/top-deals/-/N-4xw74?prehydrateClick=true">
Showing first 10 of 107 audited elements.
Elements must only use permitted ARIA attributes7 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
<nav aria-label="Primary">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
Elements must only use supported ARIA attributes7 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
<nav aria-label="Primary">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" aria-atomic="true" aria-live="assertive"></span>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
Elements should not have tabindex greater than zero4 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 class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div aria-atomic="true" aria-live="assertive" class="styles_text__WdQJ6" tabindex="-1">
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<h2 class="styles_ndsHeading__phw6r styles_fontSize2__rqnzp styles_noMargin___oE_D" tabindex="-1">Loading screen</h2>
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="styles_ndsTypography__tjnQZ styles_bodyMdBold__hrnyT styles_headingText__RuZC8">Sign in for the best experience</h2>
Headings should not be empty3 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 class="styles_ndsTypography__tjnQZ styles_bodyMdBold__hrnyT styles_headingText__RuZC8">Sign in for the best experience</h2>
<h2 class="styles_ndsHeading__phw6r styles_fontSize2__rqnzp styles_noMargin___oE_D" tabindex="-1">Loading screen</h2>
<h3 class="styles_ndsHeading__phw6r styles_fontSize3__AoSnd styles_x1Margin__UGy1b styles_heading__PFMyC">
IDs used in ARIA and labels must be unique6 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
<input autocapitalize="none" autocomplete="on" autocorrect="off" id="" type="hidden" placeholder=" " name="prehydrateSearch" value="true" data-floating-ui-inert="" aria-hidden="true">
<button role="tab" type="button" aria-selected="true" class="styles_tabsButton__26AOd styles_active__sJna0 styles_md__eSU3X" style="--tabs-border-bottom-color:#333333" aria-controls="tabContent-tab-HouseholdEssentials" data-test="tabHouseholdEssentials" id="tab-HouseholdEssentials">
<div data-test="tab-tabContent-tab-HouseholdEssentials" id="tabContent-tab-HouseholdEssentials" role="tabpanel" aria-labelledby="tab-HouseholdEssentials">
<button role="tab" type="button" aria-selected="true" class="styles_tabsButton__26AOd styles_active__sJna0 styles_md__eSU3X" style="--tabs-border-bottom-color:#333333" aria-controls="tabContent-tab-KBeauty" data-test="tabKBeauty" id="tab-KBeauty">K-Beauty</button>
<div data-test="tab-tabContent-tab-KBeauty" id="tabContent-tab-KBeauty" role="tabpanel" aria-labelledby="tab-KBeauty">
<input autocapitalize="none" autocomplete="on" autocorrect="off" id="email-address" type="email" placeholder=" " name="email-address" value="" data-floating-ui-inert="" aria-hidden="true">
Inline text spacing must be adjustable with custom stylesheets6 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
<html lang="en-US" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
<body spellcheck="false" style="--scrollbar-width: 0px; overflow: hidden; --floating-ui-scrollbar-width: 0px;">
<div class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="styles_overlay__AJMdo" style="position: fixed; overflow: auto; inset: 0px; transition-property: opacity; transition-timing-function: cubic-bezier(0.12, 0.51, 0.19, 1.09); opacity: 1; transition-duration: 300ms;">
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<div class="styles_ndsSpinner__agM2w styles_spinner__GbTsM" style="--nds-spinner-color: var(--color-icon-disabled); --nds-spinner-size: var(--size-icon-sm);">
Interactive controls must not be nested2 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="styles_btn__1hjpW styles_base__3f8L_ styles_md__Jpg6t styles_ndsButton__XOOOH styles_md__Yc3tr styles_filled___MOAP styles_fullWidth__8m0Wc" type="button">Sign in or create account</button>
<button aria-label="close" class="styles_ndsButtonClose__GCWpq styles_sm__uMXLg styles_closeButton__61TIz" type="button"><svg viewBox="0 0 24 24"><use href="/icons-illustrations/v2/close.svg#close" xlink:href="/icons-illustrations/v2/close.svg#close"></use></svg></button>
Landmarks 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.
Audit Elements
<nav aria-label="Primary">
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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
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" style="--global-header-height-sm: 125px; --global-header-height-lg: 80px;">
Required ARIA attributes must be provided5 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
<div class="styles_ndsPopover__a..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
<div aria-labelledby="_r_a_" aria-modal="true" class="styles_ndsModal__4H1..." tabindex="-1" data-floating-ui-foc...="" id="_r_b_" role="dialog" style="transition-property:...">
<div class="styles_content__XGoOV" role="status">
<span class="styles_ndsScreenReaderOnly__JErIH styles_notFocusable__MXmh8" role="alert">Loading content</span>
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 content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=2, interactive-widget=overlays-content" name="viewport" data-next-head="">