Skip to content
https://amazonvideo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 "Navigation Bar" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

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

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="phrase" id="pv-search-nav">; <input type="search" name="phrase" id="pv-search-nav">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#pv-search-navsearch(Search)placeholder only
#pv-search-navsearch(Search)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="phrase" id="pv-search-nav">; <input type="search" name="phrase" id="pv-search-nav">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title That shouldn't have happened. ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
17 icon(s) detected
REVIEW
17 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Watch movies, series, and more
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
32px · bottom of viewport
title Prime Video: Watch movies, TV shows, spo…
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
1.06:1
#000000
on
#060B12
needs 4.5:1 (normal text)
16px · top of page (header area)
label Browse
1.22:1
#000000
on
#07193E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Home
1.13:1
#000000
on
#09122A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Movies
1.13:1
#000000
on
#0A112C
needs 4.5:1 (normal text)
16px · above the fold
span TV shows
1.14:1
#000000
on
#0B122D
needs 4.5:1 (normal text)
16px · above the fold
span Sports
1.15:1
#000000
on
#0C132D
needs 4.5:1 (normal text)
16px · above the fold
span News
1.10:1
#000000
on
#080E22
needs 4.5:1 (normal text)
16px · above the fold
span Live TV
1.02:1
#000000
on
#01040B
needs 4.5:1 (normal text)
16px · above the fold
label Subscriptions
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · above the fold
span Browse all
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · above the fold
span Home
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · above the fold
span Movies
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · above the fold
span TV shows
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page
span Sports
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page
span News
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page
span Live TV
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page
span Subscriptions
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page
button Clear
1.03:1
#000000
on
#00050D
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Watch movies, series…1.32:13.0:1
#000000
#222222
Fail
title Prime Video: Watch m…1.03:14.5:1
#000000
#00050D
Fail
span Menu1.06:14.5:1
#000000
#060B12
Fail
label Browse1.22:14.5:1
#000000
#07193E
Fail
span Home1.13:14.5:1
#000000
#09122A
Fail
span Movies1.13:14.5:1
#000000
#0A112C
Fail
span TV shows1.14:14.5:1
#000000
#0B122D
Fail
span Sports1.15:14.5:1
#000000
#0C132D
Fail
span News1.10:14.5:1
#000000
#080E22
Fail
span Live TV1.02:14.5:1
#000000
#01040B
Fail
label Subscriptions1.03:14.5:1
#000000
#00050D
Fail
span Browse all1.03:14.5:1
#000000
#00050D
Fail
span Home1.03:14.5:1
#000000
#00050D
Fail
span Movies1.03:14.5:1
#000000
#00050D
Fail
span TV shows1.03:14.5:1
#000000
#00050D
Fail
span Sports1.03:14.5:1
#000000
#00050D
Fail
span News1.03:14.5:1
#000000
#00050D
Fail
span Live TV1.03:14.5:1
#000000
#00050D
Fail
span Subscriptions1.03:14.5:1
#000000
#00050D
Fail
button Clear1.03:14.5:1
#000000
#00050D
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.

A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Watch movies, series, and more
A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
3 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
4 images 1 good alt text 3 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 23 passed
PASS
98

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.a-touch html.a-touch

These items highlight common accessibility best practices.

○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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●`[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
●`[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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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