Guides March 24, 2026

Video Widget Accessibility Guide

Learn how to ensure your video widget accessibility meets standards to provide an inclusive experience for all website visitors.

Video Widget Accessibility Guide

Key takeaways

  • Review keyboard operation, screen reader access, media alternatives, contrast, and motion/audio controls against the applicable WCAG criteria.
  • Accessible video helps people use your content. It does not guarantee protection from lawsuits or a particular business result.
  • Before you drop any new video widgets on your site, run an accessibility audit on the ones you’ve already got.

Video accessibility depends on the content, player controls, and surrounding page. Use WCAG to assess keyboard access, captions, media alternatives, contrast, and motion controls. WHO estimates that 16% of the world’s population experiences significant disability. That is a global population estimate, not your site’s customer share. CompleteGreet plans start at $29/month billed yearly. Its feature list does not establish conformance on your installation.

Some fixes are content or configuration changes. Others need development work and specialist testing.

Start by testing the widget with a keyboard and a screen reader. Check that visitors can operate playback and other available functions, understand the labels, and leave the widget without a keyboard trap. These checks are part of an assessment, not a complete conformance test.

What is the short answer?

An accessible implementation needs usable controls, appropriate media alternatives, and compliance with the applicable WCAG criteria on the actual page. Keyboard and screen reader checks are essential parts of that review.

A video bubble with audio that plays automatically for more than three seconds needs pause/stop or volume control independent of system volume under SC 1.4.2. Silent movement is assessed separately: SC 2.2.2 requires pause, stop, or hide for automatic movement lasting over five seconds alongside other content, unless essential.

Automated tools cannot establish that every interaction is accessible.

Pair an automated scan with manual keyboard and screen reader checks. Include people who use assistive technology where possible. Record which interactions were tested and what still needs review.

Why does this matter?

A widget can become a barrier if visitors cannot hear its information, operate its controls, or continue using the page. In the US, Department of Justice guidance describes web-accessibility responsibilities under the ADA for covered entities. Applicable duties depend on the organization and legal context. A widget feature list or an automated scan does not guarantee legal compliance.

Concept illustration for Why does this matter

Consider people who use captions, keyboard input, screen readers, magnification, or reduced-motion settings. Their needs differ, so one setting or one automated score cannot stand in for a review of the experience.

Missing captions can prevent deaf and hard of hearing visitors from understanding audio. Missing audio description can hide important visual information from blind visitors. Keyboard traps and unclear controls can prevent people from operating the player or returning to the page.

Start with the task a visitor needs to complete: watching an explanation, contacting the business, or closing the player to keep reading. Test those tasks and prioritize barriers that prevent access to the page or its information.

Give visitors a way to report accessibility problems, and include that feedback in your review. Keep a record of the affected control, device, browser, assistive technology, and steps needed to reproduce the problem.

Include accessibility work when planning content, design, and development. Set aside time to verify fixes and check for regressions after changes.

What should you do next?

Before you add any new video widgets to your site, run an accessibility audit on the ones you’ve already got. Record the barriers you find before adding another player.

Test with a screen reader. NVDA is free for Windows, and VoiceOver comes built into every Mac.

Test keyboard operation using the controls’ documented commands, including Tab, Shift+Tab, Enter, Space, arrow keys, and Escape where applicable. SC 2.1.1 requires functionality through a keyboard interface, except path-dependent input. It does not require each control to be a separate Tab stop, and this check alone does not establish Level AA conformance.

Put captions and transcripts ahead of visual polish. Auto generated captions from YouTube or Vimeo are a starting point, but they’re definitely not the finish line.

Check dialogue, speaker identification, meaningful non-speech sounds, technical terms, and timing. Correct the captions using the format or editor your player supports, then verify them in playback.

Don’t forget color contrast ratios. Visual cues that identify controls and their states generally need 3:1 contrast against adjacent colors under WCAG 1.4.11, with exceptions for inactive or unmodified user-agent controls. Measure the actual colors rather than judging by appearance alone.

Mobile testing surfaces different barriers than desktop audits do. WCAG 2.2 AA generally requires targets of at least 24 by 24 CSS pixels, with spacing and other exceptions. The enhanced AAA target is 44 by 44 CSS pixels, with exceptions.

People who use assistive technology can help identify barriers that automated tools miss.

Write down your widget configuration choices. When the person who set up the player leaves the company, the next admin needs to understand why those specific color contrasts, button sizes, and autoplay settings were chosen.

One more thing, accessibility isn’t a set it and forget it deal. You’ve got to check it after every platform update or theme change. Small accessibility issues have a sneaky habit of creeping back in after routine CMS updates that reset your custom code.

