Target target.com

Screenshot of the Target home page

Accessibility score

Poor+35 vs September

League position

6thof 10

Issues found

3

Audits passed

15

Accessibility score over time

weekly scans · last 6 months

Good · 90+
Needs improvement · 70–89
Poor · Below 70

This month's scan

Issues found

2Serious1Minor

Serious

Frames must have an accessible name

1 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

#px-captcha-modal

<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"

Serious

Text must remain readable when spacing is increased

25 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

#utilityNav-circle

<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Target Circle" data-test="@web/GlobalHeader/UtilityHeader/TargetCircle" id="utilityNav-circle" href="/l/target-circle/-/N-pzno9">

#utilityNav-circleCardLI

<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">

#utilityNav-circle360

<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">

#utilityNav-registries

<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Registry" data-test="@web/GlobalHeader/UtilityHeader/Registry" id="utilityNav-registries" href="/gift-registry">

#utilityNav-weeklyAd

<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">

#utilityNav-findStores

<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.h-margin-l-wide

<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...">

div.styles_desktopLinkContainer__C7CaC:nth-of-type(3)>a.styles_spacedPrimaryHeaderLink__F8MNV

<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.h-hidden-md-down

<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&amp;prehydr...">

button.styles_searchButton__atdn9

<button aria-label="search" class="styles_searchButton__atdn9 " data-test="@web/Search/SearchButton" tabindex="0" type="submit">

Showing first 10 of 25 failing elements.

Minor

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.

Failing Elements

meta[name="viewport"]

<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 audits15 across 1 page

<html> element must have a lang attribute

1 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

<html lang="en-US" style="overflow: hidden;">

<html> element must have a valid value for the lang attribute

1 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

<html lang="en-US" style="overflow: hidden;">

All page content should be contained by landmarks

1 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.

Audit Elements

#px-captcha-modal

<iframe id="px-captcha-modal" style="display: block; position: fixed; top: 0; left: 0; width: 100%; height: 100%; border: none; z-index: 2147483647;"></iframe>

ARIA hidden element must not be focusable or contain focusable elements

23 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

#__NEXT_DATA__

<script id="__NEXT_DATA__" type="application/json" crossorigin="anonymous" aria-hidden="true">

iframe[name="q7k2m8010129"]

<iframe name="q7k2m8010129" aria-hidden="true" tabindex="-1" style="display: none;"></iframe>

.ModalDrawer[aria-hidden="true"]:nth-child(4)

<div class="ModalDrawer" aria-hidden="true"></div>

.ModalDrawer[aria-hidden="true"]:nth-child(5)

<div class="ModalDrawer" aria-hidden="true"></div>

.ModalDrawer[aria-hidden="true"]:nth-child(6)

<div class="ModalDrawer" aria-hidden="true"></div>

Showing first 5 of 23 audited elements.

ARIA role should be appropriate for the element

28 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

.styles_agenticChatWrapper__tOJGT > .styles_agenticShopperButton__gN1CM > .AskAiButton_button__7WulQ.AskAiButton_play__eJkPS[aria-label="Ask Target"]

<div aria-label="Ask Target" class="AskAiButton_button__7WulQ AskAiButton_play__eJkPS " role="button" style="--btn-h:32px" tabindex="0">

.styles_ndsPopover__ot3WT

<div class="styles_ndsPopover__o..." role="tooltip" tabindex="-1" data-floating-ui-foc...="" style="left: 912px; top: 62...">

.styles_agenticChatWrapper__eB6tJ > .styles_agenticShopperButton__gN1CM > .AskAiButton_button__7WulQ.AskAiButton_play__eJkPS[aria-label="Ask Target"]

<div aria-label="Ask Target" class="AskAiButton_button__7WulQ AskAiButton_play__eJkPS " role="button" style="--btn-h:32px" tabindex="0">

.styles_ndsButtonSecondary__heDu5

<button class="styles_btn__zZcJr styles_base__SonOG styles_md__YSyPt styles_ndsButtonSecondary__heDu5 h-margin-v-default" type="button" role="link" data-test="storycard--staticButton"><span>Shop all Halloween</span></button>

div[data-component-position="525"] > div > .styles-common_contentPoolContainer__cGo6_ > .styles-common_baseContainer__A_qX9 > .styles-multistory_multistoryGrid__JdZ_d.styles-multistory_grid4Up__lQDEL > .h-position-relative[role="presentation"][data-viewable-impression="true"]:nth-child(1)

<div class="h-position-relative  " data-test="content-pool-multi-story-poly-amplified-card" role="presentation" data-viewable-impression="true">

Showing first 5 of 28 audited elements.

aria-hidden="true" must not be present on the document body

1 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

<body spellcheck="false" style="--scrollbar-width: 0px;">

Content must reflow without two-dimensional scrolling

0 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.

Document should have one main landmark

1 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

<html lang="en-US" style="overflow: hidden;">

Documents must have <title> element to aid in navigation

1 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

<html lang="en-US" style="overflow: hidden;">

Elements must meet minimum color contrast ratio thresholds

108 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

.styles_styledNameSpan__4zoPU

<span class="styles_styledNameSpan__4zoPU   " data-test="@web/ZipCodeButton/ZipCodeNumber">Ship to 01010</span>

.styles_styledStoreNameSpan__rxeca

<span class="styles_styledStoreNameSpan__rxeca  ">Springfield East</span>

#utilityNav-circle

<a class="styles_utilityLink__LPo9H" data-ff-lnk-nav-click-text="Target Circle" data-test="@web/GlobalHeader/UtilityHeader/TargetCircle" id="utilityNav-circle" href="/l/target-circle/-/N-pzno9">Target Circle™</a>

#utilityNav-circleCardLI

<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>

#utilityNav-circle360

<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 108 audited elements.

IDs used in ARIA and labels must be unique

4 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

form[method="get"] > .styles_inputWrapper__gWJPt.styles_ndsTextField__xsdD2 > input[autocapitalize="none"][type="hidden"][name="prehydrateSearch"]

<input autocapitalize="none" autocomplete="on" autocorrect="off" id="" type="hidden" placeholder=" " name="prehydrateSearch" value="true">

#tab-Womens

<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-Womens" data-test="tabWomens" id="tab-Womens">Women’s</button>

#tabContent-tab-Womens

<div data-test="tab-tabContent-tab-Womens" id="tabContent-tab-Womens" role="tabpanel" aria-labelledby="tab-Womens"><div class="styles_PrzContainer__h2nG1"></div></div>

#email-address

<input autocomplete="on" autocorrect="off" id="email-address" type="text" placeholder=" " name="email-address" value="">

Inline text spacing must be adjustable with custom stylesheets

2 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

<html lang="en-US" style="overflow: hidden;">

body

<body spellcheck="false" style="--scrollbar-width: 0px;">

Page must have means to bypass repeated blocks

1 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

<html lang="en-US" style="overflow: hidden;">

Page should contain a level-one heading

1 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

<html lang="en-US" style="overflow: hidden;">

Zooming and scaling must not be disabled

1 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"]

<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