Amazon amazon.com
Accessibility score
League position
9thof 10
Issues found
12
Audits passed
50
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalElements must only use supported ARIA attributes1 element
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.
Failing Elements
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
CriticalARIA attributes must conform to valid values1 element
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.
Failing Elements
<button class="nav-arrow icp-up-down-arrow" aria-controls="nav-flyout-icp-footer-flyout" aria-label="Expand to Change Language or Country"></button>
Fix all of the following:
- Invalid ARIA attribute value: aria-controls="nav-flyout-icp-footer-flyout"
SeriousARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Failing Elements
<div id="nav-flyout-ewc" class="nav-ewc-lazy-align nav-ewcFlyout nav-flyout nav-locked" aria-modal="false" role="dialog" style="top: 0px; height: 800px;">
Fix any of the following:
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
SeriousElements must have their visible text as part of their accessible name2 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<a href="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lang_ais" class="nav-a nav-a-2 icp-link-style-2" aria-label="Choose a language for shopping in Amazon United States. The current selection is English (EN). ">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a href="/gp/cart/view.html?ref_=nav_cart" aria-label="0 items in cart" class="nav-a nav-a-2 nav-progressive-attribute" id="nav-cart">
Fix any of the following:
- Text inside the element is not included in the accessible name
SeriousForm elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Failing Elements
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
Fix all of the following:
- Only title used to generate label for form element
Serious<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
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.
Failing Elements
<ul class="nav-ul">
Fix all of the following:
- List element has direct children that are not allowed: a
SeriousAll touch targets must be 24px large, or leave sufficient space1 element
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Failing Elements
<button class="nav-flyout-button nav-icon nav-arrow" aria-label="Expand Account and Lists" tabindex="0" style="visibility: visible;"></button>
Fix any of the following:
- Target has insufficient size (8px by 4px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 10px instead of at least 24px.
SeriousText must remain readable when spacing is increased200 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
<a href="/Amazon-Video/b/?ie=UTF8&node=2858778011&r..." class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_0" data-csa-c-content-id="nav_cs_prime_video" data-csa-c-id="888pvu-bhlsjn-hlwg8-x5ryra">
<a href="/coupons?ref_=nav_cs_coupons" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_1" data-csa-c-content-id="nav_cs_coupons" data-csa-c-id="l914ns-s4rqix-w353ma-pkcya1">
<a href="/gp/help/customer/display.html?nodeId=508510&r..." class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_2" data-csa-c-content-id="nav_cs_customerservice" data-csa-c-id="sv0k3p-fjomf2-yx9mqf-1tdns1">
<a href="/gp/goldbox?ref_=nav_cs_gb" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_3" data-csa-c-content-id="nav_cs_gb" data-csa-c-id="q77zq7-f1u4n8-bdl5o9-4kfkpf">
<a href="/gp/browse.html?node=16115931011&ref_=nav_cs_r..." class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_4" data-csa-c-content-id="nav_cs_registry" data-csa-c-id="l0ut0i-vhv4tb-vs2w7g-nccbdv">
<a href="/gift-cards/b/?ie=UTF8&node=2238192011&ref..." class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_5" data-csa-c-content-id="nav_cs_gc" data-csa-c-id="paqcka-csd8y-uozx7k-yffyo3">
<a href="/b/?_encoding=UTF8&ld=AZUSSOA-sell&node=12..." class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_6" data-csa-c-content-id="nav_cs_sell" data-csa-c-id="p15i9o-b2gnps-meeyu8-zh13dd">
<span class="wdTitle _single-creative-card_style_truncation__x...">
<span class="sub-header-title-font wdSubTitle _single-creative-...">
<span class="wdTitle _single-creative-card_style_truncation__x...">
Showing first 10 of 200 failing elements.
ModerateHeading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<div class="navFooterColHead" role="heading" aria-level="6">Get to Know Us</div>
Fix any of the following:
- Heading order invalid
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html lang="en-us" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks16 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 class="navFooterLinkCol navAccessibility">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="navFooterColHead" role="heading" aria-level="6">Make Money with Us</div>
Fix any of the following:
- Some page content is not contained by landmarks
<li class="nav_first">
<a href="https://services.amazon.com/sell.html?ld=AZFSSOA&ref_=footer_soa" class="nav_a">Sell products on Amazon</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="https://services.amazon.com/amazon-business.html?ld=usb2bunifooter&ref_=footer_b2b" class="nav_a">Sell on Amazon Business</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="https://developer.amazon.com" class="nav_a">Sell apps on Amazon</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="https://affiliate-program.amazon.com/" class="nav_a">Become an Affiliate</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="https://advertising.amazon.com/?ref=ext_amzn_ftr" class="nav_a">Advertise Your Products</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="/gp/seller-account/mm-summary-page.html?ld=AZFooterSelfPublish&topic=200260520&ref_=footer_publishing" class="nav_a">Self-Publish with Us</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<li>
<a href="https://go.thehub-amazon.com/amazon-hub-locker" class="nav_a">Host an Amazon Hub</a>
</li>Fix any of the following:
- Some page content is not contained by landmarks
<a href="/b/?node=18190131011&ld=AZUSSOA-seemore&ref_=footer_seemore" class="nav_a">See More Make Money with Us</a>
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 16 failing elements.
MinorAlternative text of images should not be repeated as text3 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Failing Elements
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Start looking sharp" class="a-amazon-image _sing...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Toys for little ones" class="a-amazon-image _sing...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Level up your PC her..." class="a-amazon-image _sing...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
Passed audits50 across 1 page
[role="img"] and [role="image"] elements must have alternative text1 element
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<span class="icp-nav-flag icp-nav-flag-us icp-nav-flag-lop" role="img" aria-label="United States"></span>
<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" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
<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" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
<li> elements must be contained in a <ul> or <ol>62 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="nav-assistant-list-item ">
<li class="nav-li"> <div class="nav-div"> <a href="/Amazon-Video/b/?ie=UTF8&node=2858778011&ref_=nav_cs_prime_video" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_0" data-csa-c-content-id="nav_cs_prime_video">Prime Video</a> </div> </li>
<li class="nav-li"> <div class="nav-div"> <a href="/coupons?ref_=nav_cs_coupons" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_1" data-csa-c-content-id="nav_cs_coupons">Coupons</a> </div> </li>
<li class="nav-li"> <div class="nav-div"> <a href="/gp/help/customer/display.html?nodeId=508510&ref_=nav_cs_customerservice" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_2" data-csa-c-content-id="nav_cs_customerservice">Customer Service</a> </div> </li>
<li class="nav-li"> <div class="nav-div"> <a href="/gp/goldbox?ref_=nav_cs_gb" class="nav-a " tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav_cs_3" data-csa-c-content-id="nav_cs_gb">Today's Deals</a> </div> </li>
Showing first 5 of 62 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements11 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 aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<ul id="gwm-window" class="a-unordered-list a-nostyle a-horizontal gwm-window-wrapper">
<ul>
<ul>
<ul>
Showing first 5 of 11 audited elements.
All page content should be contained by landmarks489 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="a-page">
<a id="nav-top"></a>
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<h2 id="nav-assistant-links-heading" class="nav-assistant-heading nav-assistant-headers-font">Skip to</h2>
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
Showing first 5 of 489 audited elements.
All touch targets must be 24px large, or leave sufficient space81 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Showing first 5 of 81 audited elements.
Alternative text of images should not be repeated as text4 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 loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Kitchen must-haves" class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="All things beauty" class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Free international d..." class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Books you can't put ..." class="a-amazon-image _sing...">
ARIA attributes must be used as specified for the element's role29 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
Showing first 5 of 29 audited elements.
ARIA attributes must conform to valid names29 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
Showing first 5 of 29 audited elements.
ARIA attributes must conform to valid values27 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
Showing first 5 of 27 audited elements.
ARIA hidden element must not be focusable or contain focusable elements39 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
<hr class="nav-assistant-separator" aria-hidden="true">
<div class="keyboard-shortcut-container" aria-hidden="true">
<div class="keyboard-shortcut-container" aria-hidden="true">
<div class="keyboard-shortcut-container" aria-hidden="true">
<div class="keyboard-shortcut-container" aria-hidden="true">
Showing first 5 of 39 audited elements.
ARIA role should be appropriate for the element56 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
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<a href="javascript:void(0)" id="nav-assist-search" role="link" tabindex="-1" class="nav-assistant-menu-i..." data-nav-assist-menu...="1" data-behavior="navigate" data-actuators="[{"eventCode":"Slash..." data-target="#twotabsearchtextbox" data-modal-ignore="" ...><a href="javascript:void(0)" id="nav-assist-cart" role="link" tabindex="-1" class="nav-assistant-menu-i..." data-nav-assist-menu...="2" data-behavior="navigate" data-actuators="[{"eventKey":"Ç","ev..." data-target="/gp/cart/view.html/?..." data-modal-ignore="" aria-label="Cart, shift, alt, c" ...><a href="javascript:void(0)" id="nav-assist-home" role="link" tabindex="-1" class="nav-assistant-menu-i..." data-nav-assist-menu...="3" data-behavior="navigate" data-actuators="[{"eventKey":"Ó","ev..." data-target="/?ref_=nav_assist" data-modal-ignore="" aria-label="Home, shift, alt, h" ...><a href="javascript:void(0)" id="nav-assist-your-orde..." role="link" tabindex="-1" class="nav-assistant-menu-i..." data-nav-assist-menu...="4" data-behavior="navigate" data-actuators="[{"eventKey":"Ø","ev..." data-target="/gp/css/order-histor..." data-modal-ignore="" ...>Showing first 5 of 56 audited elements.
ARIA roles used must conform to valid values25 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
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<form id="nav-search-bar-form" accept-charset="utf-8" action="/s/ref=nb_sb_noss" class="nav-searchbar nav-progressive-attribute" method="GET" name="site-search" role="search">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Showing first 5 of 25 audited elements.
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="a-m-us a-aui_72554-c a-aui_template_weblab_cache_333406-c a-bw_aui_dark_mode_mshop_ios_1390013-t2">
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 type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
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 id="navbar-main" class="nav-opt-sprite nav-flex nav-locale-us nav-lang-en nav-ssl nav-unrec nav-progressive-attribute">
Buttons must have discernible text3 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="nav-flyout-button nav-icon nav-arrow" aria-label="Expand Account and Lists" tabindex="0" style="visibility: visible;"></button>
<button id="navBackToTop" class="navFooterBackToTopText" aria-label="Back to top"><div class="navFooterBackToTop">Back to top</div></button>
<button class="nav-arrow icp-up-down-arrow" aria-controls="nav-flyout-icp-footer-flyout" aria-label="Expand to Change Language or Country"></button>
Certain ARIA roles must be contained by particular parents8 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
<li class="gwm-window-tile" role="listitem">
<li class="gwm-window-tile" role="listitem">
<li class="gwm-window-tile" role="listitem">
<li class="gwm-window-tile" role="listitem">
<li class="gwm-window-tile" role="listitem">
Showing first 5 of 8 audited elements.
Deprecated ARIA roles must not be used25 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
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<form id="nav-search-bar-form" accept-charset="utf-8" action="/s/ref=nb_sb_noss" class="nav-searchbar nav-progressive-attribute" method="GET" name="site-search" role="search">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Showing first 5 of 25 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" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
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 id="navbar-main" class="nav-opt-sprite nav-flex nav-locale-us nav-lang-en nav-ssl nav-unrec nav-progressive-attribute">
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
<div role="main" id="gwm-Deck" class="gwm-u-blackjack-typography aok-clearfix" style="">
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" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
Elements must have their visible text as part of their accessible name4 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<a href="javascript: void(0)" id="nav-hamburger-menu" role="button" aria-label="Open All Categories Menu" aria-expanded="false" data-csa-c-type="widget" data-csa-c-slot-id="HamburgerMenuDesktop" data-csa-c-interaction-events="click">
<button id="navBackToTop" class="navFooterBackToTopText" aria-label="Back to top"><div class="navFooterBackToTop">Back to top</div></button>
<a href="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_lang" class="icp-language-link" aria-label="Choose a language for shopping. Current selection is English. ">
<a href="/customer-preferences/country?ie=UTF8&preferencesReturnUrl=%2F&ref_=footer_icp_cp" role="button" aria-label="Choose a country/region for shopping. The current selection is United States." class="icp-button" id="icp-touch-link-country">
Elements must meet minimum color contrast ratio thresholds82 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="nav-line-1 nav-progressive-content" id="glow-ingress-line1">
Deliver to
</span><span class="nav-line-2 nav-progressive-content" id="glow-ingress-line2">
New Zealand
</span><select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
<div>EN</div>
Showing first 5 of 82 audited elements.
Elements must only use permitted ARIA attributes27 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
Showing first 5 of 27 audited elements.
Elements must only use supported ARIA attributes28 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<ul aria-labelledby="nav-assistant-links-heading" class="nav-assistant-links-container">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
Showing first 5 of 28 audited elements.
Elements should not have tabindex greater than zero21 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
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<a href="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Showing first 5 of 21 audited elements.
Focused elements must not be entirely hidden by author-created content49 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a href="#skippedLink" id="nav-assist-skip-to-main-content" aria-label="main content" aria-describedby="nav-assist-shortcut-help" tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu-item-index="0" class="nav-assistant-link nav-assistant-menu-ite...
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-..." href="">
<select aria-describedby="searchDropdownDescription" class="nav-search-dropdown searchSelect nav-progressive-a..." data-nav-digest="k+fyIAyB82R9jVEmroQ0OWwSW3A=" data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progressive-attribute" dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-results-c...
Showing first 5 of 49 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
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
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Heading levels should only increase by one36 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 id="nav-assistant-links-heading" class="nav-assistant-heading nav-assistant-headers-font">Skip to</h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Shop kitchen must-haves</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Shop all things beauty</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Start looking sharp</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Free international delivery</span></div></h2>
Showing first 5 of 36 audited elements.
Headings should not be empty37 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 id="nav-assistant-links-heading" class="nav-assistant-heading nav-assistant-headers-font">Skip to</h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Shop kitchen must-haves</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Shop all things beauty</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Start looking sharp</span></div></h2>
<h2 class="a-spacing-none"><div class="a-section experimental-header-title-font"><span class="wdTitle _single-creative-card_style_truncation__x9-69 _single-creative-card_style_twoLineTruncation__16TLV a-text-bold">Free international delivery</span></div></h2>
Showing first 5 of 37 audited elements.
IDs used in ARIA and labels must be unique8 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
<h2 id="nav-assistant-links-heading" class="nav-assistant-heading nav-assistant-headers-font">Skip to</h2>
<h2 id="nav-assist-shortcuts-heading" class="nav-assistant-heading nav-assistant-headers-font font-color aok-hidden">
Keyboard shortcuts
</h2><div id="nav-assist-shortcut-help" class="aok-hidden">
<label id="searchDropdownDescription" for="searchDropdownBox" class="nav-progressive-attribute" style="display:none">Select the department you want to search in</label>
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
Showing first 5 of 8 audited elements.
Images must have alternative text7 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 loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Kitchen must-haves" class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="All things beauty" class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Start looking sharp" class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Free international d..." class="a-amazon-image _sing...">
<img loading="eager" src="https://m.media-amaz..." srcset="https://m.media-amaz..." alt="Toys for little ones" class="a-amazon-image _sing...">
Showing first 5 of 7 audited elements.
Inline text spacing must be adjustable with custom stylesheets1 element
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div role="main" id="gwm-Deck" class="gwm-u-blackjack-typography aok-clearfix" style="">
Input buttons must have discernible text1 element
Screen reader users cannot understand an input type="button"'s purpose without an accessible name. Unnamed button images provide no description of their destination, purpose, or function, leaving users unable to make informed decisions about activating them.
Audit Elements
<input id="nav-search-submit-button" type="submit" class="nav-input nav-progressive-attribute" value="Go" tabindex="0">
Interactive controls must not be nested43 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
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<option selected="selected" value="search-alias=aps">All Departments</option>
<option value="search-alias=arts-crafts-intl-ship">Arts & Crafts</option>
<option value="search-alias=automotive-intl-ship">Automotive</option>
<option value="search-alias=baby-products-intl-ship">Baby</option>
Showing first 5 of 43 audited elements.
Interactive elements must have a visible focus indicator50 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a href="#skippedLink" id="nav-assist-skip-to-main-content" aria-label="main content" aria-describedby="nav-assist-shortcut-help" tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu-item-index="0" class="nav-assistant-link nav-assistant-menu-ite...
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-..." href="">
<select aria-describedby="searchDropdownDescription" class="nav-search-dropdown searchSelect nav-progressive-a..." data-nav-digest="k+fyIAyB82R9jVEmroQ0OWwSW3A=" data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progressive-attribute" dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-results-c...
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination7 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 id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<header id="navbar-main" class="nav-opt-sprite nav-flex nav-locale-us nav-lang-en nav-ssl nav-unrec nav-progressive-attribute">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<form id="nav-search-bar-form" accept-charset="utf-8" action="/s/ref=nb_sb_noss" class="nav-searchbar nav-progressive-attribute" method="GET" name="site-search" role="search">
<div role="main" id="gwm-Deck" class="gwm-u-blackjack-typography aok-clearfix" style="">
Showing first 5 of 7 audited elements.
lang attribute must have a valid value2 elements
Screen readers use language-specific pronunciation libraries that must match the content's language. Invalid language declarations cause screen readers to use the wrong pronunciation library, making content sound confusing or unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
<a aria-label="Amazon US Home" lang="en" href="/?ref_=footer_logo">
<div class="nav-logo-base nav-sprite"></div>
</a>Links must have discernible text81 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="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
<a href="/ref=nav_logo" id="nav-logo-sprites" class="nav-logo-link nav-progressive-attribute" aria-label="Amazon" lang="en">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<a href="/customer-preferences/edit?ie=UTF8&preferencesReturnUrl=%2F&ref_=topnav_lang_ais" class="nav-a nav-a-2 icp-link-style-2" aria-label="Choose a language for shopping in Amazon United States. The current selection is English (EN). ">
<a href="https://www.amazon.c..." class="nav-a nav-a-2 nav-..." data-nav-ref="nav_ya_signin" data-nav-role="signin" data-ux-jq-mouseente...="true" tabindex="0" data-csa-c-type="link" data-csa-c-slot-id="nav-link-accountList" data-csa-c-content-i...="nav_ya_signin" ...>
Showing first 5 of 81 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
<div role="main" id="gwm-Deck" class="gwm-u-blackjack-typography aok-clearfix" style="">
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" class="a-ws a-js a-audio a-..." data-19ax5a9jf="dingo" data-aui-build-date="3.26.9-2026-10-21">
Required ARIA attributes must be provided25 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
<nav id="shortcut-menu" class="nav-assistant" aria-label="Shortcuts menu" tabindex="-1" role="navigation" data-skip-link-target-text="Main content start" data-hashed-id="" data-raw-id="">
<div id="navbar" cel_widget_id="Navigation-desktop-navbar" role="navigation" class="nav-sprite-v1 celwidget nav-bluebeacon bold-focus-hover layout2 nav-flex layout3 layout3-alt nav-packard-glow hamburger nav-progressive-attribute" aria-label="Primary">
<a id="nav-global-location-popover-link" role="button" tabindex="0" class="nav-a nav-a-2 a-popover-trigger a-declarative nav-progressive-attribute" href="">
<form id="nav-search-bar-form" accept-charset="utf-8" action="/s/ref=nb_sb_noss" class="nav-searchbar nav-progressive-attribute" method="GET" name="site-search" role="search">
<input type="text" id="twotabsearchtextbox" value="" name="field-keywords" autocomplete="off" placeholder="Search Amazon" class="nav-input nav-progre..." dir="auto" tabindex="0" aria-label="Search Amazon" role="searchbox" aria-autocomplete="list" aria-controls="sac-autocomplete-res..." ...>
Showing first 5 of 25 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div id="gwm-window-container" data-csa-c-type="widget" celwidgetid="gwm-window-container" class="window-container horizontal-parent" data-csa-op-log-render="">
Select element must have an accessible name1 element
Screen reader users cannot understand what information a select element requires without a proper label. Labels are essential for identifying form fields even when the purpose seems visually obvious, ensuring all users can complete forms successfully.
Audit Elements
<select aria-describedby="searchDropdownDescri..." class="nav-search-dropdown ..." data-nav-digest="k+fyIAyB82R9jVEmroQ0..." data-nav-selected="0" id="searchDropdownBox" name="url" style="display: block;" tabindex="0" title="Search in">
The skip-link target should exist and be focusable1 element
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="#skippedLink" id="nav-assist-skip-to-m..." aria-label="main content" aria-describedby="nav-assist-shortcut-..." tabindex="0" data-target="#skippedLink" data-scrolltarget="" data-behavior="navigate" data-nav-assist-menu...="0" class="nav-assistant-link n...">
How does your site stack up against Amazon?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Retail & E-commerce