Constructing Snippets
The easiest approach to creating a snippet is to use our Access Player Builder. This will setup a snippet that has the media source and your settings all configured directly in the snippet. The Access Player will show you sources from upload. If you need a source 3Play hasn’t seen yet, you can easily copy a link to the media or manually edit settings to customize the source you are loading from.
The Access Player is very flexible on how it can look up media to make integrating with your workflow as easy as possible. If you have setup videos with one of our integrations, the player will simply look up by the video IDs (and account and player IDs, if necessary) from your integrations.
If you don’t have an integration set up, you can also manually associate video IDs to a specific 3Play transcript through the Media File ID.
Choosing between a Javascript Snippet or an iframe snippet
Responsiveness |
Yes Styling and positioning on your site may be easier with the JavaScript snippet. |
Yes Custom styling with height constraints may be more difficult compared to the JavaScript snippet. |
Collapsable transcript |
Yes |
No |
Interactive transcript |
Yes |
Yes |
Search |
Yes |
Yes |
Download |
Yes |
Yes |
Audio Description |
Yes |
Yes |
Loading performance |
As fast as possible. Prefer this if the Access Player is the primary content on the page. |
Lower priority. Slower to load; interferes less with other content. |
Compatibility |
May not be supported due to CMS security policies disallowing third-party JavaScript. |
Should work with nearly all CMS systems. |
SEO |
Best effort; transcript should be found and indexable by Google. |
Generally not indexable by google as content is framed. |
Accessibility Experience |
Strong. |
Strong. Screenreaders may need to enter the iframe but this will be a familiar experience with video content. |
Lighthouse Impact |
As minimal as possible! The Access Player was designed to be lightweight and load large amounts of content as fast as possible. |
May provide a slightly higher score due to iframes being currently ignored by Lighthouse scoring. However, this is actually a slower loading experience for the user and scores may be lower if Lighthouse scoring changes in future. |
Multiple players on one page |
No (currently) |
Yes |
0 Comments