Skip to content
https://paramountplus.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-a9bu5v
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
1 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 1 <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
Heading Hierarchy
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Info::
1 hidden heading(s) (aria-hidden)
  • H2 Review and Manage Your Cookie Settings
  • H2 Review and Manage Your Cookie Settings hidden
  • H3 Your Privacy
  • H4 Your Privacy
  • H3 Essential
  • H4 Essential
  • H3 Analytic & Performance
  • H4 Analytic & Performance
  • H3 Functional
  • H4 Functional
  • H3 Marketing and Advertising
  • H4 Marketing and Advertising
  • H3 Social Media
  • H4 Social Media
  • H3 Advertising Cookies

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

B
Form Accessibility
2 of 12 controls have issues
REVIEW
2 of 12 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
10 control(s) properly labeled
12 controls
10 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#emailtextShare your email address to stay up-to-date on Paramount+ news*.for/id
#ot-group-id-2checkboxAnalytic & Performancefor/id
#ot-group-id-3checkboxFunctionalfor/id
#ot-group-id-4checkboxMarketing and Advertisingfor/id
#ot-group-id-5checkboxSocial Mediafor/id
#vendor-search-handlertextVendor Searcharia-label
#select-all-vendor-leg-handlercheckboxSelect All Vendorsfor/id
#select-all-vendor-groups-handlercheckboxSelect All Vendorsfor/id
#select-all-hosts-groups-handlercheckboxSelect All Hostsfor/id
#storage-access-groupcheckboxInformation storage and accessfor/id
#g-recaptcha-response-100000textarea(none)none
#g-recaptcha-responsetextarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ 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
h2 Review and Manage Your Cookie Settings
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Review and Manage Your Cookie Settings
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Your Privacy
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Essential
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Analytic & Performance
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Functional
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Marketing and Advertising
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Social Media
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Advertising Cookies
1.09:1
#000000
on
#040E1E
needs 3.0:1 (large text)
19px · bottom of viewport
title Paramount+ - Stream live TV, Movies, Ori…
1.12:1
#000000
on
#081220
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sign In
1.15:1
#000000
on
#0D1525
needs 4.5:1 (normal text)
16px · top of page (header area)
p UNIQUE STORIES.
1.17:1
#000000
on
#021732
needs 4.5:1 (normal text)
16px · top of page (header area)
p ICONIC STARS.
1.13:1
#000000
on
#001233
needs 4.5:1 (normal text)
16px · top of page (header area)
p A MOUNTAIN OF ENTERTAINMENT.
1.16:1
#000000
on
#001437
needs 4.5:1 (normal text)
16px · above the fold
p Paramount+, home to the world’s favour…
1.20:1
#000000
on
#00183C
needs 4.5:1 (normal text)
16px · above the fold
div Share your email address to stay up-to-d…
1.16:1
#000000
on
#001437
needs 4.5:1 (normal text)
16px · above the fold
label Share your email address to stay up-to-d…
1.25:1
#000000
on
#061D3D
needs 4.5:1 (normal text)
16px · above the fold
div Submit
1.17:1
#000000
on
#041732
needs 4.5:1 (normal text)
16px · above the fold
div By clicking the submit button, you agree…
1.24:1
#000000
on
#041E32
needs 4.5:1 (normal text)
16px · above the fold
a Privacy Policy
1.18:1
#000000
on
#05182E
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Review and Manage Yo…1.09:13.0:1
#000000
#040E1E
Fail
h2 Review and Manage Yo…1.09:13.0:1
#000000
#040E1E
Fail
h3 Your Privacy1.09:13.0:1
#000000
#040E1E
Fail
h3 Essential1.09:13.0:1
#000000
#040E1E
Fail
h3 Analytic & Performan…1.09:13.0:1
#000000
#040E1E
Fail
h3 Functional1.09:13.0:1
#000000
#040E1E
Fail
h3 Marketing and Advert…1.09:13.0:1
#000000
#040E1E
Fail
h3 Social Media1.09:13.0:1
#000000
#040E1E
Fail
h3 Advertising Cookies1.09:13.0:1
#000000
#040E1E
Fail
title Paramount+ - Stream …1.12:14.5:1
#000000
#081220
Fail
a Sign In1.15:14.5:1
#000000
#0D1525
Fail
p UNIQUE STORIES.1.17:14.5:1
#000000
#021732
Fail
p ICONIC STARS.1.13:14.5:1
#000000
#001233
Fail
p A MOUNTAIN OF ENTERT…1.16:14.5:1
#000000
#001437
Fail
p Paramount+, home to …1.20:14.5:1
#000000
#00183C
Fail
div Share your email add…1.16:14.5:1
#000000
#001437
Fail
label Share your email add…1.25:14.5:1
#000000
#061D3D
Fail
div Submit1.17:14.5:1
#000000
#041732
Fail
div By clicking the subm…1.24:14.5:1
#000000
#041E32
Fail
a Privacy Policy1.18:14.5:1
#000000
#05182E
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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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 3 images OK
PASS
All 3 images OK
Info::
3 image(s) with good alt text
3 images 3 good alt text
All images have appropriate alt text.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Paramount+
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Paramount+ ✓192×192 icon ✓512×512 icon ✓Start URL https://www.paramountplus.com/ ✓Display Mode standalone ✓
Name Paramount+ Display Mode standalone Theme Color #1d1d1d Background Color #1d1d1d Icons 7 icon(s)
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 26 passed
PASS
93

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
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.grid-wrapper > div.grid-item > div.field-wrapper > input#email div.grid-wrapper > div.grid-item > div.field-wrapper > input#email
SUBMIT form#feedback-form > div.grid-wrapper > div.grid-item > button#submit_btn

These are opportunities to improve keyboard navigation in your application.

○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.
●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 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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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
○Heading elements appear in a sequentially-descending order
○`<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
○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.

Send Feedback