Skip to content
https://plex.tv

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 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
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.
B
Landmark Structure
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title The page you were looking for doesn't exist (404) ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark light
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: #000000
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta dark light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 Welcome to Plex!
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Frequently Asked Questions
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Explore
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · above the fold
h3 Learn More
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · above the fold
h3 Categories
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · above the fold
h3 Explore
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Featured Channels
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Categories
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Company
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Watch Free on Plex
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Discover
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 My Media
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.26:1
#000000
on
#1E1E1E
needs 3.0:1 (large text)
19px · bottom of viewport
label Find Movies & TV
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Live TV
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
span On Demand
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Discover
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
div Movies & TV Shows
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div Most Popular
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
div Leaving Soon
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welcome to Plex!1.26:13.0:1
#000000
#1E1E1E
Fail
h2 Frequently Asked Que…1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Explore1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Learn More1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Categories1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Explore1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Featured Channels1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Categories1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Company1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Watch Free on Plex1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Discover1.26:13.0:1
#000000
#1E1E1E
Fail
h3 My Media1.26:13.0:1
#000000
#1E1E1E
Fail
h3 Resources1.26:13.0:1
#000000
#1E1E1E
Fail
label Find Movies & TV1.26:14.5:1
#000000
#1E1E1E
Fail
span Live TV1.26:14.5:1
#000000
#1E1E1E
Fail
span On Demand1.26:14.5:1
#000000
#1E1E1E
Fail
span Discover1.26:14.5:1
#000000
#1E1E1E
Fail
div Movies & TV Shows1.26:14.5:1
#000000
#1E1E1E
Fail
div Most Popular1.26:14.5:1
#000000
#1E1E1E
Fail
div Leaving Soon1.26:14.5:1
#000000
#1E1E1E
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
32 headings
PASS
32 headings
Info::
Single H1 present
  • H3 Explore
  • H3 Learn More
  • H3 Categories
  • H3 Explore
  • H3 Featured Channels
  • H3 Categories
  • H1 Welcome to Plex!
  • H2 Browse Movies & TV Shows
  • H2 What's On Now
  • H2 Binge-Worthy Shows
  • H2 Plex Picks
  • H2 Spring Reawakenings
  • H2 Most Popular in Spain
  • H2 Til Death Do Us Part
  • H2 Recently Added
  • H2 Most Watchlisted This Week
  • H2 Trending Trailers
  • H2 Coming Soon
  • H2 Trending on Apple TV
  • H2 Frequently Asked Questions
  • H3 Is Plex really free?
  • H3 Where is Plex available?
  • H3 Where can I watch Plex?
  • H3 Do I need a Plex account?
  • H3 How can I personalize my Plex experience?
  • H3 What is Plex Pass? And can I use it to watch Plex ad-free?
  • H3 Can I use Plex to enjoy my own personal media?
  • H3 Company
  • H3 Watch Free on Plex
  • H3 Discover
  • H3 My Media
  • H3 Resources
A+
Alt Text Quality
All 207 images OK
PASS
All 207 images OK
Info::
207 decorative image(s) correctly marked
207 images 207 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#universalSearch-inputsearchFind Movies & TVfor/id
#locale-selectselectSelect a languagearia-label
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 26 passed
PASS
97

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
18% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
52% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
67% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
88% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
39% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
49% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
4% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
10% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
42% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
49% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
43% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
54% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0
65% complete div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○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
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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
●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
○Links are distinguishable without relying on color.
○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.
○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