Skip to content
https://videojs.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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 GitHub ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
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 Not set ✗Dark theme-color #ebe4c1 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 26 passed
REVIEW
87

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0:00 div.media-default-skin > div.media-surface > div.media-time-controls > time.media-time
0:35 div.media-default-skin > div.media-surface > div.media-time-controls > time.media-time

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.

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
v10 BETA div.isolate > main#main-content > header.relative > span.inline-flex
BETA main#main-content > header.relative > span.inline-flex > span.whitespace-pre
REACT div.flex > button#tab-1776806875071-code > span.relative > span.absolute
REACT div.flex > button#tab-1776806875072-code > span.relative > span.absolute
TECH PREVIEW div.relative > div.relative > div > h3.font-display
BETA div.relative > div.relative > div > h3.font-display
GA div.relative > div.relative > div > h3.font-display
CORE FEATURE PARITY div.relative > div.relative > div > h3.font-display
CORPORATE SHEPHERD section.row-span-2 > div.grid > div.flex > h3.mb-2.5
CDN div.relative > div.grid > div.h-auto > h3.relative
EMERITUS SPONSOR div.relative > div.grid > div.h-auto > h3.relative
DEVICE TESTING div.relative > div.grid > div.h-auto > h3.relative
STATIC HOSTING div.relative > div.grid > div.h-auto > h3.relative

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > astro-island > div.media-default-skin > img div.relative > astro-island > div.media-default-skin > img

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.

○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-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
●`[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
●ARIA input fields have accessible names
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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 `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
○Form elements have associated labels
○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.
○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.
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Video.js" 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

A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H1 The Open Source Player for the Web
  • H2 Assemble your player
  • H2 Take full control
  • H2 Get Started
  • H2 v10 is built different
  • H3 Download speeds
  • H2 Roadmap
  • H3 Tech Preview
  • H3 Beta
  • H3 GA
  • H3 Core Feature Parity
  • H2 Sponsors
  • H3 Corporate Shepherd
  • H3 CDN
  • H3 Emeritus Sponsor
  • H3 Device Testing
  • H3 Static Hosting
  • H3 CDN
  • H3 Emeritus Sponsor
  • H3 Device Testing
  • H3 Static Hosting
A
Alt Text Quality
1 of 2 images have issues
PASS
1 of 2 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
2 images 1 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 The Open Source Play…17.17:13.0:1
#000000
#F3E7D2
Pass
h2 Assemble your player17.17:13.0:1
#000000
#F3E7D2
Pass
h2 Take full control17.17:13.0:1
#000000
#F3E7D2
Pass
h2 Get17.17:13.0:1
#000000
#F3E7D2
Pass
h2 v10 is built differe…17.17:13.0:1
#000000
#F3E7D2
Pass
h2 Roadmap17.17:13.0:1
#000000
#F3E7D2
Pass
h2 Sponsors17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Download speeds17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Tech Preview17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Beta17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Core Feature Parity17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Corporate Shepherd17.17:13.0:1
#000000
#F3E7D2
Pass
h3 CDN17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Emeritus Sponsor17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Device Testing17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Static Hosting17.17:13.0:1
#000000
#F3E7D2
Pass
h3 CDN17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Emeritus Sponsor17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Device Testing17.17:13.0:1
#000000
#F3E7D2
Pass
h3 Static Hosting17.17:13.0:1
#000000
#F3E7D2
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback