Joshua Goodwin

<p>Some WordPress audio plugins inject JavaScript into every page of your website, even pages that don’t have any audio on them. PlayPress doesn’t need any JavaScript.</p>
<p>Other plugins rely on Adobe’s displeasing Flash technology. PlayPress can fall back or default to HTML5 audio – without any JavaScript voodoo wizardry.</p>
<p>Other plugins can play videos and make you tea. PlayPress has a laser focus on just one thing: it lets you put an audio player in blog posts and pages.</p>
<p>You use a standard WordPress shortcode like this:</p>
<pre><code>[audio mp3="http://example.com/bells.mp3" ogg="http://example.com/bells.ogg"]
</code></pre>
<p>Users of most modern browsers will see a native HTML5 audio player. In older browsers, an adequate Flash-based one will be shown.</p>
<p>You don’t even need an Ogg Vorbis file:</p>
<pre><code>[audio mp3="http://example.com/bells.mp3"]
</code></pre>
<p>In this case, PlayPress will first attempt to show the Flash player. If Flash isn’t installed, readers will see the HTML5 audio player – but it won’t work in Firefox or Opera. (Most Firefox and Opera users should have Flash installed.)</p>
<p>In either case, if neither Flash nor HTML5 are supported by the browser, users will see a link to download the audio file. Graceful degradation.</p>
<p>Optionally, specify a title and/or artist for display in the Flash player (this will override the ID3 metadata embedded in your MP3 file, which is otherwise used if present):</p>
<pre><code>[audio mp3="http://example.com/bells.mp3" title="Imagine" artist="John Lennon"]
</code></pre>
<p><a href="https://joshuagoodw.in/playpress" rel="nofollow ugc">The author’s website</a> has PlayPress running live right there on it.</p>


PlayPress

PlayPress is a JavaScript-free, low-Flash audio player, fortified with HTML5.

Joe Dolson

terrillthompson