Video widgets add playback, audio, and motion controls to a page. Assess those controls alongside the surrounding content. Autoplaying media, keyboard traps, and missing text alternatives can shut out visitors who rely on assistive technologies or just prefer reduced motion.

The following sections explain requirements to include in your review.

Keyboard Navigation and Focus Control

Make the player’s functions operable through a keyboard interface. Use a logical focus order and documented keyboard commands for buttons, sliders, and other controls. A separate Tab stop is not required for every visible control. Visitors must be able to leave the widget without a keyboard trap.

Autoplay and Audio Policies

Sound autoplay is not automatically a WCAG failure. Under SC 1.4.2, audio that starts automatically and lasts over three seconds needs pause/stop or volume control independent of system volume. Starting sound only after a deliberate user action avoids competing with a screen reader when the page opens.

Browser autoplay policies vary. Provide a clear way to start playback when autoplay is blocked, and test the actual player. Muting audio does not remove the separate requirements for controlling automatic visual movement.

Text Alternatives and Visual Contrast

SC 1.2.2 requires synchronized captions for prerecorded audio in synchronized media, including dialogue and meaningful sounds, except a clearly labeled media alternative that adds nothing to existing text. At Level AA, SC 1.2.5 requires audio description of important visual information absent from the soundtrack. No extra description is needed when the audio already conveys it. A transcript alone does not replace that AA requirement. Also check control contrast and visible focus.

Use W3C accessibility guidance to identify the applicable criteria and test them on the complete page. A checklist of selected features does not establish Level AA conformance or satisfy every procurement requirement.

Motion and Cognitive Accessibility

Moving widgets can distract visitors. Offer a way to reduce or stop unnecessary motion.

Respect reduced-motion preferences where supported, and verify the result on your player. Under SC 2.2.2, automatic moving, blinking, or scrolling content lasting over five seconds alongside other content needs pause, stop, or hide unless essential. A looping preview can exceed that duration even when each loop is short.

Resolve barriers through the content, control behavior, and page integration. If the player cannot provide an accessible interaction, investigate another implementation or an accessible route to the same information and actions.

Check CompleteGreet on your actual page, including captions, keyboard operation, screen reader output, focus behavior, motion, and audio controls. Its documented caption tools are capabilities, not a conformance report. Additional configuration, content changes, or engineering may be needed. Measure business outcomes separately rather than promising a conversion increase.

Common questions

How much does CompleteGreet cost per month for a small business website with around 10,000 visitors?

CompleteGreet runs $74 per month on the Growth plan, which covers up to 10,000 unique visitors. That flat rate includes capacity for five videos, tracking, onboarding support, and all 25 features. If you go with annual billing, it drops to $59 per month. The visitor capacity still applies during traffic spikes.

Can I install CompleteGreet on Shopify without a developer?

CompleteGreet is available through the Shopify app store. Upload the video, configure placement and actions, and test it on your theme. WordPress/WooCommerce uses a plugin, while other supported platforms use an embed. Workflows and setup time depend on the platform and installation.

Does CompleteGreet charge by video views, interactions, or something else?

CompleteGreet counts unique visitors to your website, not video plays or widget interactions. Visits are counted once per unique IP within 24 hours. This really matters for high bounce traffic where people land and leave fast. Your bill stays predictable even if your greeting racks up thousands of impressions.

How fast can I get a CompleteGreet widget live on my site?

Prepare the greeting and captions, configure the player, and use the installation route for your platform. Test keyboard operation, screen reader behavior, media alternatives, and mobile layout before publishing. The time needed depends on what those checks reveal.

Is CompleteGreet good for collecting customer surveys and long feedback forms?

CompleteGreet supports surveys, standard and step-by-step forms, ratings/NPS, live chat, and choice-based Multivid journeys. Check the available fields and workflows against the feedback you need. Arbitrary conditional rules or scored assessments are not established by those feature descriptions, so verify any such requirement separately.

What happens if my website traffic exceeds my CompleteGreet plan limit?

On capped paid plans, exceeding the visitor limit hides the bubble until the next billing period. Visits are counted once per unique IP within 24 hours. Choose capacity for expected traffic. The 30-day trial has unlimited visitors and expires separately after 30 days. The Scale plan at $199 per month, or $159 per month billed annually, covers 100,000 visitors.

Azad Habib

Azad Habib

CEO & Founder of CompleteGreet

Azad Habib is the founder of CompleteGreet. With a background in ecommerce and user experience, he works at the intersection of trust, clarity, and conversion to help businesses make their websites feel more human from the first click.