Checked 8/31/2026 · https://www.amazon.de/
1 critical barrier · plus 1 to check.
How is the score formed? (100 starting points)
| <title> missing or empty | -18 |
| No <h1> heading in the delivered HTML | -7 |
| Result | 75 / 100 |
Operable
<title> missing or empty
The page title is the first orientation for screen-reader and tab users.
<head>
This is what you should do: Assign a meaningful, page-specific <title>.
No <h1> heading in the delivered HTML
Each page should begin with exactly one h1. On pages built via JavaScript the h1 may only appear in the browser — then check in the rendered DOM.
body
This is what you should do: Insert a meaningful <h1> as the first heading (ideally already server-side).
Next steps
- <title> missing or empty. Assign a meaningful, page-specific <title>.
- No <h1> heading in the delivered HTML. Insert a meaningful <h1> as the first heading (ideally already server-side).
Weekly re-scan, JS-rendered, email on new barriers — coming soon.
Create an accessibility statement →
Method & limits
On 8/31/2026 the HTML that www.amazon.de delivers on a first visit without login was checked, plus up to four linked CSS files from the same domain. Checked: colour contrast (from CSS), text alternatives, form labelling, names of controls, heading structure, page title and page language, zoom lock, duplicate ids, positive tabindex values, landmarks.
Not checked: anything that arises via JavaScript, keyboard operability, visible focus, focus order, screen-reader announcement, content behind login, subpages. The automated test finds roughly 20–35% of WCAG breaches — the rest needs a manual check. A snapshot, not a legal decision.