Best Buybestbuy.com
Accessibility Score
Issues Found
Issues Found
SeriousARIA hidden element must not be focusable or contain focusable elements20 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.
Failing Elements
<li aria-hidden="true" class="item c-carousel-item " data-order="6" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="7" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="8" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="9" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="10" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="11" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="12" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="13" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="14" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<li aria-hidden="true" class="item c-carousel-item " data-order="15" style="margin-right: 16px; width: 159px;">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
Showing first 10 of 20 failing elements.
SeriousLinks must have discernible text1 element
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.
Failing Elements
<a href="https://www.bestbuy.com/site/promo/latest-samsung-galaxy-phones" data-testid="carousel-slide-active" class="no-underline block w-full shrink-0 focus-visible:outline focus-visible:outline-2 focus-visible:outline-brand-tech-black focus-visible:outline-offset-2" style="width: 100%;">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- 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
SeriousElements should not have tabindex greater than zero1 element
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.
Failing Elements
<div tabindex="1" data-testid="AutocompleteContainer-TestID" class="sugg-autocomplete-container sugg-lv">
Fix any of the following:
- Element has a tabindex greater than 0
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
<div style="position: fixed; bac...">
Fix any of the following:
- Some page content is not contained by landmarks
MinorAlternative text of images should not be repeated as text6 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Failing Elements
<img src="https://pisces.bbyst..." alt="Shop Top 100 Deals" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img src="https://pisces.bbyst..." alt="Apple" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img src="https://pisces.bbyst..." alt="Back to School Deals" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img src="https://pisces.bbyst..." alt="Exclusive Member Dea..." class="deals-sale-event-cat..." loading="lazy" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img src="https://pisces.bbyst..." alt="Cell Phones" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img src="https://pisces.bbyst..." alt="Computers & Tablets" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
<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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
<li> elements must be contained in a <ul> or <ol>43 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="item c-carousel-item " data-order="0" tabindex="-1" style="margin-right: 16px; width: 159px;">
<li class="item c-carousel-item " data-order="1" style="margin-right: 16px; width: 159px;">
<li class="item c-carousel-item " data-order="2" style="margin-right: 16px; width: 159px;">
<li class="item c-carousel-item " data-order="3" style="margin-right: 16px; width: 159px;">
<li class="item c-carousel-item " data-order="4" style="margin-right: 16px; width: 159px;">
<li class="item c-carousel-item " data-order="5" style="margin-right: 16px; width: 159px;">
<li class="w-1/4">
<li class="w-1/4">
<li class="w-1/4">
<li class="w-1/4">
Showing first 10 of 43 audited elements.
<svg> elements with an img role must have alternative text1 element
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements8 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="c-carousel-list" style="transform: translate3d(0px, 0px, 0px);">
<ul class="icon-navigation list-none flex grow w-full m-none px-none pb-400">
<ul class="navigation-section-list p-none list-none">
<ul class="navigation-section-list p-none list-none">
<ul class="navigation-section-list p-none list-none">
<ul class="navigation-section-list p-none list-none">
<ul class="navigation-section-list p-none list-none">
<ul class="navigation-section-list p-none list-none">
All page content should be contained by landmarks565 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 data-exp-key="exp0442"></div>
<div data-no-show="1" class="smart-banner"></div>
<div id="headerFooterIncludes-beforeFirstPaintSet">
<div class="atwa-ninja"><!--$--><div><div><div class="appContainer" data-version="0.77.0"></div></div></div><!--/$--></div>
<div><div><div class="appContainer" data-version="0.77.0"></div></div></div>
<div><div class="appContainer" data-version="0.77.0"></div></div>
<div class="appContainer" data-version="0.77.0"></div>
<div style="--marquee-collapse-delay:10s" class="marquee-ad-wrapper">
<div class="display-ad-wrapper">
<div>
Showing first 10 of 565 audited elements.
Alternative text of images should not be repeated as text9 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="https://pisces.bbystatic.com/image2/BestBuy_US/dam/2573535-bfij-clock-070725-557f39e5-6b38-40fd-9330-9a9d2627f918.png;maxHeight=30;maxWidth=40" alt="">
<img alt="" fetchpriority="high" loading="eager" width="112" height="112" decoding="async" data-nimg="1" class="w-full image-carouse..." src="https://pisces.bbyst..." style="color: transparent; ...">
<img alt="Save up to $250 on a..." fetchpriority="high" loading="eager" width="112" height="112" decoding="async" data-nimg="1" class="w-full image-carouse..." style="color:transparent;ob..." src="https://pisces.bbyst...">
<img alt="Share on YouTube" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppYouTube-c823f6d3-8dcb-4964-9494-92cd7a54b4ec.svg" width="32">
<img alt="Share on Instagram" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppInstagram-ea334c57-1040-4c6a-849b-cb5c211bfca2.svg" width="32">
<img alt="Share on TikTok" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppTikTok-4ad73591-e0c4-4848-a70c-1d251aeae862.svg" width="32">
<img alt="Share on Facebook" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppFacebook-6587dc59-5c2c-41f5-9db3-8775e21c57e9.svg" width="32">
<img alt="Share on Pinterest" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppPinterest-8bc14c43-a0c9-415f-a122-d247a150cda0.svg" width="32">
<img alt="Share on X" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/X-bd003ff5-a027-4542-9c98-1d568c5d509e.svg" width="32">
ARIA attributes must be used as specified for the element's role35 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<button id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
Showing first 10 of 35 audited elements.
ARIA attributes must conform to valid names35 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<button id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
Showing first 10 of 35 audited elements.
ARIA attributes must conform to valid values35 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<button id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
Showing first 10 of 35 audited elements.
ARIA commands must have an accessible name1 element
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<a role="button" id="learn-more-link" aria-expanded="false" tabindex="0" data-testid="learn-more-link-test-lv" class="no-underline inline">
ARIA hidden element must not be focusable or contain focusable elements75 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
<div data-version="1.3.195" style="display:none" aria-hidden="true" data-testid="search-web-view-version"></div>
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="24px" width="24px">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="24px" width="24px">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-bg-default-fixed h-icon-md w-icon-md" data-testid="store-locator-store-icon">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="leading-icon" fill="white" width="24" height="24" style="flex: 0 0 auto;">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="16px" width="16px">
<svg aria-hidden="true" viewBox="0 0 16 8" class="fill-comp-surface-default stroke-comp-outline-default-muted" height="8" width="16" style="fill: rgb(255, 255, 255); stroke: rgb(196, 200, 207); stroke-width: 1;"><path d="M 0 0 L 8 7.5 L 16 0" tabindex="-1"></path></svg>
<div data-brix-component-...="Divider" data-brix-version="1.84.5" aria-hidden="true" data-testid="cart-icon-divider-l" style="border-top-color:rgb..." class="border-comp-divider-...">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" aria-label="Cart Icon" fill="white" height="24" width="24">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default-on-emphasis block">
Showing first 10 of 75 audited elements.
ARIA role should be appropriate for the element76 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="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="24px" width="24px">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="24px" width="24px">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-bg-default-fixed h-icon-md w-icon-md" data-testid="store-locator-store-icon">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="leading-icon" fill="white" width="24" height="24" style="flex: 0 0 auto;">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" class="fill-default" height="16px" width="16px">
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 24 24" aria-hidden="true" role="img" aria-label="Cart Icon" fill="white" height="24" width="24">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
Showing first 10 of 76 audited elements.
ARIA roles used must conform to valid values10 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="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="support & services" aria-expanded="false" role="button" aria-label="Support & Services" data-testid="chip-support & servi..." style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="discover" aria-expanded="false" role="button" aria-label="Discover" data-testid="chip-discover" style="border-top-color:rgb..." class="relative border-xs b...">
<a role="button" id="learn-more-link" aria-expanded="false" tabindex="0" data-testid="learn-more-link-test-lv" class="no-underline inline">
<footer class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
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 class="bby-ghp">
autocomplete attribute must be used correctly1 element
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 class="tb-input email-signup-input" autocomplete="off" id="footer-email-signup" placeholder="Enter email address" required="" value="" name="footer-email-signup">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header data-testid="header">
Buttons must have discernible text18 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 id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
<button data-brix-component-...="Button" data-brix-version="1.82.1" id="signIn-toast-signIn-..." type="button" aria-busy="false" class="relative border-xs b..." style="min-width: 80px; min...">
<button data-brix-component-...="Button" data-brix-version="1.82.1" id="signIn-toast-createA..." type="button" aria-busy="false" class="relative border-xs b..." style="min-width: 80px; min...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="support & services" aria-expanded="false" role="button" aria-label="Support & Services" data-testid="chip-support & servi..." style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="discover" aria-expanded="false" role="button" aria-label="Discover" data-testid="chip-discover" style="border-top-color:rgb..." class="relative border-xs b...">
Showing first 10 of 18 audited elements.
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 class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
Deprecated ARIA roles must not be used10 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="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="support & services" aria-expanded="false" role="button" aria-label="Support & Services" data-testid="chip-support & servi..." style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="discover" aria-expanded="false" role="button" aria-label="Discover" data-testid="chip-discover" style="border-top-color:rgb..." class="relative border-xs b...">
<a role="button" id="learn-more-link" aria-expanded="false" tabindex="0" data-testid="learn-more-link-test-lv" class="no-underline inline">
<footer class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header data-testid="header">
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 class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
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 data-testid="main">
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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
Elements marked as presentational should be consistently ignored2 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 src="https://pisces.bbystatic.com/image2/BestBuy_US/dam/2573535-bfij-clock-070725-557f39e5-6b38-40fd-9330-9a9d2627f918.png;maxHeight=30;maxWidth=40" alt="">
<img alt="" fetchpriority="high" loading="eager" width="112" height="112" decoding="async" data-nimg="1" class="w-full image-carouse..." src="https://pisces.bbyst..." style="color: transparent; ...">
Elements must meet minimum color contrast ratio thresholds87 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
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<span data-testid="store-locator-your-store" class="font-sans text-style-body-md-400 text-default-on-emphasis">Your store</span>
<span data-testid="store-locator-store-locator" class="font-sans text-style-body-md-500 whitespace-nowrap text-default-on-emphasis">Find a store</span>
<span class="flex justify-start font-400 text-3 leading-3 text-brand-tech-white">Account</span>
<span class="v-p-right-xxs line-clamp font-500 text-3 leading-3 text-brand-tech-white" style="flex: 1 1 auto; min-width: 0px;">Sign in</span>
<p class=" text-4 font-500 leading-3 m-0" style="color: rgb(29, 37, 44); margin-bottom: 4px;">Hi there!</p>
<p class="v-fw-regular body-copy-lg font-400 text-3 leading-2 m-0" style="color: rgb(29, 37, 44);">For the best experience, be sure to sign in.</p>
<span class="font-sans text-style-body-sm-500 overflow-hidden line-clamp-1 text-default-on-emphasis" style="font-size: 12px; line-height: 16px; font-weight: 500; color: rgb(251, 251, 251);">Sign In</span>
<span class="font-sans text-style-body-sm-500 overflow-hidden line-clamp-1 text-default" style="font-size: 12px; line-height: 16px; font-weight: 500; color: rgb(3, 3, 3);">Create Account</span>
<span style="max-width:192px" class="font-sans text-left line-clamp-1 text-default-on-emphasis text-style-body-md-500 py-50">Shop</span>
Showing first 10 of 87 audited elements.
Elements must only use permitted ARIA attributes35 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<button id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
Showing first 10 of 35 audited elements.
Elements must only use supported ARIA attributes35 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<button id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
Showing first 10 of 35 audited elements.
Elements should not have tabindex greater than zero14 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="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<div tabindex="-1" style="pointer-events:none" class="m-0 w-icon-md h-icon-md">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<div tabindex="-1" class="m-0 w-icon-sm h-icon-sm" style="pointer-events: none;">
<div tabindex="-1" class="absolute flex" style="left: 383.539px; top: -8px; transform: rotate(180deg);">
<a href="/site/misc/back-to-school/pcmcat334100050000.c?id=pcmcat334100050000" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
<a href="/top-deals" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links"><span data-testid="utility-nav-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-default-on-emphasis decoration-default-on-emphasis">Top Deals</span></a>
<a href="/site/misc/deal-of-the-day/pcmcat248000050016.c?id=pcmcat248000050016" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
<a href="/site/electronics/gift-ideas/abcat0010000.c?id=abcat0010000" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
Showing first 10 of 14 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
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<input class="tb-input email-signup-input" autocomplete="off" id="footer-email-signup" placeholder="Enter email address" required="" value="" name="footer-email-signup">
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
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<input class="tb-input email-signup-input" autocomplete="off" id="footer-email-signup" placeholder="Enter email address" required="" value="" name="footer-email-signup">
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
<textarea aria-label="What can we help you find? Suggestions appear below" class="sugg-search-bar-input-adjust" placeholder="Search Best Buy" id="autocomplete-search-bar" data-testid="SearchBarExtendable-TestID" maxlength="280" value=""></textarea>
<input class="tb-input email-signup-input" autocomplete="off" id="footer-email-signup" placeholder="Enter email address" required="" value="" name="footer-email-signup">
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
Frames 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.
Audit Elements
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
Heading levels should only increase by one9 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
<h1 class="headline80 font-weight-bold font-condensed">BLACK FRIDAY <span class="font-weight-light">IN JULY</span></h1>
<h2 class="text-style-title-sm-500 line-clamp-1 text-default" data-testid="header">Shop deals by category</h2>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Order & Purchases</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Payment Options</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Support & Services</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Rewards & Membership</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Partnerships</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">About Best Buy</h3>
<h3 class="heading-6 ">Get the latest deals and more.</h3>
Headings should not be empty9 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
<h1 class="headline80 font-weight-bold font-condensed">BLACK FRIDAY <span class="font-weight-light">IN JULY</span></h1>
<h2 class="text-style-title-sm-500 line-clamp-1 text-default" data-testid="header">Shop deals by category</h2>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Order & Purchases</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Payment Options</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Support & Services</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Rewards & Membership</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">Partnerships</h3>
<h3 class="navigation-section-heading body-copy-lg v-text-tech-black">About Best Buy</h3>
<h3 class="heading-6 ">Get the latest deals and more.</h3>
IDs used in ARIA and labels must be unique1 element
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 class="tb-input email-signup-input" autocomplete="off" id="footer-email-signup" placeholder="Enter email address" required="" value="" name="footer-email-signup">
Images must have alternative text15 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="https://pisces.bbystatic.com/image2/BestBuy_US/dam/2573535-bfij-clock-070725-557f39e5-6b38-40fd-9330-9a9d2627f918.png;maxHeight=30;maxWidth=40" alt="">
<img src="https://pisces.bbyst..." alt="Shop Top 100 Deals" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img src="https://pisces.bbyst..." alt="Apple" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img src="https://pisces.bbyst..." alt="Back to School Deals" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img src="https://pisces.bbyst..." alt="Exclusive Member Dea..." class="deals-sale-event-cat..." loading="lazy" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img src="https://pisces.bbyst..." alt="Cell Phones" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img src="https://pisces.bbyst..." alt="Computers & Tablets" class="deals-sale-event-cat..." loading="eager" data-testid="Deals-Image-TestID" style="width: 100%; max-wid...">
<img alt="" fetchpriority="high" loading="eager" width="112" height="112" decoding="async" data-nimg="1" class="w-full image-carouse..." src="https://pisces.bbyst..." style="color: transparent; ...">
<img alt="Save up to $250 on a..." fetchpriority="high" loading="eager" width="112" height="112" decoding="async" data-nimg="1" class="w-full image-carouse..." style="color:transparent;ob..." src="https://pisces.bbyst...">
<img alt="Share on YouTube" height="32" loading="lazy" src="https://pisces.bbystatic.com/image2/vector/BestBuy_US/dam/AppYouTube-c823f6d3-8dcb-4964-9494-92cd7a54b4ec.svg" width="32">
Showing first 10 of 15 audited elements.
Inline text spacing must be adjustable with custom stylesheets168 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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
<div style="--marquee-collapse-delay:10s" class="marquee-ad-wrapper">
<div class="atwb-display-ad" data-version="0.77.0" style="width:100%;text-align:center">
<div class="bg-container" id="marquee-bg" style="background-image: url("https://tpc.googlesyndication.com/simgad/9885985190235676889?"); background-repeat: no-repeat; background-position: center center; position: relative;"></div>
<div id="google_ads_iframe_/6011/BestBuyDesktopWeb/best_buy_0__container__" style="border: 0pt;">
<iframe id="google_ads_iframe_/6..." name="google_ads_iframe_/6..." title="3rd party ad content" width="1008" height="160" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<div style="background-color:#0046be">
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<div style="position: absolute; inset: -4px;"></div>
<div tabindex="-1" style="pointer-events:none" class="m-0 w-icon-md h-icon-md">
Showing first 10 of 168 audited elements.
Interactive controls must not be nested34 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 id="assistive_header_survey_launch_button" type="button" class="c-button-link c-button-link link utility sr-only sr-only-focusable visibility-hidden visibility-hidden-focusable" aria-label="Open survey: Assistive Survey" aria-haspopup="dialog">Assistive Survey</button>
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<button data-brix-component-...="Button" data-brix-version="1.84.5" id="autocomplete-search-..." data-testid="SearchButton-TestID" aria-label="Submit search" aria-busy="false" style="min-width:auto;min-h..." class="relative border-soli...">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button id="account-menu-account-button" class="plButton account-button d-flex justify-content-center align-items-center bg-transparent" data-lid="hdr_signin" aria-expanded="true" type="button" style="border: transparent; cursor: pointer; max-width: 200px;">
<button data-brix-component-...="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-butt..." type="button" aria-busy="false" class="border-solid justify..." style="min-width: auto; min...">
<button data-brix-component-...="Button" data-brix-version="1.82.1" id="signIn-toast-signIn-..." type="button" aria-busy="false" class="relative border-xs b..." style="min-width: 80px; min...">
<button data-brix-component-...="Button" data-brix-version="1.82.1" id="signIn-toast-createA..." type="button" aria-busy="false" class="relative border-xs b..." style="min-width: 80px; min...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgb..." class="relative border-xs b...">
Showing first 10 of 34 audited elements.
Interactive elements must have a visible focus indicator64 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<button data-brix-component-name="Button" data-brix-version="1.82.1" aria-label="Close" data-testid="undefined-close-button" type="button" aria-busy="false" class="border-solid justify-center items-center self-star..." style="min-width: auto; min-height: auto;">
<button data-brix-component-name="Button" data-brix-version="1.82.1" id="signIn-toast-signIn-button" type="button" aria-busy="false" class="relative border-xs border-solid rounded-lg justify..." style="min-width: 80px; min-height: 40px; box-shadow: rgb...">
<button data-brix-component-name="Button" data-brix-version="1.82.1" id="signIn-toast-createAccount-button" type="button" aria-busy="false" class="relative border-xs border-solid rounded-lg justify..." style="min-width: 80px; min-height: 40px; box-shadow: rgb...">
<a href="/cart" aria-label="cart, 0 items" data-lid="hdr_carticon" class="no-underline inline-flex">
<button data-brix-component-name="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgba(255,255,255,0.30);border-rig..." class="relative border-xs border-solid items-center box-b...">
<button data-brix-component-name="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgba(255,255,255,0.30);border-rig..." class="relative border-xs border-solid items-center box-b...">
<button data-brix-component-name="Chip" data-brix-version="1.84.5" data-menu-type="support & services" aria-expanded="false" role="button" aria-label="Support & Services" data-testid="chip-support & services" style="border-top-color:rgba(255,255,255,0.30);border-rig..." class="relative b...
<button data-brix-component-name="Chip" data-brix-version="1.84.5" data-menu-type="discover" aria-expanded="false" role="button" aria-label="Discover" data-testid="chip-discover" style="border-top-color:rgba(255,255,255,0.30);border-rig..." class="relative border-xs border-solid items-center box-b.....
<a href="/site/misc/back-to-school/pcmcat334100050000.c?id=..." tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
<a href="/top-deals" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
Showing first 10 of 64 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination6 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
<div class="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<header data-testid="header">
<nav aria-label="utility" class="bottom-nav flex justify-between items-center">
<section aria-label="skip target"><div class="visibility-hidden" id="headerskip" tabindex="-1">Main Content</div></section>
<main data-testid="main">
<footer class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
Links must have discernible text74 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="#headerskip" data-testid="skip-to-content-link" class="no-underline inline visibility-hidden visibility-hidden-focusable"><span data-testid="skip-to-content-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-primary decoration-primary">Skip to content</span></a>
<a href="#autocomplete-search-bar" data-testid="skip-to-search-link" class="no-underline inline visibility-hidden visibility-hidden-focusable">
<a href="#footer" data-testid="skip-to-footer-link" class="no-underline inline visibility-hidden visibility-hidden-focusable"><span data-testid="skip-to-footer-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-primary decoration-primary">Go to Footer</span></a>
<a aria-label="best buy home" href="https://www.bestbuy.com" title="BestBuy.com">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<a href="/cart" aria-label="cart, 0 items" data-lid="hdr_carticon" class="no-underline inline-flex">
<a href="/site/misc/back-to-school/pcmcat334100050000.c?id=pcmcat334100050000" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
<a href="/top-deals" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links"><span data-testid="utility-nav-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-default-on-emphasis decoration-default-on-emphasis">Top Deals</span></a>
<a href="/site/misc/deal-of-the-day/pcmcat248000050016.c?id=pcmcat248000050016" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
<a href="/site/electronics/gift-ideas/abcat0010000.c?id=abcat0010000" tabindex="0" data-testid="utility-nav-link" class="no-underline inline utility-nav-links">
Showing first 10 of 74 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 data-testid="main">
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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
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" data-app-version="26.28.44" style="--askblue-panel-width: 0px;">
Required ARIA attributes must be provided10 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="marquee-lv media-network-ad" role="region" aria-label="Best Buy Promotion" tabindex="0" data-testid="sponsored-marquee-lv">
<svg aria-label="best buy home" class="block" height="40" role="img" width="68" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 92">
<a aria-disabled="false" class="c-button-unstyled flex items-center gap-100" href="/site/store-locator" role="button" tabindex="0" style="text-decoration-color: rgb(224, 230, 239);">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="shop" aria-expanded="false" role="button" aria-label="Shop" data-testid="chip-shop" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="deals" aria-expanded="false" role="button" aria-label="Deals" data-testid="chip-deals" style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="support & services" aria-expanded="false" role="button" aria-label="Support & Services" data-testid="chip-support & servi..." style="border-top-color:rgb..." class="relative border-xs b...">
<button data-brix-component-...="Chip" data-brix-version="1.84.5" data-menu-type="discover" aria-expanded="false" role="button" aria-label="Discover" data-testid="chip-discover" style="border-top-color:rgb..." class="relative border-xs b...">
<a role="button" id="learn-more-link" aria-expanded="false" tabindex="0" data-testid="learn-more-link-test-lv" class="no-underline inline">
<footer class="appContainer p-200 p-md-300 p-lg-400 p-xl-500 v-bg-background-white lv" id="footer" role="contentinfo">
<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>
The skip-link target should exist and be focusable3 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.
Audit Elements
<a href="#headerskip" data-testid="skip-to-content-link" class="no-underline inline visibility-hidden visibility-hidden-focusable"><span data-testid="skip-to-content-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-primary decoration-primary">Skip to content</span></a>
<a href="#autocomplete-search-bar" data-testid="skip-to-search-link" class="no-underline inline visibility-hidden visibility-hidden-focusable">
<a href="#footer" data-testid="skip-to-footer-link" class="no-underline inline visibility-hidden visibility-hidden-focusable"><span data-testid="skip-to-footer-link-text" style="cursor:pointer" class="font-sans text-style-body-md-400 text-primary decoration-primary">Go to Footer</span></a>
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">