Skip to content
https://netflix.shop

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
41
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Alt Text Quality
Action
9 of 295 images have issues
FIX
9 of 295 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
69 decorative image(s) correctly marked
Info::
217 image(s) with good alt text
295 images 217 good alt text 69 decorative 9 missing
IssueCount
missing9 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
Theme color only
FIX
Theme color only
Info::
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: #ffffff
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 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.

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::
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 2 <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
14 landmarks
REVIEW
14 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (3 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN ASIDE CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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.

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
31 headings
REVIEW
31 headings
Info::
Single H1 present
Warning::
8 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Popular Search Terms
  • H3 Popular Titles
  • H1 Official Netflix Shop - Apparel, Collectibles & More
  • H2 Set Sail in Style
  • H2 From Jack's Bar to Your Closet
  • H2 GET IT HERE FIRST AT NETFLIX SHOP
  • H2 Happy Fans, Happy Honmoon!
  • H2 Shop What's Trending
  • H2 Stranger Things x Louis De Guzman Collab
  • H2 Sakamoto Days Vol. 2 is Here
  • H2 Best Sellers
  • H2 New Arrivals
  • H2 Shop By Title
  • H2 Shop by Category
  • H2 My Cart contains (0) items.
  • H3 You have no items in your cart.
  • H3 Shipping & Returns
  • H3 Preferred Language
  • H3 Select Your Region
  • H3 Select Your Region
  • H4 Transfer History
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H3 Collections
  • H3 All Favorites
  • H4 (empty)
  • H4 (empty)

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

C
Form Accessibility
Action
7 of 38 controls have issues
REVIEW
7 of 38 controls have issues
Critical::
7 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="email">; <input type="submit">; <input type="submit">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">
Info::
31 control(s) properly labeled
38 controls
31 labeled
0 placeholder only
7 unlabeled
ControlTypeLabelMethod
#searchInputsearchSearchfor/id
#8107797119023-1775636145978selectChoose an optionaria-label
#7969782693935-1775636145978selectChoose an optionaria-label
#8194852585519-1775636145978selectChoose an optionaria-label
#8077348995119-1775636145978selectChoose an optionaria-label
#email_016JB91TTR00000000001ZRXEJemailYour Email Addressaria-label
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
customer[email]emailEmailaria-label
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextGift card codearia-label
#rivo_transfer_credit_amountnumberAmountaria-label
#rivo_transfer_credit_messagetextareaMessage (optional)aria-label
inputtextGift URLaria-label
#rivo_claim_transfer_emailemailEmail addressaria-label
#show_gift_card_recipient_fieldscheckboxnone
#rivo_gift_card_variant_idselectGift Card Valuefor/id
#rivo_gift_card_recipient_nametextRecipient Namefor/id
#rivo_gift_card_recipient_emailemailRecipient Emailfor/id
#rivo_gift_card_delivery_datedateDelivery Datefor/id
#rivo_gift_card_messagetextareaMessagefor/id
inputtextReferral URLaria-label
#customer_accepts_marketingcheckboxnone
#customer_sms_accepts_marketingcheckboxnone
#email_01KF452TRWEGHA71WXG62CFMDXemailYour Email Addressaria-label
#Birthday_01KF452TS2BQR5BW6KQENMH51XtextBirthdayfor/id
#rivo_profile_last_nametext(none)none
#rivo_profile_emailemail(none)none
inputemail(none)none
inputtel(none)none
inputsubmit(none)none
inputsubmit(none)none
#rivo_profile_first_nametext(none)none

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

<input type="email">; <input type="submit">; <input type="submit">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">

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
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ 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 Official Netflix Shop - Apparel, Collect…
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Set Sail in Style
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From Jack's Bar to Your Closet
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 GET IT HERE FIRST AT NETFLIX SHOP
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Happy Fans, Happy Honmoon!
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop What's Trending
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stranger Things x Louis De Guzman Collab
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sakamoto Days Vol. 2 is Here
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best Sellers
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 New Arrivals
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop By Title
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop by Category
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h2 My Cart
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Popular Search Terms
1.24:1
#000000
on
#2C161A
needs 3.0:1 (large text)
19px · above the fold
h3 Popular Titles
1.24:1
#000000
on
#2D161A
needs 3.0:1 (large text)
19px · mid-page
h3 You have no items in your cart.
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Shipping & Returns
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Preferred Language
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Select Your Region
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Select Your Region
1.60:1
#000000
on
#551E28
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Official Netflix Sho…1.60:13.0:1
#000000
#551E28
Fail
h2 Set Sail in Style1.60:13.0:1
#000000
#551E28
Fail
h2 From Jack's Bar to Y…1.60:13.0:1
#000000
#551E28
Fail
h2 GET IT HERE FIRST AT…1.60:13.0:1
#000000
#551E28
Fail
h2 Happy Fans, Happy Ho…1.60:13.0:1
#000000
#551E28
Fail
h2 Shop What's Trending1.60:13.0:1
#000000
#551E28
Fail
h2 Stranger Things x Lo…1.60:13.0:1
#000000
#551E28
Fail
h2 Sakamoto Days Vol. 2…1.60:13.0:1
#000000
#551E28
Fail
h2 Best Sellers1.60:13.0:1
#000000
#551E28
Fail
h2 New Arrivals1.60:13.0:1
#000000
#551E28
Fail
h2 Shop By Title1.60:13.0:1
#000000
#551E28
Fail
h2 Shop by Category1.60:13.0:1
#000000
#551E28
Fail
h2 My Cart1.60:13.0:1
#000000
#551E28
Fail
h3 Popular Search Terms1.24:13.0:1
#000000
#2C161A
Fail
h3 Popular Titles1.24:13.0:1
#000000
#2D161A
Fail
h3 You have no items in…1.60:13.0:1
#000000
#551E28
Fail
h3 Shipping & Returns1.60:13.0:1
#000000
#551E28
Fail
h3 Preferred Language1.60:13.0:1
#000000
#551E28
Fail
h3 Select Your Region1.60:13.0:1
#000000
#551E28
Fail
h3 Select Your Region1.60:13.0:1
#000000
#551E28
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+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 32 passed
PASS
96

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●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
●Form elements have associated labels
●Select elements have associated label elements.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Uses ARIA roles only on compatible elements
●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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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