Skip to content
https://player.vimeo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
12 landmarks
FIX
12 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
4 of 6 <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

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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
39 headings, 2 skip(s)
REVIEW
39 headings, 2 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.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Video platform features
  • H2 Video hosting
  • H2 Online video player
  • H2 Free screen recorder
  • H2 Free video creator
  • H2 Edit video like a pro
  • H2 Online teleprompter
  • H2 Live streaming, simplified
  • H2 Virtual events
  • H2 Webinars that work
  • H2 Interactive video
  • H2 AI script generation
  • H2 Shoppable video
  • H2 Private and secure video
  • H2 Video collaboration
  • H2 Searchable video library
  • H2 Automatic captions
  • H2 Transcribe your videos
  • H2 Video analytics
  • H2 For teams on the go
  • H2 Start your OTT platform now
  • H2 Security and compliance at Vimeo
  • H2 AI translation
  • H2 Vimeo AI
  • H2 Video SEO
  • H2 Video data residency
  • H2 Video showcases
  • H4 Get started for free skipped
  • H4 24/7 customer support
  • H2 Product
  • H3 Product
  • H3 Features
  • H3 Vimeo for
  • H3 Solutions
  • H2 Resources
  • H2 Company
  • H5 Product skipped
  • H5 Resources
  • H5 Company

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

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

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 Sorry ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Video platform features
1.08:1
#000000
on
#0A0E12
needs 3.0:1 (large text)
32px · bottom of viewport
h3 Product
1.08:1
#000000
on
#0A0E12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Features
1.08:1
#000000
on
#0A0E12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Vimeo for
1.08:1
#000000
on
#0A0E12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Solutions
1.08:1
#000000
on
#0A0E12
needs 3.0:1 (large text)
19px · bottom of viewport
title Video Platform Features
1.20:1
#000000
on
#141A20
needs 4.5:1 (normal text)
16px · top of page (header area)
span Hosting and player
1.20:1
#000000
on
#141A20
needs 4.5:1 (normal text)
16px · top of page (header area)
span Hosting and player
1.20:1
#000000
on
#141A20
needs 4.5:1 (normal text)
16px · top of page (header area)
span Hosting and player
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · top of page (header area)
span Hosting and player
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Video player
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Completely customizable
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Video hosting
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Ad-free, HD, fast, and secure
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Creation and editing
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Creation and editing
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Creation and editing
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Creation and editing
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · above the fold
span Record
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · mid-page
span Capture and share quickly
1.08:1
#000000
on
#0A0E12
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Video platform featu…1.08:13.0:1
#000000
#0A0E12
Fail
h3 Product1.08:13.0:1
#000000
#0A0E12
Fail
h3 Features1.08:13.0:1
#000000
#0A0E12
Fail
h3 Vimeo for1.08:13.0:1
#000000
#0A0E12
Fail
h3 Solutions1.08:13.0:1
#000000
#0A0E12
Fail
title Video Platform Featu…1.20:14.5:1
#000000
#141A20
Fail
span Hosting and player1.20:14.5:1
#000000
#141A20
Fail
span Hosting and player1.20:14.5:1
#000000
#141A20
Fail
span Hosting and player1.08:14.5:1
#000000
#0A0E12
Fail
span Hosting and player1.08:14.5:1
#000000
#0A0E12
Fail
span Video player1.08:14.5:1
#000000
#0A0E12
Fail
span Completely customiza…1.08:14.5:1
#000000
#0A0E12
Fail
span Video hosting1.08:14.5:1
#000000
#0A0E12
Fail
span Ad-free, HD, fast, a…1.08:14.5:1
#000000
#0A0E12
Fail
span Creation and editing1.08:14.5:1
#000000
#0A0E12
Fail
span Creation and editing1.08:14.5:1
#000000
#0A0E12
Fail
span Creation and editing1.08:14.5:1
#000000
#0A0E12
Fail
span Creation and editing1.08:14.5:1
#000000
#0A0E12
Fail
span Record1.08:14.5:1
#000000
#0A0E12
Fail
span Capture and share qu…1.08:14.5:1
#000000
#0A0E12
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 24 passed
REVIEW
81

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Features div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container
Use cases div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container
Enterprise div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container
Learn div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container
Pricing div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container
What's new div.relative > nav.flex > div.flex > li.nav-parent-dropdown-container

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body.__variable_8cc651 > q-focus-sentinel > div
After AI assistant body.__variable_8cc651 > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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.

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
Get started for free div.container-inner > div.w-full > div.flex > h4.text-display-mobile-6

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Sales Login div.builder-f96617c97c2e44bda514b8a282c1a380 > header#global-nav-2025-top-mobile > div.flex > ul.flex

These are opportunities to improve the experience of reading tabular or list data using 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
Pricing div.w-full > div.flex > div.flex > a.button-v3-minimal
Contact Sales div.w-full > div.flex > div.flex > a.button-v3-minimal
Watch Demos div.w-full > div.flex > div.flex > a.button-v3-minimal

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
●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
●Background and foreground colors have a sufficient contrast ratio
●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 have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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
○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.
○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
○`<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.
○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+
Alt Text Quality
All 27 images OK
PASS
All 27 images OK
Info::
1 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
27 images 26 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback