Skip to content
https://jwplayer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
5
REVIEW
1
PASS
7
INFO
0
Checks
13
7 PASS 1 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main navigation" MAIN CONTENTINFO footer
A
Heading Hierarchy
18 headings
PASS
18 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Transforming ContentInto Growth
  • H2 Solutions for EveryMedia Business
  • H2 Discover Your Ideal JWX Solution
  • H2 Discover Your Ideal JWX Solution
  • H2 Latest news and articles by JWX
  • H3 How the new video playbook centers flexible solutions for broadcasters and audiences alike
  • H3 JWP Connatix is Shortlisted for the 2025 European Video Awards
  • H3 JWP Connatix talks video monetization for publishers and broadcasters
  • H2 Latest News and Articles by JWX
  • H3 JWX Acquires True Anthem to Give Publishers AI-Powered Social Publishing and Distribution Layer
  • H3 JWX Partners with QuantumPath to Give Media Buyers Holistic Control Across Their Programmatic Ad Buys
  • H3 JWX Launches Vertical Video Product To Help Publishers Increase Engagement and Time-on-Site
  • H2 Build Your Business with a Smarter Content Strategy
  • H1 Let Us Turn Your Content Into Consistent Revenue duplicate H1
  • H2 What we have to say
  • H3 What Are Ad Impressions?
  • H3 What is Video Encoding?
  • H3 PROMOTE YOUR PRODUCTS AND SERVICES

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

A+
Alt Text Quality
All 41 images OK
PASS
All 41 images OK
Info::
41 image(s) with good alt text
41 images 41 good alt text
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
#pwr-js-burger-search__inputtextSearcharia-label
#pwr-header-search__inputtextSearcharia-label
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - JW Player ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Let Us Turn Your Con…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Solutions for Every20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Media Business20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Discover Your Ideal …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Discover Your Ideal …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Latest news and arti…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Latest News and Arti…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Build Your Business …20.12:13.0:1
#000000
#FAFAFA
Pass
h2 What we have to say20.12:13.0:1
#000000
#FAFAFA
Pass
h3 How the new video pl…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 JWP Connatix is Shor…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 JWP Connatix talks v…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 JWX Acquires True An…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 JWX Partners with Qu…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 JWX Launches Vertica…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 What Are Ad Impressi…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 What is Video Encodi…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 PROMOTE YOUR PRODUCT…20.12:13.0:1
#000000
#FAFAFA
Pass
title Video technology & m…20.65:14.5:1
#000000
#FDFDFD
Pass
a Skip to content19.95:14.5:1
#000000
#F9F9F9
Pass

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
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 28 passed
PASS
90

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
Let Us Turn Your Content Into Consistent Revenue div.pwr-sec-cta > div.pwr-sec-cta--content > div.pwr-sec-cta__hor-text-wrapper > h1#let-us-turn-your-content-into-consistent-revenue
Whether your goal is growth, efficiency, or improved monetization, JWX gives yo… div.pwr-sec-cta__hor-text-wrapper > span.pwr-rich-text > p > span

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JWX_footer_logo div.row-fluid > div.pwr-footer-company-info > div.pwr-footer__logo > a

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy div#hs_menu_wrapper_menu_160582056051 > ul > li.hs-menu-item > a
DMCA div#hs_menu_wrapper_menu_160582056051 > ul > li.hs-menu-item > a
Ad Choices div#hs_menu_wrapper_menu_160582056051 > ul > li.hs-menu-item > a
Support div#hs_menu_wrapper_menu_160582056051 > ul > li.hs-menu-item > a
Opt Out div#hs_menu_wrapper_menu_160582056051 > ul > li.hs-menu-item > a

These items highlight common accessibility best practices.

○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
●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
●`[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.
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○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