Paramount+ paramountplus.com
Accessibility score
League position
9thof 10
Issues found
2
Audits passed
31
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements should not have tabindex greater than zero2 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Failing Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
Fix any of the following:
- Element has a tabindex greater than 0
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<div class="button__text">Submit</div>
</button>Fix any of the following:
- Element has a tabindex greater than 0
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html lang="en-us">
Fix all of the following:
- Page must have a level-one heading
Passed audits31 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en-us">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en-us">
All page content should be contained by landmarks40 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<main id="main-container">
<section class="padded-container">
<div class="logo">
<img src="/assets/images/intl-landing-page/pplus_marketing_site_logo_white.png" alt="Paramount+" width="100%">
</div><img src="/assets/images/intl-landing-page/pplus_marketing_site_logo_white.png" alt="Paramount+" width="100%">
<div class="header">
<p>UNIQUE STORIES.</p>
<p>ICONIC STARS.</p>
<p>A MOUNTAIN OF ENTERTAINMENT.</p>
</div>Showing first 5 of 40 audited elements.
All touch targets must be 24px large, or leave sufficient space2 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<div class="button__text">Submit</div>
</button>Alternative text of images should not be repeated as text1 element
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="/assets/images/intl-landing-page/pplus_marketing_site_logo_white.png" alt="Paramount+" width="100%">
ARIA role should be appropriate for the element2 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<iframe title="reCAPTCHA" width="256" height="60" role="presentation" name="a-pxcp1s7jroxz" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.recaptch...">
<iframe title="reCAPTCHA" width="256" height="60" role="presentation" name="a-y57kmcgi1wur" frameborder="0" scrolling="no" sandbox="allow-forms allow-po..." src="https://www.recaptch...">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="round-corners intl property-nz">
Buttons must have discernible text1 element
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<div class="button__text">Submit</div>
</button>Content must reflow without two-dimensional scrolling0 elements
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer>
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en-us">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer>
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main id="main-container">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en-us">
Elements must meet minimum color contrast ratio thresholds3 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
<textarea id="g-recaptcha-response" name="g-recaptcha-response" class="g-recaptcha-response" style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
<textarea id="g-recaptcha-response-100000" name="g-recaptcha-response" class="g-recaptcha-response" style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
Focused elements must not be entirely hidden by author-created content8 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<a href="https://www.pplus.legal/privacy">
<a href="https://www.skyshowtime.com/where-can-i-stream">
<a rel="noopener" href="https://www.pplus.legal/tou" target="_blank">
Showing first 5 of 8 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
IDs used in ARIA and labels must be unique1 element
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
Images must have alternative text1 element
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="/assets/images/intl-landing-page/pplus_marketing_site_logo_white.png" alt="Paramount+" width="100%">
Interactive controls must not be nested2 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<img src="/assets/images/intl-landing-page/pplus_marketing_site_logo_white.png" alt="Paramount+" width="100%">
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<div class="button__text">Submit</div>
</button>Interactive elements must have a visible focus indicator8 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<input maxlength="320" tabindex="2" type="text" name="email" id="email" value="" placeholder="Enter Email">
<button tabindex="3" aa-link="" class="button submit" id="submit_btn">
<a href="https://www.pplus.legal/privacy">
<a href="https://www.skyshowtime.com/where-can-i-stream">
<a rel="noopener" href="https://www.pplus.legal/tou" target="_blank">
Showing first 5 of 8 audited elements.
Keyboard focus must be able to leave every component it can enter0 elements
Keyboard users move through a page with Tab, Shift+Tab, arrow keys and Escape. When focus enters a component and none of those keys lets it leave, the rest of the page becomes unreachable and the only way out is to reload or abandon it.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<main id="main-container">
<footer>
Links must have discernible text6 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="https://www.pplus.legal/privacy">Privacy Policy</a>
<a href="https://www.skyshowtime.com/where-can-i-stream">www.skyshowtime.com</a>
<a rel="noopener" href="https://www.pplus.legal/tou" target="_blank">Terms of Use</a>
<a rel="noopener" href="https://www.pplus.legal/privacy" target="_blank">Privacy Policy</a>
<a rel="noopener" href="http://legalterms.cbsinteractive.com/cookies" target="_blank">Cookies</a>
Showing first 5 of 6 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main id="main-container">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en-us">
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">
How does your site stack up against Paramount+?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Streaming & Entertainment