<p>This plug-in uses Able Player, an open-source fully-accessible cross-browser HTML5 media player, to embed audio or video within your WordPress page.</p>
<h3>Instructions for Use</h3>
<p>There are currently three ways to add an Able Player instance to a WordPress site:</p>
<ol>
<li>Go to Settings > Able Player > Settings and enable the options to use Able Player for all video, audio, and playlists. Able Player will automatically replace MediaElement.jss or the default WordPress video/audio blocks with Able Player.</li>
<li>Go to Settings > Able Player > Shortcodes to generate an <code>[ableplayer]</code> shortcode.</li>
<li>Enter or paste any valid HTML5 Able Player code into your web page. Full documentation is available on the <a href="http://ableplayer.github.io/ableplayer" rel="nofollow ugc">Able Player</a> project page on GitHub.</li>
</ol>
<p>Using the media rewriting in option #1, Able Player will replace any <code>audio</code> or <code>video</code> block. Any tracks added to that block will be automatically handled, giving you support for all the standard Able Player features: captions, navigable transcripts, subtitles, chapters, and audio description.</p>
<p>Using option #2, you can create Able Player shortcodes that support most of the basic Able Player features, with support for Vimeo, YouTube, or local video.</p>
<p>Option #3 supports the full scope of Able Player features.</p>
<h3>The [ableplayer] shortcode</h3>
<p>The <code>[ableplayer]</code> shortcode supports the following attributes.</p>
<h4>Required attributes (one of these)</h4>
<ul>
<li><code>youtube-id</code> – 11-character YouTube ID or YouTube URL.</li>
<li><code>vimeo-id</code> – Vimeo ID or URL.</li>
<li>`media-id’ – An attachment ID for a media file in your WordPress media library or the URL to a hosted video.</li>
</ul>
<h4>Additional Player Content</h4>
<ul>
<li><code>captions</code> – Attachment ID or URL to <code>.vtt</code> captions file. Optional pipe separator for language code and label.</li>
<li><code>subtitles</code> – Attachment ID or URL to <code>.vtt</code> subtitles file. Optional pipe separator for language code and label.</li>
<li><code>chapters</code> – Attachment ID or URL to <code>.vtt</code> chapters file. Optional pipe separator for language code and label.</li>
<li><code>descriptions</code> – Attachment ID or URL to <code>.vtt</code> audio descriptions file. Optional pipe separator for language code and label.</li>
<li><code>youtube-desc-id</code> – YouTube URL or ID of a described version of the video</li>
<li><code>youtube-sign-src</code> – YouTube URL or ID of a sign language interpreted accompanying video</li>
<li><code>vimeo-desc-id</code> – Vimeo URL or ID of a described version of the video</li>
</ul>
<p>All captions, subtitles, chapters, and descriptions tracks must be in <code>.vtt</code> format. The shortcode only supports a single set of values for each type of data; to add multiple tracks of the same type you can use the Video block or add custom HTML.</p>
<p>Either an attachment ID or a URL for your track <code>.vtt</code> is required; you can optionally add a language code and a custom label:</p>
<pre><code>captions="/path/to/file.vtt|es|Español"
</code></pre>
<p>By default, the language will be your WordPress installation language, with the labels “Captions”, “Subtitles”, “Chapters” or “Audio Description”.</p>
<h4>Player Options</h4>
<ul>
<li><code>youtube-nocookie</code> – “true” or “false” (use “true” to embed YouTube untracked, for added privacy)</li>
<li><code>autoplay</code> – “true” or “false” (default is “false”)</li>
<li><code>loop</code> – “true” or “false” (default is “false”)</li>
<li><code>playsinline</code> – “true” or “false” (default is “true”). By setting to “false”, some devices (e.g., iPhones) will play the video in their own media player rather than in Able Player.</li>
<li><code>hidecontrols</code> – “true” or “false” (default is “false”). Set to “true” to enable the player controls to fade away during playback. They will appear again if the user hovers over the player or pressing a key, and they are always accessible to screen reader users.</li>
<li><code>poster</code> – the URL of a poster image, displayed before the user presses Play</li>
<li><code>width</code> – a value in pixels (by default, the player will be sized to fit its container)</li>
<li><code>height</code> – a value in pixels (by default, the height of the player will be in proportion to the width)</li>
<li><code>heading</code> – The HTML heading level (1-6) of the visually hidden “Media Player” heading that precedes the player (for the benefit of screen reader users). If omitted, a heading level will be intelligently assigned based on context.</li>
<li><code>speed</code> – “animals” or “arrows” (default is “animals”)</li>
<li><code>start</code> – start time at which to start playing the media, in seconds. Some browsers do not support this.</li>
<li><code>volume</code> – “0” to “10” (default is “7” to avoid overpowering screen reader audio). Some browsers do not support this.</li>
<li><code>seekinterval</code> – number of seconds to forward/rewind with the Forward and Rewind buttons. If omitted, the interval will be intelligently assigned based on length of the video.</li>
<li><code>nowplaying</code> – “true” or “false” to include a “Selected Track” section within the media player (default is “false”).</li>
<li><code>transcript-div</code> – ID attribute of a target element that will contain the video transcript</li>
<li><code>id</code> – a unique id for the player (if omitted, one will be automatically assigned)</li>
</ul>
<h3>Examples</h3>
<h4>Example 1</h4>
<p>This example uses HTML to add an audio player to the page, with one source (an MP3 file).<br />
    <code>html<br />
  <audio id="audio1" preload="auto" data-able-player src="path_to_audio.mp3"></audio></code></p>
<h4>Example 2</h4>
<p>This example uses HTML to add a video player to the page, with one source (an MP4 file) and four tracks (for captions, descriptions, and chapters in English; and subtitles in Spanish).<br />
    <code>html<br />
  <video id="able-player-1" data-able-player preload="auto" poster="path_to_image.jpg"><br />
    <source type="video/mp4" src="path_to_video.mp4"><br />
    <track kind="captions" src="path_to_captions.vtt" srclang="en" label="English"><br />
    <track kind="subtitles" src="path_to_subtitles.vtt" srclang="es" label="Español"><br />
    <track kind="descriptions" src="path_to_descriptions.vtt" srclang="en"><br />
    <track kind="chapters" src="path_to_chapters.vtt" srclang="en"><br />
  </video></code></p>
<h4>Example 3</h4>
<p>This example uses the shortcode to add a video player to the page, with one source (an MP4 file) and four tracks (for captions, descriptions, and chapters in English; and subtitles in Spanish). All sources are fetched as WordPress media attachments.<br />
    <code>html<br />
  [ableplayer poster="21" media-id="24" captions="25|en|English" subtitles="26|es|Español" descriptions="27" chapters="28"]</code></p>
<h4>Example 4</h4>
<p>This example uses a shortcode to add a YouTube player to the page, with two versions of the video, one with audio description and the other without (the user can toggle between the two versions using the D button).<br />
    <code>[ableplayer youtube-id="XXXXXXXXXXX" youtube-desc-id="YYYYYYYYYYY"]</code></p>
<h4>Example 5</h4>
<p>This example uses a shortcode to add a Vimeo player to the page, with two versions of the video, one with audio description and the other without (the user can toggle between the two versions using the D button).<br />
    <code>[ableplayer vimeo-id="XXXXXXXXX" vimeo-desc-id="YYYYYYYYY"]</code></p>
<p>The Able Player plugin was originally created by <a href="https://terrillthompson.com" rel="nofollow ugc">Terrill Thompson</a>.</p>


PlayPress vs Able Player, accessible HTML5 media player