Skip to content
https://livestream.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
9 landmarks
FIX
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
✓ favicon.ico Present
✓ 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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Livestream - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 22 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Live stream right now div.flex > div.cardheader > div.cardtext > h4.text-display-mobile-7

These are opportunities to improve keyboard navigation in your application.

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.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-initial-child-container > div.rfm-child > div.h-10 > img div.rfm-initial-child-container > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img
div.rfm-marquee > div.rfm-child > div.h-10 > img div.rfm-marquee > div.rfm-child > div.h-10 > img

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
div.container-inner > div.col-start-2 > nav.inline-flex > a.inline-flex div.container-inner > div.col-start-2 > nav.inline-flex > a.inline-flex

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●`[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
●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
●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.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<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 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
○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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
Heading Hierarchy
20 headings, 1 skip(s)
PASS
20 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Live video streaming
  • H2 Live streaming solutions you can count on
  • H2 Trusted by leading brands
  • H3 Put your live video to work
  • H3 Grow your audience, everywhere
  • H3 Connect face-to-face
  • H2 Share everywhere
  • H2 Start streaming live with Vimeo
  • H4 Live stream right now skipped
  • H4 Get enterprise‑grade live streaming
  • H4 Monetize your live streams
  • H2 Everything you need to livestream
  • H3 Flawless adaptive streaming
  • H3 Video management
  • H3 Live production graphics and tools
  • H3 Priority support
  • H2 About
  • H2 Solutions
  • H2 Discover
  • H2 Services

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

A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
1 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
10 images 9 good alt text 1 decorative
All images have appropriate alt text.
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 Live video streaming20.41:13.0:1
#000000
#FAFCFD
Pass
h2 Live streaming solut…20.41:13.0:1
#000000
#FAFCFD
Pass
h2 Trusted by leading b…20.41:13.0:1
#000000
#FAFCFD
Pass
h2 Share everywhere20.41:13.0:1
#000000
#FAFCFD
Pass
h2 Start streaming live…20.41:13.0:1
#000000
#FAFCFD
Pass
h2 Everything you need …20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Put your live video …20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Grow your audience, …20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Connect face-to-face20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Flawless adaptive st…20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Video management20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Live production grap…20.41:13.0:1
#000000
#FAFCFD
Pass
h3 Priority support20.41:13.0:1
#000000
#FAFCFD
Pass
title Stream Live Video On…20.36:14.5:1
#000000
#F9FCFC
Pass
span open main menu20.36:14.5:1
#000000
#F9FCFC
Pass
span Product20.41:14.5:1
#000000
#FAFCFD
Pass
span Product20.41:14.5:1
#000000
#FAFCFD
Pass
span Hosting and Player20.41:14.5:1
#000000
#FAFCFD
Pass
span Video Player20.41:14.5:1
#000000
#FAFCFD
Pass
span Video Hosting20.41:14.5:1
#000000
#FAFCFD
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