This is a brief outline of what Vidyard customers need to do or avoid to meet the Web Content Accessibility Guidelines (WCAG) 2.0 level A and AA accessibility standards.
Here we’ll teach you to how meet these standards for the Vidyard player. Each success criteria also includes a link to W3C’s Understanding WCAG 2.0 document which will provide you with a more detailed description, examples, strategies, and other important resources to help you ensure your web content is accessible.
By default, Vidyard player events can meet WCAG 2.0 level A criteria, but because they are highly customizable, you must follow some accessibility standards to ensure you are providing the best possible experience for disabled users. If you have written custom code for your player event, please refer to the WCAG 2.0 criteria to ensure your custom event content is accessible.
Note: Events added through event builder do not all meet WCAG accessibility standards.
Outside of the event content, in order to meet level A standards, there are a few important things to do:
- Always give the user the ability to pause the video
- Allow the user to skip fullscreen events if not essential
- Allow user to close popout events if not essential
- Turn off the “show once” setting unless the event gates content
- Always include links to event content in video transcriptions
Because Vidyard’s legacy player uses Flash, it is inaccessible for screen reader and keyboard-only users and is also worth calling out specifically. Views from limited-support browsers use the legacy player, so the player will still not be accessible in these browsers. Legacy mode can also be disabled, but the player will only appear in HTML5-supported browsers.
Level A Success Criteria
Level A contains the basic criteria for making content accessible. This is what most users need to be able to use the site, and will meet most standards required by various organizations. It has limited restrictions on design, so there is no or minimal impact on the website.
1.1.1 Non-text content
Watermarks currently have generic alt text; in addition, if the watermark is a link, it will not have alt text explaining where the link goes. This feature is not accessible to all users and should not be used to provide the user with important information not provided elsewhere.
Video and Audio
See criteria 1.2.1 Audio-only and Video-only (Pre-recorded) and 1.2.3 - Audio Description or Media Alternative (Prerecorded).
1.2.1 Audio-only and video-only (pre-recorded)
Audio-only and video-only content requires a transcript. Speaker names will have to be provided, but you can request transcripts through the Request Transcriptions feature. You can upload a descriptive audio track with your video, but if you do not do this a transcript can be written describing the visuals.
Descriptive audio also meets this criteria for video-only content. Vidyard supports videos with multiple audio tracks, so you can upload videos with a described video audio track to aid people who are visually impaired.
1.2.2 Captions (Pre-recorded)
Captions must be added to all videos with sound. If the video has no sound, it is useful to include a caption stating, “[no sound]”. For closed captions, Vidyard currently has two options: they can be added manually or through transcription services available through Vidyard. Technically, captions are not required if the video is a media alternative for text and is clearly labelled that way.
There are many resources available detailing best practices for captions.
1.2.3 Audio description or media alternative (pre-recorded)
This criteria refers to providing an alternative for synchronized media. Synchronized media is audio or video that is played in sync with other content and/or interactive time-based elements. For example, video with synchronized audio, or audio only with interactive, time-based elements would constitute synchronized media; audio-only or video-only would not. See criteria 1.2.1 - Audio-only and Video-only (Pre-recorded) for non-synchronized video and audio.
Alternatives for time-based media
Vidyard does not currently provide a way to generate a time-based media alternative, but it is possible to request a transcription. If speaker names are included and the video contains no important visual information aside from who is speaking, this transcript may be sufficient. If the video does have other important visual information, you can create a time-based media alternative by adding descriptions of the visuals to the text. On completion, it should look similar to a screenplay, or a transcription of a video with descriptive audio.
Interactive time-based elements
In the Vidyard player, interactive time-based elements may, for example, refer to time-based events with buttons or forms. If such an element is included in the player, the transcript must also include links to the event contents at the appropriate times. If an alternative for time-based media is not otherwise required, one must be created.
Descriptive audio also meets the criteria for synchronized media without interactive time-based elements. Vidyard supports multiple audio tracks in one video, which allows you to upload and host videos with a descriptive audio track.
1.4.2 Audio control
If audio autoplays and is more than three seconds long, the Hide controls design setting must be turned off in order to give users control of the volume; otherwise, the sound can interfere with the use of a screen reader.
2.2.1 Timing adjustable
Content with a time limit in the player includes events, ads, the playlist, sharing, and autoplay of the next video. In order to meet this criteria, the Disable pausing and Hide controls features must be turned off to allow the user to adjust the time limit.
2.2.2 Pause, stop, hide (autoplay)
If an autoplay video is presented concurrently with other content (including text, audio, or video) and is more than five seconds long, the player setting Disable pausing and the design setting Hide controls must be turned off in order to meet this criteria.
Animated splash screens
Because the Animated Splash Screen plays automatically and cannot be paused, the animated GIF must be under 5 seconds if the player is not the only information on the page.
2.3.1 Three flashes or below
Ensuring your video does not have any content that flashes more than 3 times per second makes it safe to watch for users with photosensitive seizure disorders such as epilepsy. There are thresholds where flashing is acceptable, but they are fairly technical, and it is simpler to just avoid flashing if possible. See WCAG criteria 2.3.1 for a more detailed description.
Level AA Success Criteria
Level AA contains criteria that help make accessible content more user-friendly, and makes content accessible for even more users. Level AA standards are a less common requirement than level A standards for organizations concerned about accessibility. If you are only concerned with meeting A, this level of criteria still has useful guidelines for improving usability for disabled users, but it has some light restrictions on website design.
1.2.4 Closed captions (live)
Real time closed captioning is currently supported, but not provided, by Vidyard. Live stream videos support CEA-608 and CEA-708 captions, standards for captions used in analog and digital broadcasting respectively. These captions can be added to live streams using a live captioning service, such as iCap, in conjunction with your broadcasting software. Live captions are not supported on Microsoft Edge or Android, so users should be advised not to use these browsers if they need to see live captions.
1.2.5 Audio description (pre-recorded)
Vidyard supports multiple audio streams, which allows you to upload a video with a descriptive audio track.
1.4.3 Contrast (minimum)
The text on the player is small and should retain a contrast ratio of 4.5:1. The play button on the splash screen should have a contrast ratio of at least 3:1. If the colours or size of text, or background colour must be changed, they should still adhere to these guidelines. These guidelines ensure that users with moderately low vision and users with color blindness are able to read text. For a more detailed explanation of AA contrast, see WCAG criteria 1.4.3.
Keep accessibility in mind while planning and recording your video. This is especially important for instructional or informational videos where many accessibility improvements will improve the overall quality of the video. Here are some examples:
- Low background noise for clear sound
- Good lighting and clear visuals
- Explain instructions with visual demonstrations where appropriate
- Explain visual information with audio where appropriate
Poor usability makes it difficult for anyone to use a website, but it can make things especially difficult for a user with a disability. Many of the accessibility guidelines overlap with W3C’s guidelines for good usability because, although they are important for everybody, they are of specific concern for users with a disability. This means that good usability and user experience tend to make the content more accessible, and vice versa.
Displaying the play button on the player splash screen is a good example of something that is a good usability practice that also has accessibility benefits. The play button on the splash screen helps to communicate that the image has another function. This makes it easier to use for everyone and more accessible for users who may otherwise have trouble noticing or understanding that the image can be clicked to play a video.
Outside of a few use-cases, autoplay can be disruptive to any user, but especially to users who rely on a screen reader to navigate the page. Autoplay audio overrides the screen reader audio, interrupting the flow of information that the user is receiving. Without audio feedback it may be difficult for screen reader users to find the player controls to pause the video. Autoplay and other interruptions can also be disruptive to users who have attention deficit disorders. Autoplay accessibility criteria can be met by always giving users control of play/pause and volume. However, it can still be very disruptive and it is best to avoid in most cases. One case where autoplay is typically okay is when the user understands when they click a link that they are going to a page where a video will be playing.
In addition to autoplay, interruptions can include events, ads, up next, and autoplay next video in the playlist. Playlist autoplay should be turned off in the event settings page and up next should be turned off in the player settings page. Remember to always allow users to skip non-essential events and, where possible, consider offering the content in a way that is not time-based, such as embedding it in the page alongside the video.