Able Player, accessible HTML5 media player
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. Instructions for Use There are currently three ways to add an Able Player instance to a WordPress site: 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.js or the default WordPress video/audio blocks with Able Player. Go to Settings > Able Player > Shortcodes to generate an [ableplayer] shortcode. Enter or paste any valid HTML5 Able Player code into your web page. Full documentation is available on the Able Player project page on GitHub. Using the media rewriting in option #1, Able Player will replace any audio or video 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. 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. Option #3 supports the full scope of Able Player features. The [ableplayer] shortcode The [ableplayer] shortcode supports the following attributes. Required attributes (one of these) youtube-id – 11-character YouTube ID or YouTube URL. vimeo-id – Vimeo ID or URL. media-id – An attachment ID for a media file in your WordPress media library or the URL to a hosted video. Additional Player Content captions – Attachment ID or URL to .vtt captions file. Optional pipe separator for language code and label. subtitles – Attachment ID or URL to .vtt subtitles file. Optional pipe separator for language code and label. chapters – Attachment ID or URL to .vtt chapters file. Optional pipe separator for language code and label. descriptions – Attachment ID or URL to .vtt audio descriptions file. Optional pipe separator for language code and label. youtube-desc-id – YouTube URL or ID of a described version of the video youtube-sign-src – YouTube URL or ID of a sign language interpreted accompanying video vimeo-desc-id – Vimeo URL or ID of a described version of the video All captions, subtitles, chapters, and descriptions tracks must be in .vtt 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. Either an attachment ID or a URL for your track .vtt is required; you can optionally add a language code and a custom label: captions="/path/to/file.vtt|es|Español" By default, the language will be your WordPress installation language, with the labels “Captions”, “Subtitles”, “Chapters” or “Audio Description”. Player Options youtube-nocookie – “true” or “false” (use “true” to embed YouTube untracked, for added privacy) autoplay – “true” or “false” (default is “false”) loop – “true” or “false” (default is “false”) playsinline – “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. hidecontrols – “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. poster – the URL of a poster image, displayed before the user presses Play width – a value in pixels (by default, the player will be sized to fit its container) height – a value in pixels (by default, the height of the player will be in proportion to the width) heading – 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. speed – “animals” or “arrows” (default is “animals”) start – start time at which to start playing the media, in seconds. Some browsers do not support this. volume – “0” to “10” (default is “7” to avoid overpowering screen reader audio). Some browsers do not support this. seekinterval – 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. nowplaying – “true” or “false” to include a “Selected Track” section within the media player (default is “false”). transcript-div – ID attribute of a target element that will contain the video transcript id – a unique id for the player (if omitted, one will be automatically assigned) Examples Example 1 This example uses HTML to add an audio player to the page, with one source (an MP3 file). html Example 2 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). html Example 3 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. html [ableplayer poster="21" media-id="24" captions="25|en|English" subtitles="26|es|Español" descriptions="27" chapters="28"] Example 4 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). [ableplayer youtube-id="XXXXXXXXXXX" youtube-desc-id="YYYYYYYYYYY"] Example 5 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). [ableplayer vimeo-id="XXXXXXXXX" vimeo-desc-id="YYYYYYYYY"] The Able Player plugin was originally created by Terrill Thompson.
Top keywords
- player33×3.42%
- video17×1.76%
- able16×1.66%
- able player16×1.66%
- id14×1.45%
- url12×1.24%
- audio11×1.14%
- default11×1.14%
- false11×1.14%
- example10×1.04%
- add9×0.93%
- captions9×0.93%
Toolbelt
A collection of simple addons that provide every day functionality with privacy and speed. There’s very few options, and no unnecessary filler. It does exactly what it needs to do and nothing else. Toolbelt takes a privacy first approach to adding features. Everything happens on your server. No data is sent to third party servers without your explicit consent. No data is loaded from third parties (for example social sharing scripts). Taking inspiration from Jetpack I want to rebuild the features I use the most and make them as simple and fast as possible. Toolbelt has been featured on The WordPress Tavern in an interview with me. You can read more about the creation of the plugin and my desire for a more private internet. Gutenberg Blocks Some of the Toolbelt modules include blocks to make working with the generated content easier. The available blocks are: Contact Form – The simplest way to have people get in touch. Works with the spam module. Post Categories – A category content list for magazine and newspaper themes. Simple Slider – A fast, CSS powered slider. No JavaScript and easy to edit. Projects Grid – to list a collection of projects. These can be filtered by project category. Testimonials Grid – to list a group of testimonials. Great for showing off! 🙂 Markdown – for those who like a simpler writing experience. Sitemap – Easily list all posts, pages, Categories and Projects. Star Rating – Rate things with a simple visual interface. Breadcrumbs – for full site editing. Related posts – for full site editing. All Features Toolbelt has a lot of features. The complete list is below. Admin Interface Tweaks – Small CSS changes to make the interface nicer to use. Avatars – Algorithmicly generated private avatars that are consistent across websites. Breadcrumbs Contact Form – Gutenberg compatible & private. Supports the spam blocker module. Cookie Banner CSP Header Disable Comment Urls – Removes comments urls from your site. Disable REST API – Disable the REST API from public usage. Fast 404 – Stops WordPress from loading the full 404 page for images and other content. Reduces server usage. Footnotes Get Image – Find a featured image for posts that do not have one assigned. Heading Anchors – Add anchor names to headings so that they can be linked to. Iframe Privacy Shield – Remove iframes and add a clickable screen so that they load when the user wants to see them. Infinite Scroll Jetpack Dev Mode – Disable Jetpacks connection so that only local functions are enabled. Lazy Loading Layout Grid – A nicer columns block. Markdown Monetization – Enable Coil Web Monetization. OEmbed – Add additional OEmbed providers. Optimization – Remove WordPress features that are rarely used. Portfolio – Portfolio custom post type and blocks. Post Category – A post category block. Random Redirection – Randomly redirect to a blog post. Related Posts Remove IP Addresses – Remove IP addresses from comments for user privacy (spam protection still works). Responsive Videos Search Redirect – If there’s a single search result redirect to it instead of displaying the restuls. Sitemap – Sitemap block. Slider – JavaScript free CSS slider block. Social Menu – Replace social links with icons in navigation blocks. Spam Blocker – Privacy focused spam blocker. Static Social Sharing – Link to social sharing pages, and don’t load social network content on your site. Stats – Enable privacy focused analytics providers like Fathom. Testimonials – Testimonials Custom post types and blocks. Tidy Notifications – Move plugin and theme notifications to a sidebar. Typographic Widows – Remove widows in post titles. Widget Display – Set rules for widget visibility. Toolbelt is Private Every week there’s a new story about Facebook (or Google, or Amazon, or whoever) tracking people inappropriately, or selling user details. Or some security breach that leaks users passwords or credit card info. Privacy is a big topic and frankly, it’s scary how much big corporations like Google, Facebook, and Twitter know. To ensure Toolbelt is as privacy focused as possible it: Does not phone out. No data is shared with third parties. Does not use standard social sharing javascripts (loaded from social networks servers). Does not track your usage of the plugin. Does not add generator comments, or secret promotional comments to your site html. Toolbelt is Fast Slow websites make me sad. I don’t want to add anything to Toolbelt that will impact site load speed. My Google Pagespeed score should not move from 100. Why? Faster sites are shown to increase conversions and time on site. Google loves fast sites and improves their search rankings. In addition fast sites are great for people with slower internet access, or on mobile data, and use less resources to generate the page. So many benefits! To be fast Toolbelt: Doesn’t use jQuery or any other javascript framework. All javascript is vanilla js, and minified. Minifies all assets (JS and CSS). Loads all assets inline. They are already small, and loading them directly on the page means there are no server requests. Only loads things when they are needed. JS and CSS are only loaded for activated modules. Very few options. There’s one main database option, an array that stores what modules are active. And another that stores settings for some modules. Uses the minimum code possible. Minimum Javascript and PHP. Less code means more speed, and fewer bugs. All options are disabled by default. You enable only the ones you need. Built for developers Toolbelt is built with developers in mind. It has a collection of hooks and filters to enable you to make the modules work the way you want. If you’re intersted to jump in the project, there are opportunities for developers at all levels to help out. Contribute to Toolbelt on GitHub and join the party. 🎉 The code can be found on Github Documentation with code examples can be found on the wiki You can reach out to me with questions or problems on Twitter