Skip to content
https://amazon.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Shortcuts menu" MAIN ASIDE "Your recently viewed items and featured recommendations" CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

C
Heading Hierarchy
Action
42 headings, 1 skip(s)
REVIEW
42 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Cookies and Advertising Choices
  • H2 Skip to
  • H2 Keyboard shortcuts
  • H2 Best sellers in Electronics
  • H2 Save on Amazon DevicesSave on Amazon Devices
  • H2 Best sellers in Home
  • H2 Sign in for your best experienceSign in for your best experience
  • H2 Buy more & save: Up to 40% off
  • H2 Top dealsTop deals
  • H2 Get 10 € off with first app purchase
  • H2 Free delivery on Lieferando
  • H2 Shop in your currency
  • H2 Best Sellers in Computer & Accessories
  • H2 Best Sellers in Sports & Outdoors
  • H2 Refurbished home and kitchen
  • H2 Refurbished productsRefurbished products
  • H2 Shop seasonal outfits for less
  • H2 Deals on sports gear
  • H2 Shop all Italian products
  • H2 Best Sellers in Books
  • H2 Refurbished tech under 50 €
  • H2 Fashion accessories
  • H2 Spring starts here. All under €20
  • H2 Made in Italy products
  • H2 Best Sellers in Home & Kitchen
  • H2 Most wished for in DVD & Blu-ray
  • H2 Shop Spring Essentials
  • H2 Spring essentials from €1.99
  • H2 "Wuthering Heights"
  • H2 Unlock exclusive savings on baby items
  • H2 Most wished for in PC & Video Games
  • H5 Amazon Advertising skipped
  • H5 Amazon Music
  • H5 AbeBooks
  • H5 Amazon Web Services
  • H5 Audible
  • H5 IMDb
  • H5 Kindle Direct Publishing
  • H5 Shopbop
  • H5 Amazon Resale
  • H5 ZVAB
  • H5 Amazon Business

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

B
Alt Text Quality
1 of 218 images have issues
REVIEW
1 of 218 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
9 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
206 image(s) with good alt text
218 images 206 good alt text 2 decorative 1 missing
IssueCount
missing1 image(s)
too long9 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

C
Form Accessibility
Action
3 of 7 controls have issues
REVIEW
3 of 7 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="nav-search-submit-button">; <input type="submit">; <input type="submit">
Info::
4 control(s) properly labeled
7 controls
4 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#sp-cc-acceptsubmitAcceptaria-label
#sp-cc-rejectall-linksubmitDeclinearia-label
#searchDropdownBoxselectSelect the department you want to search infor/id
#twotabsearchtextboxtextSearch Amazon.dearia-label
#nav-search-submit-buttonsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" id="nav-search-submit-button">; <input type="submit">; <input type="submit">

Why this matters

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Seite wurde nicht gefunden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Skip to15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Keyboard shortcuts15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Best sellers in Elec…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Best sellers in Home15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Buy more & save: Up …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Get 10 € off with …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Free delivery on Lie…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Shop in your currenc…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Refurbished home and…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Shop seasonal outfit…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Deals on sports gear15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Refurbished tech und…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Fashion accessories15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Spring starts here. …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Made in Italy produc…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Shop Spring Essentia…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Spring essentials fr…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 "Wuthering Heights"15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Unlock exclusive sav…15.46:13.0:1
#000000
#DDDDDD
Pass
title Amazon.de: Low Price…15.46:14.5:1
#000000
#DDDDDD
Pass

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.

A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 32 passed
PASS
93

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Amazon.de form#nav-search-form > div.nav-fill > div.nav-search-field > input#nav-search-keywords
Your first delivery is FREE Click here to learn more T&Cs apply Shop deals endi… div#gwm-Deck > div#gwm-Deck-cf > div#gwm-window-container > ul#gwm-window

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Notice div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a
Imprint div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a
Interest-Based Ads Notice div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0 div#navbar > div#nav-logobar > div.nav-right > a#nav-button-cart
Men's watches Men's watches div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Women's watches Women's watches div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Women's jewellery Women's jewellery div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Bags & Suitcases Bags & Suitcases div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Beauty Beauty div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Staples Staples div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
New in New in div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Trending Trending div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Spring favourites Spring favourites div#CardInstanceHXMSXtJd5mPiggnQDOM7Aw > div.a-cardui-body > div.a-section > a.a-link-normal
Fashion Fashion div.a-cardui-body > div.a-section > div.a-section > a.a-link-normal
Picnic Picnic div.a-cardui-body > div.a-section > div.a-section > a.a-link-normal
Beauty Beauty div.a-cardui-body > div.a-section > div.a-section > a.a-link-normal
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback