For most of its history, web video has looked like TV — with one video playing at a time, and simple controls — like those on a DVD player. The HTML video element and video services have implemented controls in the same way.
But interactive media have a more complex set of concerns. There may be multiple media elements playing at the same time, and they may not play in sync. And media will not necessarily progress linearly; it might loop, pause or skip around in response to code or user interactions. Video may be partially obscured by other elements on the page, making the use of existing control schemes difficult. As a result, new controls may need to be created to meet these criteria — and to match the style of the rest of the content.
It can be tempting to keep controls to a minimum, assuming that a viewer will fully submit to the author, like they would with a film in a theater or a broadcast TV show, but it’s worth considering the experience from a user’s point of view. A web or app experience is not like a theater, where the exhibitor has complete control and any external factors have been eliminated. Your viewers’ attention will likely be divided among multiple applications and browser tabs. (This is not always a bad thing. They may be taking notes, searching for related information or sharing your work with someone else.) Even the most dedicated user may be interrupted by factors beyond their control. They might be at work, on a mobile device or around kids and pets. To ignore these considerations not only disrespects your audience, it also makes it difficult for them to recover and get back to appreciating your work.
So let’s explore a few ways we can give some control back to an audience without sacrificing a full interactive experience.
Reactions to Visibility
Manual volume control is a user interface component that is easy to ignore. Sometimes it’s better to play your media at full volume and allow the user to depend on system volume, but a user is likely to have multiple applications going at once. You may have multiple kinds of audio in one experience. Consider the convention in video games of providing separate volume settings for background music vs. sound effects and dialogue.
The ability to seek within media is also useful but perhaps more complex. It might not even make sense if your site is truly non-linear. You may not want to allow skipping ahead past a reveal or other required interaction, but a viewer might want to rewind to review something they’ve already watched for clarification or deeper understanding. Consider that they may also want to skip ahead to resume from a previous play experience. Remember, seeking applies to both continuous media timelines and to skipping between discrete sections. You can store data with localStorage to have your site remember how far a user has progressed into your story and adjust seeking controls accordingly.
Finally, at the very least, please implement a pause button. Ideally, enable the spacebar for toggling play and pause, if you don’t otherwise need it for typing text.
Designing controls can be a challenge for a rich media experience, so think about the different levels of interaction. Media components can be active, passive or ambient, and each of these warrants different modes of control. There are many dimensions to consider, and they will vary for every scenario, but by working towards common conventions that are generous to an audience, we can collectively teach them to be more open to our work.