Skip to content
https://paramount.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Heading Hierarchy
Action
18 headings, 1 skip(s)
FIX
18 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
12 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Paramount Home page
  • H2 More Of What you love
  • H2 More Of
  • H1 What you love duplicate H1
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H2 SHAPE THE
  • H1 FUTURE duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Paramount ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

6 pass 14 fail WCAG AA 6 pass AA only
title Home | Paramount
1.11:1
#000000
on
#000A3C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.11:1
#000000
on
#000A3C
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.11:1
#000000
on
#020B3A
needs 4.5:1 (normal text)
16px · top of page (header area)
button About
1.13:1
#000000
on
#0E0F30
needs 4.5:1 (normal text)
16px · top of page (header area)
a Brands
1.18:1
#000000
on
#21131F
needs 4.5:1 (normal text)
16px · above the fold
a Businesses
1.31:1
#000000
on
#341A16
needs 4.5:1 (normal text)
16px · above the fold
a Leadership
1.54:1
#000000
on
#462519
needs 4.5:1 (normal text)
16px · above the fold
a Board of Directors
1.85:1
#000000
on
#55311F
needs 4.5:1 (normal text)
16px · above the fold
a History
1.83:1
#000000
on
#55301E
needs 4.5:1 (normal text)
16px · above the fold
a Compliance Resources
1.57:1
#000000
on
#472718
needs 4.5:1 (normal text)
16px · above the fold
a News
1.54:1
#000000
on
#402819
needs 4.5:1 (normal text)
16px · above the fold
button News
1.68:1
#000000
on
#423020
needs 4.5:1 (normal text)
16px · above the fold
a Press Releases
1.82:1
#000000
on
#493522
needs 4.5:1 (normal text)
16px · above the fold
a Careers
2.21:1
#000000
on
#594126
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Paramount Home page4.27:13.0:1
#000000
#0064FF
Pass
h1 What you love4.27:13.0:1
#000000
#0064FF
Pass
h1 FUTURE4.27:13.0:1
#000000
#0064FF
Pass
h2 More Of What you lov…4.27:13.0:1
#000000
#0064FF
Pass
h2 More Of4.27:13.0:1
#000000
#0064FF
Pass
h2 SHAPE THE4.27:13.0:1
#000000
#0064FF
Pass
title Home | Paramount1.11:14.5:1
#000000
#000A3C
Fail
a Skip to main content1.11:14.5:1
#000000
#000A3C
Fail
a About1.11:14.5:1
#000000
#020B3A
Fail
button About1.13:14.5:1
#000000
#0E0F30
Fail
a Brands1.18:14.5:1
#000000
#21131F
Fail
a Businesses1.31:14.5:1
#000000
#341A16
Fail
a Leadership1.54:14.5:1
#000000
#462519
Fail
a Board of Directors1.85:14.5:1
#000000
#55311F
Fail
a History1.83:14.5:1
#000000
#55301E
Fail
a Compliance Resources1.57:14.5:1
#000000
#472718
Fail
a News1.54:14.5:1
#000000
#402819
Fail
button News1.68:14.5:1
#000000
#423020
Fail
a Press Releases1.82:14.5:1
#000000
#493522
Fail
a Careers2.21:14.5:1
#000000
#594126
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
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer
A
Alt Text Quality
2 of 39 images have issues
PASS
2 of 39 images have issues
Warning::
2 image(s) with generic alt text
Info::
37 image(s) with good alt text
39 images 37 good alt text 2 generic
IssueCount
generic2 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 24 passed
PASS
95

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.coh-container > div.coh-container > div.coh-container > button.coh-button div.coh-container > div.coh-container > div.coh-container > button.coh-button
div.coh-container > div.coh-container > div.coh-container > button.coh-button div.coh-container > div.coh-container > div.coh-container > button.coh-button
div.coh-container > div.coh-container > div.coh-container > button.coh-button div.coh-container > div.coh-container > div.coh-container > button.coh-button
div.coh-container > div.coh-container > div.coh-container > button.coh-button div.coh-container > div.coh-container > div.coh-container > button.coh-button

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Details div.coh-container > ul.coh-list-container > li.coh-list-item > a.coh-link
○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
●Image elements have `[alt]` attributes
●`[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
●`[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 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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○Form elements have associated labels
○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.
○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