Skip to content
https://streamable.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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::
1 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 1 <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 Streamable ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 77/100 — 6 failing, 23 passed
REVIEW
77

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#root > nav.navigation-bar-v2 > div.navigation-bar-v2__content > button.sb-button div#root > nav.navigation-bar-v2 > div.navigation-bar-v2__content > button.sb-button

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
nav.navigation-bar-v2 > div.navigation-bar-v2__content > div.navigation-bar-v2__logo-container > a.navigation-bar-v2__logo-link nav.navigation-bar-v2 > div.navigation-bar-v2__content > div.navigation-bar-v2__logo-container > a.navigation-bar-v2__logo-link

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.

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
Upload video for free div.ticker-with-dropzone-hero__ticker-container > div > div.hero-dropzone > button.sb-button
*No credit card or account required div.ticker-with-dropzone-hero__ticker-container > div > div.hero-dropzone > p.hero-dropzone__no-credit-card
Terms of Service div > div.hero-dropzone > p.ticker-with-dropzone-hero__terms > a
Privacy Policy div > div.hero-dropzone > p.ticker-with-dropzone-hero__terms > a
Sign up for free main.main > section.get-started-for-free-banner > div.get-started-for-free-banner__content > a.get-started-for-free-banner__cta
Accept all cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

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
Select videos to upload div > div.hero-dropzone > div.hero-dropzone__info > h3.hero-dropzone__info__title

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Blog div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Privacy Policy div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Cookie Policy div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Cookie Preferences div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Terms div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Community guidelines div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Law Enforcement guidelines div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Transparency Report div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Open Source Libraries div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Pricing div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Log in div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Sign up div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Upload video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Clip from URL div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Simple video manager div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Backup video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Crop video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Mute video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Merge video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Trim video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Rotate video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Compress video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Share video link div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Send multiple videos div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Embed video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Download video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Video privacy div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Password protected video div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Ad free video player div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Help center div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Contact div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Getting the best audio in your recordings div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
How to wear a lavalier microphone div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item
Improve the lighting in your videos div.sb-flex > section.footer-v3-section > div.sb-flex > li.footer-v3-section__navigation-list__item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

A
Heading Hierarchy
13 headings, 1 skip(s)
PASS
13 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Video hosting made easy
  • H3 Select videos to upload skipped
  • H2 Upload and share your videos instantly
  • H2 Video editing that gets out of your way
  • H2 Streamable is loved by over 50 million users and customers from 122 countries
  • H3 I love it when a web tool provides a simple service seamlessly. @streamable is a super clean #video publishing tool. Host a vid with no surrounding noise but the logo. Embed tool as well. Great place
  • H3 Shoutout to @streamable for being so good at converting videos, else I would not have any awesome plays of the game to share with my server members!
  • H2 Get started for free
  • H3 Company
  • H3 Product
  • H3 Tools
  • H3 Support
  • H3 Learning

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 9 images OK
PASS
All 9 images OK
Info::
9 image(s) with good alt text
9 images 9 good alt text
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 Video hosting made e…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Upload and share you…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Video editing that g…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Streamable is loved …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Get started for20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Select videos to upl…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 I love it when a web…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Shoutout to @streama…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Company20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Product20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Tools20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Support20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Learning20.82:13.0:1
#000000
#FEFEFE
Pass
title Upload Video Online …21.00:14.5:1
#000000
#FFFFFF
Pass
button Tools21.00:14.5:1
#000000
#FFFFFF
Pass
p Upload21.00:14.5:1
#000000
#FFFFFF
Pass
a Upload video21.00:14.5:1
#000000
#FFFFFF
Pass
a Clip from URL21.00:14.5:1
#000000
#FFFFFF
Pass
a Backup video21.00:14.5:1
#000000
#FFFFFF
Pass
p Edit21.00:14.5:1
#000000
#FFFFFF
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