Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Heading Hierarchy

Action

113 headings

FIX

113 headings

No H1 heading found

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

50 empty heading(s)

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

H2 Welcome.
H3 Millions of movies, TV shows and people to discover. Explore now.
H2 Trending
H3 Today
H3 This Week
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 Latest Trailers
H3 Popular
H3 Streaming
H3 On TV
H3 For Rent
H3 In Theaters
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 (empty)
H3 (empty)
H2 What's Popular
H3 Streaming
H3 On TV
H3 For Rent
H3 In Theaters
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 Free To Watch
H3 Movies
H3 TV
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 Join Today
H2 Leaderboard
H3 RuiZafon
H4 2,205,118
H4 44,112
H3 Shei
H4 2,720,357
H4 33,446
H3 Samara
H4 4,589,013
H4 21,562
H3 enterpr1se
H4 2,714,416
H4 20,833
H3 Roman
H4 621,442
H4 19,233
H3 Stuxmovy
H4 65,591
H4 13,186
H3 TMDB-Import | 此剧由TMDB-Helper托管自动维护···
H4 100,161
H4 11,856
H3 beepol4
H4 202,242
H4 8,474
H3 veposid
H4 96,493
H4 8,409
H3 3298021
H4 38,953
H4 6,383
H3 The Basics
H3 Get Involved
H3 Community
H3 Legal
H3 Global
H3 On media pages
H3 On TV season pages
H3 On TV episode pages
H3 On all image pages
H3 On all edit pages
H3 On discussion pages
H3 Settings

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

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: #032541

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

2 of 5 controls have issues

REVIEW

2 of 5 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">

3 control(s) properly labeled

5 controls

3 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#search_v4	text		none
#inner_search_v4	text		none
#toggle_keyboard_shortcuts	checkbox		none
input	submit	(none)	none
input	submit	(none)	none

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

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

Link & Button Quality

2 issue(s) across 82 links and 3 buttons

REVIEW

2 issue(s) across 82 links and 3 buttons

1 link(s) with generic text

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

Got: ("More")

3 link(s) open in new tab without warning

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

Got: /docs; https://developer.themoviedb.org/docs; https://status.themoviedb.org/

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="submit"].k-button (#295 on page)

78 link(s) with descriptive text

82 links

0 empty

1 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	More	generic text	Replace with descriptive text
Before: More Suggested: Home page
/docs	API Documentation	new tab	Add '(opens in new tab)' to text
https://developer.themoviedb.org/docs	API Documentation	new tab	Add '(opens in new tab)' to text
https://status.themoviedb.org/	System Status	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label

80 links and buttons have descriptive text

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

("More")

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.

/docs; https://developer.themoviedb.org/docs; https://status.themoviedb.org/

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

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="submit"].k-button (#295 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found — The Movie Database (TMDB) ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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 Present

✓ Multiple Sizes Present

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

h2 Welcome.

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trending

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest Trailers

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What's Popular

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Free To Watch

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join Today

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Leaderboard

1.34:1

#000000

#032541

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Millions of movies, TV shows and people …

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The Basics

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get Involved

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Community

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Legal

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Global

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On media pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On TV season pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On TV episode pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On all image pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On all edit pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 On discussion pages

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Settings

1.34:1

#000000

#032541

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Welcome.	1.34:1	3.0:1	#000000	#032541	Fail
h2 Trending	1.34:1	3.0:1	#000000	#032541	Fail
h2 Latest Trailers	1.34:1	3.0:1	#000000	#032541	Fail
h2 What's Popular	1.34:1	3.0:1	#000000	#032541	Fail
h2 Free To Watch	1.34:1	3.0:1	#000000	#032541	Fail
h2 Join Today	1.34:1	3.0:1	#000000	#032541	Fail
h2 Leaderboard	1.34:1	3.0:1	#000000	#032541	Fail
h3 Millions of movies, …	1.34:1	3.0:1	#000000	#032541	Fail
h3 The Basics	1.34:1	3.0:1	#000000	#032541	Fail
h3 Get Involved	1.34:1	3.0:1	#000000	#032541	Fail
h3 Community	1.34:1	3.0:1	#000000	#032541	Fail
h3 Legal	1.34:1	3.0:1	#000000	#032541	Fail
h3 Global	1.34:1	3.0:1	#000000	#032541	Fail
h3 On media pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 On TV season pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 On TV episode pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 On all image pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 On all edit pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 On discussion pages	1.34:1	3.0:1	#000000	#032541	Fail
h3 Settings	1.34:1	3.0:1	#000000	#032541	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.

Landmark Structure

4 landmarks

PASS

4 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 8 images OK

PASS

All 8 images OK

8 image(s) with good alt text

8 images 8 good alt text

All images have appropriate alt text.

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: The Movie Database

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name The Movie Database ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name The Movie Database Display Mode standalone Theme Color #032541 Background Color #032541 Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 31 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#inner_search_form > label.inner_search_wrapper > span.k-input > input#inner_search_v4 `form#inner_search_form > label.inner_search_wrapper > span.k-input > input#inner_search_v4`
Reject All `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler`
Accept All Cookies `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

○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

●Input buttons have discernible text.

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●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

●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

●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

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

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

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

○Uses ARIA roles only on compatible elements

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