Able Player, accessible HTML5 media player vs Bubuku Media Library

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.

Bubuku Media Library helps content and marketing teams audit, monitor and optimize images in WordPress. Track file sizes, identify missing alt text, export reports, receive email summaries and connect AI assistants through MCP. New in version 1.3.0: Bubuku Media Library includes an MCP Server that allows compatible AI assistants and developer tools to interact with your WordPress Media Library through a secure endpoint with role-based permissions. You can: Sort the Media Library by file size to easily identify large files. Filter images that don’t have alternative text (alt text). Use size-based filters (for example: optimal size, medium size, large size) to prioritize which images to optimize first. Run a Bulk Action in the Media Library to calculate file sizes for existing uploads. Export CSV reports including file size, format (MIME type), URL, alt text, image date, post title and post URL — ideal for audits or sharing with your team. See a summary of your Media Library in a dashboard widget, including how many images are heavy or missing alt text. Configure weekly or monthly email reports so you can monitor the optimization status of your images without logging into WordPress. Connect MCP-compatible AI assistants to your Media Library using role-based permissions and configurable abilities. More information (in Spanish) about how the plugin works: How to know if we have to reduce weight to the image and Alt SEO attribute AI & MCP Integration Bubuku Media Library includes a built-in MCP Server that allows compatible AI assistants and development tools to securely interact with your WordPress Media Library. Available MCP abilities include: Listing media library attachments. Reviewing image metadata and alt text coverage. Exporting media audits to CSV. Accessing media library summary metrics. Triggering reports and diagnostics. Managing media accessibility workflows. Each ability can be enabled or disabled individually and restricted to a minimum WordPress role. This allows you to safely connect AI assistants like Claude Desktop, Codex, Cursor and other MCP-compatible clients to audit images, review missing alt text, generate reports and automate media management workflows, while keeping permissions under your control. Typical use cases include: Finding images without alt text. Exporting media audits for content reviews. Checking image size distribution. Generating accessibility reports. Integrating WordPress media workflows with AI assistants. Automating repetitive media library review tasks. Quick Start From your server (SSH), move the plugin folder to the plugins directory: wp-content/plugins/bubuku-media-library/ Activate the plugin via the WordPress admin or using WP-CLI: wp plugin activate bubuku-media-library (Optional) Run the bulk action in Media > Library to calculate file sizes for existing images. Evaluate results Recommended Tools – Lighthouse (in Chrome DevTools) — Analyze image weight and format, as well as the use of alternative text (ALT). – WebPageTest — Check how images affect real-world load times. – Squoosh — Compare visual quality and file size savings when optimizing images. – WAVE Accessibility Tool — Verify whether images are missing ALT attributes or if the alternative texts are descriptive. Evaluation Guidelines – Identify images without ALT text or with excessive file size before running external tests. – After replacing large images or adding ALT text, repeat your evaluations to confirm improvements. – Evaluate both new and existing content — not only the most recent uploads. – Define an internal size limit (for example, 200 KB per image) and monitor it regularly. – Keep in mind that accessibility also affects SEO and overall user experience. SUPPORT Need help or have a suggestion? Please use the official WordPress.org Support Forum for any issues related to the plugin. Official Website For additional information or to get in touch with the development team, please visit our official website. Like the plugin? Please leave a 5-star review and help others discover Bubuku Media Library. ABOUT BUBUKU_CODE We develop custom solutions for WordPress focused on performance, accessibility, and maintainable code. Our work includes plugins, themes, and integrations designed to improve the daily workflow of marketing and content teams.