Target target.com
Accessibility score
League position
8thof 9
Issues found
5
Audits passed
47
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousFrames must have an accessible name1 element
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Failing Elements
<iframe id="px-captcha-modal" style="display: block; position: fixed; top: 0; left: 0; width: 100%; height: 100%; border: none; z-index: 2147483647;"></iframe>
Fix any of the following:
- Element has no title attribute
- 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's default semantics were not overridden with role="none" or role="presentation"
SeriousText must remain readable when spacing is increased26 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
<span class="styles_styledNameSpan__4zoPU " data-test="@web/ZipCodeButton/ZipCodeNumber">
<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Target Circle" data-test="@web/GlobalHeader/UtilityHeader/TargetCircle" id="utilityNav-circle" href="/circle">
<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Target Circle Card" data-test="@web/GlobalHeader/UtilityHeader/TargetCircleCard" id="utilityNav-circleCardLI" href="/circlecard">
<a class="styles_utilityLink__LPo9H" 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">
<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Registry" data-test="@web/GlobalHeader/UtilityHeader/Registry" id="utilityNav-registries" href="/gift-registry">
<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Weekly Ad" data-test="@web/GlobalHeader/UtilityHeader/WeeklyAd" id="utilityNav-weeklyAd" href="/weekly-ad">
<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Find Stores" data-test="@web/GlobalHeader/UtilityHeader/FindStores" id="utilityNav-findStores" href="/store-locator/find-stores">
<a aria-expanded="false" aria-label="Categories" data-test="@web/Header/MainMenuLink" class="styles_ndsLink__WPjeX styles_neverDecorate__P_tPc ..." href="/c/shop-all-categories/-/N-5xsxf?prehydrateClick=t...">
<a aria-expanded="false" aria-label="Deals" data-test="@web/Header/MainMenuLink" class="styles_ndsLink__WPjeX styles_neverDecorate__P_tPc ..." href="/c/top-deals/-/N-4xw74?prehydrateClick=true">
<a aria-expanded="false" aria-label="pickup and delivery" data-test="@web/PICKUP_AND_DELIVERY_PRIMARY_HEADER_LINK" class="styles_ndsLink__WPjeX styles_neverDecorate__P_tPc ..." href="/c/order-pickup/-/N-ng0a0?l1_nid=5xt1a&prehydr...">
Showing first 10 of 26 failing elements.
ModerateAll page content should be contained by landmarks4 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 data-test="skipLinks" id="skipLinks">
Fix any of the following:
- Some page content is not contained by landmarks
<h3 class="styles_ndsHeading__V2MIZ styles_fontSize3__xFv1m styles_x2Margin__7Pnix styles_signupHeading__l_hr_">Get top deals, latest trends, and more.</h3>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="styles_styledTextField__vYipy">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="styles_privacyAndTermsWrapper__ZzJ5u">
Fix any of the following:
- Some page content is not contained by landmarks
ModerateThe skip-link target should exist and be focusable2 elements
Skip links allow keyboard users to bypass repetitive navigation and jump directly to main content. Without skip links, users must tab through potentially hundreds of navigation links on every page, which is time-consuming and can cause physical pain for users with motor limitations.
Failing Elements
<a href="#skip" data-command="content" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to main content</a>
Fix any of the following:
- No skip link target
<a href="#skip" data-command="footer" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to footer</a>
Fix any of the following:
- No skip link target
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=resizes-content" name="viewport" data-next-head="">
Fix any of the following:
- <meta> tag limits zooming on mobile devices
Passed audits47 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" style="overflow: hidden;">
<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="overflow: hidden;">
<li> elements must be contained in a <ul> or <ol>24 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="styles_listItem__XZUUA">
<li class="styles_listItem__XZUUA">
<li class="styles_listItem__XZUUA">
<li class="styles_listItem__XZUUA">
<li class="styles_listItem__XZUUA">
Showing first 5 of 24 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements2 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 data-test="pictureNavigation-fe..." class="styles_row__KeMSR st..." style="--xs-row-j:center;--...">
<ul data-test="pictureNavigation-fe..." class="styles_row__KeMSR st..." style="--xs-row-j:center;--...">
All page content should be contained by landmarks841 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">
<a href="#skip" data-command="content" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to main content</a>
<a href="#skip" data-command="footer" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to footer</a>
<div>
<div class="styles_utilityHeaderWrapper__qFk52">
Showing first 5 of 841 audited elements.
Alternative text of images should not be repeated as text47 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 class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_9d8478bb-8498-4ceb-b473-ffaabf30e42f?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_2c28ec1f-c454-44a0-8d93-0ff4787815b2?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
Showing first 5 of 47 audited elements.
ARIA attributes must be used as specified for the element's role30 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="styles_btn__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<nav aria-label="Utility">
<nav aria-label="Primary">
<a aria-label="Target home" class="styles_ndsLink__WPjeX styles_logoLinkDesktop__wkzz5" href="/"><svg viewBox="0 0 24 24" width="48px"><image height="100%" href="/icons-illustrations/v2/light/bullseye-tm.svg" width="100%" xlink:href="/icons-illustrations/v2/light/bullseye-tm.svg"></image></svg></a>
Showing first 5 of 30 audited elements.
ARIA attributes must conform to valid names30 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="styles_btn__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<nav aria-label="Utility">
<nav aria-label="Primary">
<a aria-label="Target home" class="styles_ndsLink__WPjeX styles_logoLinkDesktop__wkzz5" href="/"><svg viewBox="0 0 24 24" width="48px"><image height="100%" href="/icons-illustrations/v2/light/bullseye-tm.svg" width="100%" xlink:href="/icons-illustrations/v2/light/bullseye-tm.svg"></image></svg></a>
Showing first 5 of 30 audited elements.
ARIA attributes must conform to valid values30 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="styles_btn__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<nav aria-label="Utility">
<nav aria-label="Primary">
<a aria-label="Target home" class="styles_ndsLink__WPjeX styles_logoLinkDesktop__wkzz5" href="/"><svg viewBox="0 0 24 24" width="48px"><image height="100%" href="/icons-illustrations/v2/light/bullseye-tm.svg" width="100%" xlink:href="/icons-illustrations/v2/light/bullseye-tm.svg"></image></svg></a>
Showing first 5 of 30 audited elements.
ARIA hidden element must not be focusable or contain focusable elements11 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 type="button" aria-hidden="true" id="staticShellLink" tabindex="-1" class="styles_ndsLink__WPjeX h-display-flex"></button>
<svg class="styles_shadowArrow__Gbtqo" 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);">
<br aria-hidden="true">
<span aria-hidden="true"></span>
<br aria-hidden="true">
Showing first 5 of 11 audited elements.
ARIA role should be appropriate for the element24 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__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
Showing first 5 of 24 audited elements.
ARIA roles used must conform to valid values24 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__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
Showing first 5 of 24 audited elements.
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__o..." 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;">
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 aria-label="What can we help you find? suggestions appear below" autocapitalize="off" autocomplete="off" autocorrect="off" class="styles_searchInput__vzqyk" data-test="@web/Search/SearchInput" id="search" placeholder="What can we help you find?" type="search" name="searchTerm" value="">
<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">
Buttons must have discernible text14 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__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<button aria-label="search by voice" class="styles_micButton__qOyg3" data-test="@web/Search/Microphone" type="button"></button>
<button aria-label="search" class="styles_searchButton__atdn9" data-test="@web/Search/SearchButton" tabindex="0" type="submit">search</button>
<button class="styles_btn__zZcJr styles_ndsButton__VgXft styles_md__N9Usy styles_filled__uq68y styles_fullWidth__ztP_d" type="button">Sign in or create account</button>
Showing first 5 of 14 audited elements.
Certain ARIA roles must be contained by particular parents6 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<button role="tab" type="button" aria-selected="true" class="styles_tabsButton__kHBwR styles_active__1GciG styles_md__Kf2l0" style="--tabs-border-bottom-color:#333333" aria-controls="tabContent-tab-FitnessActivewear" data-test="tabFitnessActivewear" id="tab-FitnessActivewear">
<button role="tab" type="button" aria-selected="false" class="styles_tabsButton__kHBwR styles_inactive__MfT7g styles_md__Kf2l0" style="--tabs-border-bottom-color:transparent" aria-controls="tabContent-tab-EatWell" data-test="tabEatWell" id="tab-EatWell">Eat Well</button>
<button role="tab" type="button" aria-selected="false" class="styles_tabsButton__kHBwR styles_inactive__MfT7g styles_md__Kf2l0" style="--tabs-border-bottom-color:transparent" aria-controls="tabContent-tab-VitaminsSupplements" data-test="tabVitaminsSupplements" id="tab-VitaminsSupplements">
<button role="tab" type="button" aria-selected="false" class="styles_tabsButton__kHBwR styles_inactive__MfT7g styles_md__Kf2l0" style="--tabs-border-bottom-color:transparent" aria-controls="tabContent-tab-SelfCare" data-test="tabSelfCare" id="tab-SelfCare">Self-Care</button>
<button role="tab" type="button" aria-selected="false" class="styles_tabsButton__kHBwR styles_inactive__MfT7g styles_md__Kf2l0" style="--tabs-border-bottom-color:transparent" aria-controls="tabContent-tab-WearableTech" data-test="tabWearableTech" id="tab-WearableTech">Wearable Tech</button>
Showing first 5 of 6 audited elements.
Certain ARIA roles must contain particular children1 element
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div class="styles_tabList__x6BFk styles_center__CQ9Pd" role="tablist">
Content must reflow without two-dimensional scrolling1 element
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="styles_ndsPopover__ot3WT styles_shadow__3_Zy_ styl..." role="tooltip" tabindex="-1" data-floating-ui-focusable="" style="left: 8px; top: 54px; position: absolute; transiti...">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer><h2 class="h-sr-only" id="footerHeader" tabindex="-1">Footer</h2><div id="embedded-chat"></div><div></div></footer>
Deprecated ARIA roles must not be used24 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__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
Showing first 5 of 24 audited elements.
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="overflow: hidden;">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer><h2 class="h-sr-only" id="footerHeader" tabindex="-1">Footer</h2><div id="embedded-chat"></div><div></div></footer>
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="sc-6842029c-0 YiPKX l-container-fixed" id="pageBodyContainer">
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="overflow: hidden;">
Elements marked as presentational should be consistently ignored46 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_9d8478bb-8498-4ceb-b473-ffaabf30e42f?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_2c28ec1f-c454-44a0-8d93-0ff4787815b2?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
Showing first 5 of 46 audited elements.
Elements must meet minimum color contrast ratio thresholds99 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__4zoPU " data-test="@web/ZipCodeButton/ZipCodeNumber">Ship to 95051</span>
<span class="styles_styledStoreNameSpan__rxeca ">Santa Clara</span>
<a class="styles_utilityLink__LPo9H" 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__LPo9H" 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__LPo9H" 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>
Showing first 5 of 99 audited elements.
Elements must only use permitted ARIA attributes30 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="styles_btn__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<nav aria-label="Utility">
<nav aria-label="Primary">
<a aria-label="Target home" class="styles_ndsLink__WPjeX styles_logoLinkDesktop__wkzz5" href="/"><svg viewBox="0 0 24 24" width="48px"><image height="100%" href="/icons-illustrations/v2/light/bullseye-tm.svg" width="100%" xlink:href="/icons-illustrations/v2/light/bullseye-tm.svg"></image></svg></a>
Showing first 5 of 30 audited elements.
Elements must only use supported ARIA attributes30 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="styles_btn__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<nav aria-label="Utility">
<nav aria-label="Primary">
<a aria-label="Target home" class="styles_ndsLink__WPjeX styles_logoLinkDesktop__wkzz5" href="/"><svg viewBox="0 0 24 24" width="48px"><image height="100%" href="/icons-illustrations/v2/light/bullseye-tm.svg" width="100%" xlink:href="/icons-illustrations/v2/light/bullseye-tm.svg"></image></svg></a>
Showing first 5 of 30 audited elements.
Elements should not have tabindex greater than zero10 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 aria-label="search" class="styles_searchButton__atdn9" data-test="@web/Search/SearchButton" tabindex="0" type="submit">search</button>
<a aria-expanded="false" aria-label="Account, sign in" data-test="@web/AccountLink" id="account-sign-in" tabindex="0" class="styles_ndsLink__WPjeX styles_neverDecorate__P_tPc sc-b1b0f138-0 sc-7c583681-1 naexN cbMJyf" href="/account?prehydrateClick=true">
<div class="styles_ndsPopover__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div aria-atomic="true" aria-live="assertive" class="styles_text__xx_bV" tabindex="-1">
<a aria-label="cart 0 items" data-test="@web/CartLink" tabindex="0" class="styles_ndsLink__WPjeX styles_neverDecorate__P_tPc styles_primaryHeaderLink__f_7xi styles_cartLink__O0Kbq " href="/cart?prehydrateClick=true">
Showing first 5 of 10 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 aria-label="What can we help you find? suggestions appear below" autocapitalize="off" autocomplete="off" autocorrect="off" class="styles_searchInput__vzqyk" data-test="@web/Search/SearchInput" id="search" placeholder="What can we help you find?" type="search" name="searchTerm" value="">
<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">
Form elements should have a visible label2 elements
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 aria-label="What can we help you find? suggestions appear below" autocapitalize="off" autocomplete="off" autocorrect="off" class="styles_searchInput__vzqyk" data-test="@web/Search/SearchInput" id="search" placeholder="What can we help you find?" type="search" name="searchTerm" value="">
<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">
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 aria-label="What can we help you find? suggestions appear below" autocapitalize="off" autocomplete="off" autocorrect="off" class="styles_searchInput__vzqyk" data-test="@web/Search/SearchInput" id="search" placeholder="What can we help you find?" type="search" name="searchTerm" value="">
<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">
Frames must have an accessible name3 elements
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe frameborder="0" src="https://96ff4edf6a73..." id="google_ads_iframe_/7..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="0" height="48" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." tabindex="0" ...>
<iframe frameborder="0" src="https://96ff4edf6a73..." id="google_ads_iframe_/7..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="0" height="100" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." tabindex="0" ...>
<iframe frameborder="0" src="https://96ff4edf6a73..." id="google_ads_iframe_/7..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="0" height="454" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." tabindex="0" ...>
Heading levels should only increase by one27 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h2 class="styles_ndsTypography__KEuZO styles_bodyMdBold__V6Ekx styles_headingText__q_RBb">Sign in for the best experience</h2>
<h1 class="styles_ndsHeading__V2MIZ styles_fontSize1___cLy8 styles_x2Margin__7Pnix" data-test="page-title" tabindex="-1">Homepage</h1>
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
Showing first 5 of 27 audited elements.
Headings should not be empty27 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__KEuZO styles_bodyMdBold__V6Ekx styles_headingText__q_RBb">Sign in for the best experience</h2>
<h1 class="styles_ndsHeading__V2MIZ styles_fontSize1___cLy8 styles_x2Margin__7Pnix" data-test="page-title" tabindex="-1">Homepage</h1>
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
<h2 class="styles_ndsHeading__V2MIZ styles_fontSize2__xNlIo styles_x2Margin__7Pnix storycard--headline styles_storycardHeadline__cM2fH styles_flexTextBigHeadline__HbGw7">
Showing first 5 of 27 audited elements.
IDs used in ARIA and labels must be unique4 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">
<button role="tab" type="button" aria-selected="true" class="styles_tabsButton__kHBwR styles_active__1GciG styles_md__Kf2l0" style="--tabs-border-bottom-color:#333333" aria-controls="tabContent-tab-FitnessActivewear" data-test="tabFitnessActivewear" id="tab-FitnessActivewear">
<div data-test="tab-tabContent-tab-FitnessActivewear" id="tabContent-tab-FitnessActivewear" role="tabpanel" aria-labelledby="tab-FitnessActivewear"><div class="styles_PrzContainer__h2nG1"></div></div>
<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">
Images must have alternative text47 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 class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_9d8478bb-8498-4ceb-b473-ffaabf30e42f?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_2c28ec1f-c454-44a0-8d93-0ff4787815b2?wid=668&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
<img class="styles_pictureLazy__HaVFX styles_fullWidth__TDj2w" src="https://target.scene7.com/is/image/Target/GUEST_0ea1432f-55df-4bc4-907c-25cbd9fb9c3d?wid=521&qlt=80&fmt=webp" alt="" loading="lazy" width="100%">
Showing first 5 of 47 audited elements.
Inline text spacing must be adjustable with custom stylesheets202 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="overflow: hidden;">
<body spellcheck="false" style="--scrollbar-width: 0px;">
<div class="styles_ndsTruncate__PqkOk" style="--truncate-lines: 2;"><span class="styles_styledStoreNameSpan__rxeca ">Santa Clara</span></div>
<div class="styles_ndsPopover__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="styles_storycardWrap..." data-test="@web/SlingshotCompon..." style="--aspect-ratio-defau...">
Showing first 5 of 202 audited elements.
Interactive controls must not be nested15 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__zZcJr styles_styledZipCodeButton__sSgbz " type="button" aria-expanded="false" aria-label="Ship to location: 95051" data-test="@web/ZipCodeButton/StyledZipCodeButton" id="zip-code-id-btn">
<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_storeNameButton__AoeaG " type="button" aria-expanded="false" aria-label="Store: Santa Clara" data-test="@web/StoreName/Button" id="web-store-id-msg-btn">
<button aria-label="search by voice" class="styles_micButton__qOyg3" data-test="@web/Search/Microphone" type="button"></button>
<button aria-label="search" class="styles_searchButton__atdn9" data-test="@web/Search/SearchButton" tabindex="0" type="submit">search</button>
<button class="styles_btn__zZcJr styles_ndsButton__VgXft styles_md__N9Usy styles_filled__uq68y styles_fullWidth__ztP_d" type="button">Sign in or create account</button>
Showing first 5 of 15 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination4 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<nav aria-label="Utility">
<nav aria-label="Primary">
<main class="sc-6842029c-0 YiPKX l-container-fixed" id="pageBodyContainer">
<footer><h2 class="h-sr-only" id="footerHeader" tabindex="-1">Footer</h2><div id="embedded-chat"></div><div></div></footer>
Links must have discernible text63 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 href="#skip" data-command="content" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to main content</a>
<a href="#skip" data-command="footer" class="styles_ndsLink__WPjeX styles_skipLink__PRpO9 h-sr-only h-sr-only-focusable ">skip to footer</a>
<a class="styles_utilityLink__LPo9H" 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__LPo9H" 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__LPo9H" 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>
Showing first 5 of 63 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main class="sc-6842029c-0 YiPKX l-container-fixed" id="pageBodyContainer">
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="overflow: hidden;">
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="overflow: hidden;">
Required ARIA attributes must be provided24 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__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
<div class="h-position-relative " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">
Showing first 5 of 24 audited elements.
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=resizes-content" name="viewport" data-next-head="">
How does your site stack up against Target?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Retail & E-commerce
