Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Heading Hierarchy

Action

12 headings

FIX

12 headings

No H1 heading found

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

5 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Select your cookie preferences
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 Top TV
H2 Spanish TV comedies
H2 Top movies
H2 Popular European titles
H2 Amazon Originals and Exclusives
H2 Explore: Popular movies

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: black-translucent

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

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

Control	Type	Label	Method
#pv-search-nav	search	(Search)	placeholder only
#pv-search-nav	search	(Search)	placeholder only

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

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

Link & Button Quality

117 links, 149 buttons — all OK

REVIEW

117 links, 149 buttons — all OK

2 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[data-testid="pv-nav-branding"]; a[data-testid="pv-nav-branding"]

115 link(s) with descriptive text

117 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/storefront	Home	img no alt	Add alt attribute to the image
/storefront	Home	img no alt	Add alt attribute to the image

264 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[data-testid="pv-nav-branding"]; a[data-testid="pv-nav-branding"]

Why this matters

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

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 ✗

Favicon & Branding

17 icon(s) detected

REVIEW

17 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA 2 pass AA only

h2 Select your cookie preferences

1.15:1

#000000

#171514

needs 3.0:1 (large text)

24px · top of page (header area) · over background image/gradient

title Prime Video: Watch movies, TV shows, spo…

1.03:1

#000000

#00050D

needs 4.5:1 (normal text)

16px · top of page (header area)

p We use cookies and similar tools that ar…

1.19:1

#000000

#1C1812

needs 4.5:1 (normal text)

16px · top of page (header area)

a Cookie Notice

1.08:1

#000000

#100C09

needs 4.5:1 (normal text)

16px · top of page (header area)

p . We also use these cookies to understan…

1.05:1

#000000

#0C0807

needs 4.5:1 (normal text)

16px · above the fold

p If you agree, we'll also use cookies to …

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a 103 third parties

1.03:1

#000000

#00050D

needs 4.5:1 (normal text)

16px · above the fold

p use cookies on this service for their pu…

1.03:1

#000000

#00050D

needs 4.5:1 (normal text)

16px · above the fold

p To learn more about the personal informa…

2.06:1

#000000

#15465A

needs 4.5:1 (normal text)

16px · above the fold

a Privacy Notice

1.92:1

#000000

#800100

needs 4.5:1 (normal text)

16px · above the fold

p and

1.16:1

#000000

#121622

needs 4.5:1 (normal text)

16px · above the fold

a Cookie Notice

1.03:1

#000000

#06050C

needs 4.5:1 (normal text)

16px · above the fold

p Click Decline to reject or Customize to …

1.03:1

#000000

#00050D

needs 4.5:1 (normal text)

16px · above the fold

button Customize

1.76:1

#000000

#373736

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Menu

1.98:1

#000000

#403E41

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

label Browse

1.03:1

#000000

#00050D

needs 4.5:1 (normal text)

16px · mid-page

span Home

3.16:1

#000000

#5E5C5B

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

4 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)

Element	Ratio	Required	FG	BG	Result
h2 Select your cookie p…	1.15:1	3.0:1	#000000	#171514	Fail
title Prime Video: Watch m…	1.03:1	4.5:1	#000000	#00050D	Fail
p We use cookies and s…	1.19:1	4.5:1	#000000	#1C1812	Fail
a Cookie Notice	1.08:1	4.5:1	#000000	#100C09	Fail
p . We also use these …	1.05:1	4.5:1	#000000	#0C0807	Fail
p If you agree, we'll …	1.04:1	4.5:1	#000000	#050608	Fail
a 103 third parties	1.03:1	4.5:1	#000000	#00050D	Fail
p use cookies on this …	1.03:1	4.5:1	#000000	#00050D	Fail
p To learn more about …	2.06:1	4.5:1	#000000	#15465A	Fail
a Privacy Notice	1.92:1	4.5:1	#000000	#800100	Fail
p and	1.16:1	4.5:1	#000000	#121622	Fail
a Cookie Notice	1.03:1	4.5:1	#000000	#06050C	Fail
p Click Decline to rej…	1.03:1	4.5:1	#000000	#00050D	Fail
button Accept	5.68:1	4.5:1	#000000	#F43F53	Pass
button Decline	5.25:1	4.5:1	#000000	#ED374D	Pass
button Customize	1.76:1	4.5:1	#000000	#373736	Fail
span Menu	1.98:1	4.5:1	#000000	#403E41	Fail
label Browse	1.03:1	4.5:1	#000000	#00050D	Fail
span Home	3.16:1	4.5:1	#000000	#5E5C5B	Fail
span Movies	15.43:1	4.5:1	#000000	#EDDAC4	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Alt Text Quality

All 70 images OK

PASS

All 70 images OK

50 decorative image(s) correctly marked

20 image(s) with good alt text

70 images 20 good alt text 50 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 26 passed

PASS

100

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.

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
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
NEW EPISODE `ul.cards-lw1NJZ > li.card-NQEYQF > article.card-N6UUyI > a.shared-poster-link`
NEW MOVIE `ul.cards-lw1NJZ > li.card-NQEYQF > article.card-N6UUyI > a.shared-poster-link`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `section > section.headerWrapper-QHjixV > span.title-TvxgS1 > a.seeMore-toEceS`
See more `div > div.paginationWrapper-dg0_ks > div.paginationButton-WO8gtc > a._1jWggM`

○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 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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○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.

○`[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.

○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.