Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-j5uuw4

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://netflix.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://netflix.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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.

Landmark Structure

Action

11 landmarks

REVIEW

11 landmarks

No <main> landmark found

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

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

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 Unlimited movies, TV shows, and more

1.07:1

#000000

#100A03

needs 3.0:1 (large text)

32px · above the fold

h2 Trending Now

1.01:1

#000000

#030200

needs 3.0:1 (large text)

24px · mid-page

h2 More Reasons to Join

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Ready to watch? Enter your email to crea…

1.05:1

#000000

#040909

needs 3.0:1 (large text)

19px · above the fold

h3 The Netflix you love for just R$20.90.

1.34:1

#000000

#232323

needs 3.0:1 (large text)

19px · above the fold

h3 Enjoy on your TV

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Download your shows to watch offline

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Watch everywhere

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Create profiles for kids

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ready to watch? Enter your email to crea…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 General Description

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Essential Cookies

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 First Party Performance and Functionalit…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Third Party Performance and Functionalit…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Advertising Cookies

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Netflix - Watch TV Shows Online, Watch M…

1.06:1

#000000

#0B0907

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Unlimited movies, TV…	1.07:1	3.0:1	#000000	#100A03	Fail
h2 Trending Now	1.01:1	3.0:1	#000000	#030200	Fail
h2 More Reasons to Join	1.00:1	3.0:1	#000000	#000000	Fail
h2 Frequently Asked Que…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Privacy Preference C…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Privacy Preference C…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Ready to watch? Ente…	1.05:1	3.0:1	#000000	#040909	Fail
h3 The Netflix you love…	1.34:1	3.0:1	#000000	#232323	Fail
h3 Enjoy on your TV	1.00:1	3.0:1	#000000	#000000	Fail
h3 Download your shows …	1.00:1	3.0:1	#000000	#000000	Fail
h3 Watch everywhere	1.00:1	3.0:1	#000000	#000000	Fail
h3 Create profiles for …	1.00:1	3.0:1	#000000	#000000	Fail
h3 Ready to watch? Ente…	1.00:1	3.0:1	#000000	#000000	Fail
h3 General Description	1.00:1	3.0:1	#000000	#000000	Fail
h3 Essential Cookies	1.00:1	3.0:1	#000000	#000000	Fail
h3 First Party Performa…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Third Party Performa…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Advertising Cookies	1.00:1	3.0:1	#000000	#000000	Fail
h3 Cookie List	1.00:1	3.0:1	#000000	#000000	Fail
title Netflix - Watch TV S…	1.06:1	4.5:1	#000000	#0B0907	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.

Heading Hierarchy

30 headings, 1 skip(s)

PASS

30 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

1 hidden heading(s) (aria-hidden)

H1 Unlimited movies, TV shows, and more
H3 Ready to watch? Enter your email to create or restart your membership. skipped
H3 The Netflix you love for just R$20.90.
H2 Trending Now
H2 More Reasons to Join
H3 Enjoy on your TV
H3 Download your shows to watch offline
H3 Watch everywhere
H3 Create profiles for kids
H2 Frequently Asked Questions
H3 What is Netflix?
H3 How much does Netflix cost?
H3 Where can I watch?
H3 How do I cancel?
H3 What can I watch on Netflix?
H3 Is Netflix good for kids?
H3 Ready to watch? Enter your email to create or restart your membership.
H2 Privacy Preference Center
H2 Privacy Preference Center hidden
H3 General Description
H3 Essential Cookies
H3 First Party Performance and Functionality Cookies
H3 Third Party Performance and Functionality Cookies
H3 Advertising Cookies
H4 General Description
H4 Essential Cookies
H4 First Party Performance and Functionality Cookies
H4 Third Party Performance and Functionality Cookies
H4 Advertising Cookies
H3 Cookie List

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

1 decorative image(s) correctly marked

2 image(s) with good alt text

3 images 2 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 11 controls labeled

PASS

All 11 controls labeled

11 control(s) properly labeled

11 controls

11 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#:R2l6lalalalb96:	select	Select Language	for/id
#:r0:	email	Email address	for/id
#:r6:	email	Email address	for/id
#:R59qlbanb96:	select	Select Language	for/id
#ot-group-id-C0003	checkbox	Third Party Performance and Functionality Cookies	for/id
#ot-group-id-C0004	checkbox	Advertising Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#chkbox-id	checkbox	checkbox label	for/id

Link & Button Quality

1 issue(s) across 31 links and 33 buttons

PASS

1 issue(s) across 31 links and 33 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://help.netflix.com/legal/privacy#cookies ("here")

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.onetrust.com/products/cookie-consent/

29 link(s) with descriptive text

31 links

0 empty

1 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://help.netflix.com/legal/privacy#c…	here	generic text	Replace with descriptive text
Before: here Suggested: Privacy#Cookies
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text

62 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://help.netflix.com/legal/privacy#cookies ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.onetrust.com/products/cookie-consent/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 27 passed

PASS

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ready to watch? Enter your email to create or restart your membership. `div.default-ltr-iqcdef-cache-1josprq > div.default-ltr-iqcdef-cache-noi56b > form.default-ltr-iqcdef-cache-14nc2q6 > h3.default-ltr-iqcdef-cache-18zqjlh`

These are opportunities to improve keyboard navigation in your application.

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●`<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.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●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

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

○Image elements have `[alt]` attributes

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

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