Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction8 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
DHeading HierarchyAction67 headings, 3 skip(s)FIX
- H2 Skip to
- H2 Keyboard shortcuts
- H1 Free with Prime
- H4 Ask more of your AI assistant skipped
- H2 Get Alexa+
- H5 Ready wherever you are skipped
- H5 Gets more done
- H5 Easy to talk to
- H5 Tailored to you
- H2 Compare Alexa+ plans
- H3 Free
- H3 Prime
- H3 Standard
- H2 Alexa+ has entered the chat
- H2 Ready wherever you are
- H2 (empty)
- H3 Alexa app
- H3 Echo devices
- H3 Fire TV
- H3 Fire Tablets
- H2 Does more for you every day
- H2 Your conversations, your way
- H2 (empty)
- H3 Talk naturally
- H3 Jump right in
- H3 Pivots welcome
- H3 Uniquely yours
- H2 Yours. Truly.
- H2 Intelligence that’s right at home
- H2 Got Prime? You’ve got Alexa+
- H3 Designed for Alexa+
- H2 Trust is built intoAlexa+ by design
- H3 Private
- H3 Secure
- H3 Trusted
- H2 Frequently asked questions
- H5 Amazon Music skipped
- H5 Amazon Ads
- H5 6pm
- H5 AbeBooks
- H5 ACX
- H5 Sell on Amazon
- H5 Veeqo
- H5 Amazon Business
- H5 Amazon Fresh
- H5 AmazonGlobal
- H5 Home Services
- H5 Amazon Web Services
- H5 Audible
- H5 Box Office Mojo
- H5 Goodreads
- H5 IMDb
- H5 IMDbPro
- H5 Kindle Direct Publishing
- H5 Amazon Photos
- H5 Prime Video Direct
- H5 Shopbop
- H5 Amazon Resale
- H5 Whole Foods Market
- H5 Woot!
- H5 Zappos
- H5 Ring
- H5 eero WiFi
- H5 Blink
- H5 Neighbors App
- H5 PillPack
- H5 Amazon Renewed
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Empty headings appear in the document outline but provide no information.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
FLink & Button QualityAction5 issue(s) across 256 links and 73 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| (empty) | empty | Add link text or aria-label | |
| /alexaplus?ref_=MARS_NAVSTRIPE_desktop_b… | Echo | img no alt | Add alt attribute to the image |
| (empty) | empty | Add link text or aria-label | |
| # | Go to Alexa | img no alt | Add alt attribute to the image |
| https://www.amazon.com/amazonprime?ref_=… | learn more | generic text | Replace with descriptive text |
Before: learn more Suggested: Amazonprime?Ref =Xaa Spp D Ap Li | |||
| /dp/B0DC91H3JK?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DC8ZMR1P?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DMQ1QMVV?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0D6SX8VLQ?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0FD44PTYN?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0FD4435WL?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DD28FS3D?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DD2P7YVW?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DD2F6VXT?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DD24KM9Y?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DFNFX2K7?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DFNTKTYN?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DFNPK1D3?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0DSYMDC8Y?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| /dp/B0F758GJFX?ref_=amzdv_dscx_rpc_d_clk… | See all details | new tab | Add '(opens in new tab)' to text |
| https://www.amazon.com/alexaplus#whybuys | here | generic text | Replace with descriptive text |
Before: here Suggested: Alexaplus#Whybuys | |||
| https://www.amazon.com/hz5/yourmembershi… | here | generic text | Replace with descriptive text |
Before: here Suggested: Yourmembershipsandsubscriptions?Ref =Xaa Spp Faq D Li Yms | |||
Links without text are announced as raw URLs by screen readers.
a#nav-top; a#skippedLink
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
https://www.amazon.com/amazonprime?ref_=xaa_spp_d_ap_li ("learn more"); https://www.amazon.com/alexaplus#whybuys ("here"); https://www.amazon.com/hz5/yourmembershipsandsubscriptions?ref_=xaa_spp_faq_d… ("here")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="/alexaplus?ref_=MARS_NAVSTRIPE_desktop_bar_echo_logo"]; a[href="#"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
/dp/B0DC91H3JK?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DC91H3JK; /dp/B0DC8ZMR1P?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DC8ZMR1P; /dp/B0DMQ1QMVV?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DMQ1QMVV; /dp/B0D6SX8VLQ?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0D6SX8VLQ; /dp/B0FD44PTYN?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0FD44PTYN; /dp/B0FD4435WL?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0FD4435WL; /dp/B0DD28FS3D?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DD28FS3D; /dp/B0DD2P7YVW?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DD2P7YVW; /dp/B0DD2F6VXT?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DD2F6VXT; /dp/B0DD24KM9Y?ref_=amzdv_dscx_rpc_d_clk_banyanspp_B0DD24KM9Y (+5 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FFavicon & BrandingAction1 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CAlt Text QualityAction3 of 58 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 3 image(s) |
| too long | 15 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
CColor Contrast (Screenshot)Action20 text elements analyzed, 16 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Free with Prime | 1.44:1 | 3.0:1 | #000000 | #272929 | Fail |
| h2 Skip to | 4.45:1 | 3.0:1 | #000000 | #6E747B | Pass |
| h2 Keyboard shortcuts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Get Alexa+ | 1.44:1 | 3.0:1 | #000000 | #272929 | Fail |
| h2 Compare Alexa+ plans | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Free | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Prime | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Standard | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Alexa app | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Echo devices | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Fire TV | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Fire Tablets | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Talk naturally | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Jump right in | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Pivots welcome | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| h3 Uniquely yours | 1.29:1 | 3.0:1 | #0F1111 | #272929 | Fail |
| title Alexa Plus | 6.91:1 | 4.5:1 | #000000 | #929497 | Pass |
| a Main content | 1.55:1 | 4.5:1 | #000000 | #232F3E | Fail |
| span Search | 20.65:1 | 4.5:1 | #000000 | #FDFDFD | Pass |
| span alt | 1.14:1 | 4.5:1 | #000000 | #0E151A | Fail |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
BLighthouse Accessibility AuditsScore 82/100 — 7 failing, 30 passedREVIEW
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search Amazon form#nav-search-form > div.nav-fill > div.nav-search-field > input#nav-search-keywords |
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
New Devices div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Smart Displays div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Smart Speakers div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Fire TVs div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Smart Home div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
On-the-go div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Kids div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
Tablets div#ucw-widget-upsell--1537871196 > div#ucw-widget-upsell-category--1537871196 > ul#ucw-category-list--1537871196 > li.a-spacing-small |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Ask more of your AI assistant div.a-row > div.a-column > div.a-row > h4.a-color-inverse |
Ready wherever you are div.content-grid-col-wrapper > div.a-column > div.content-grid-block > h5 |
These are opportunities to improve keyboard navigation in your application.
Names and labels
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-1c1990ac-113f-4335-8318-8d2888c9fe27 > img.content-grid-cinemagraph-placeholder div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-1c1990ac-113f-4335-8318-8d2888c9fe27 > img.content-grid-cinemagraph-placeholder |
div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-85e3fc44-0f83-4f10-895e-aa22d773153f > img.content-grid-cinemagraph-placeholder div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-85e3fc44-0f83-4f10-895e-aa22d773153f > img.content-grid-cinemagraph-placeholder |
div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-f9b69314-d183-4d9d-80ea-30fa620e50ed > img.content-grid-cinemagraph-placeholder div.a-column > div.content-grid-block > video#ods-cg-cinemagraph-f9b69314-d183-4d9d-80ea-30fa620e50ed > img.content-grid-cinemagraph-placeholder |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Conditions of Use div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a |
Privacy Notice div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a |
Consumer Health Data Privacy Disclosure div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a |
Your Ads Privacy Choices div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.a-touch html.a-touch |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
0 div#navbar > div#nav-logobar > div.nav-right > a#nav-button-cart |
AForm Accessibility1 of 3 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #searchDropdownBox | select | Select the department you want to search in | for/id |
| #twotabsearchtextbox | text | Search Amazon | aria-label |
| #nav-search-submit-button | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="nav-search-submit-button">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2