AxesWeb

AxesWeb Accessibility Solution adds an accessibility toolbar to your WordPress site to help users customize their reading experience, in line with WCAG 2.1 and 2.2 guidelines. The widget is lightweight, configurable from the settings page, and designed to be theme-agnostic.
<h3>External services</h3>
This plugin connects to the AxesWeb CDN to load the accessibility widget JavaScript. It is required to render the accessibility UI and features in the front‑end.
What data is sent and when: 
– When the widget is loaded, the browser requests the script file from the CDN. No personal data is sent by the plugin to AxesWeb. The plugin does not add cookies or tracking. 
– When the optional accessibility feedback form is enabled, submissions are sent to your WordPress site via admin-ajax.php using a nonce-protected action. Emails are dispatched by your site to the recipient you configure. No data is sent to AxesWeb for this feature.
Service provider: AxesWeb 
– Script URL pattern: <code>https://cdn.axesweb.com/widget/{version}/accessibility-widget.js</code> 
– Terms of Service: https://www.axesweb.com/termini-di-servizio/ 
– Privacy Policy: https://www.axesweb.com/privacy-policy/
Additionally, when you verify your API key from the plugin settings, the plugin makes a request to the AxesWeb verification API to validate your license.
What data is sent and when: 
– On verification: your site URL and the API key you enter are sent in a JSON request to the verification endpoint to confirm validity and activate features. 
– No periodic personal data transfers occur. A lightweight validity recheck may occur based on stored TTL to keep the activation status up to date.
Service provider: AxesWeb 
– Verification endpoint: https://www.axesweb.com/wp-json/axesweb/v1/key/verify 
– Terms of Service: https://www.axesweb.com/termini-di-servizio/ 
– Privacy Policy: https://www.axesweb.com/privacy-policy/
<h3>License</h3>
This plugin is released under the GPL v2 or later. 
See <code>https://www.gnu.org/licenses/gpl-2.0.html</code>.

AxesWeb Accessibility Solution


Despite the presence of many accessibility plugin, this is the real completely free plugin. And it works like charm. Thanks


the first free accessibility plugin

WCAG 2.1 and 2.2-ready accessibility toolbar for WordPress with a configurable, lightweight widget.

LewisCowles

daronspence

This short, handy plugin will add playback buttons to your audio, video & playlist elements added via the built-in WordPress shortcodes for media using mediaelement.js.
Each set of buttons is configured for it’s corresponding element on the page, so you can adjust the speed of multiple files independently.
There is currently no persistence implemented in this plugin. It just scratches an itch to be able to broadly adjust media playback speeds using the HTML api.
NOTE: This uses the HTML5 media Element API. Any browser not supporting these or using the Flash Player fallback will miss out on this functionality.
<h4>Developers</h4>
Two hooks are provided within this plugin.
<ul>
<li>
<code>media-playback-speed-generate-controls</code> provides a single argument which is a boolean. If you return this as false, this will stop buttons being added to a media player. This is intended for advanced setups where markup for controls might be placed manually elsewhere on the page such as a sticky footer. So long as controls follow the built-in markup (being within the body tag and have a playback-rate-button class (no default styling, used for enabling DOM access only).
</li>
<li>
‘media-playback-speed-data’ provides the default array containing arrays as items with <code>rate</code>, <code>title</code> and <code>label</code> entries, which set the playback rate, the title and aria-title for the buttons as well as adjust the button text.
</li>
</ul>
<h4>Theme & Front-end</h4>
The <code>.playback-rate-button.mejs-active</code> and/or <code>.playback-rate-button.active-playback-rate</code> CSS-selectors allow you to style the active speed (per-player).
Initially mejs-active class was added in order to create media-playback-js compatible / familiar class names.
Now that Gutenberg does not add these, it makes sense to for-now add two sets of classes.
The <code>.playback-rate-button.mejs-active</code> selector will be deprecated in version 2.
<h4>Troubleshooting</h4>
This works with the traditional <code>audio</code>, <code>video</code> and <code>playlist</code> shortcodes so long as WordPress uses the JavaScript player.
With the latest 1.1.1 release this also works for HTML5 audio and video too, however you will need to implement your own controls which have the <code>playback-rate-button</code> class and follow the patterns of this.
HTML5 raw controls do not have a playlist the author is aware of, and they use global state, so playback rate is per-page.
There is currently no history as part of this plugin, however a sister plugin could be authored and hooks added to it to store playback rate.
Please ensure that you have no broken javascript, or wrap all functions in <code>(function() { // do things })()</code> blocks to ensure nothing interferes with this plugin. This plugin does this so that it should not interfere with your site, even in browsers and pages which do not support this plugin.
<h4>Feedback</h4>
Please feel free to <a href="https://github.com/CODESIGN2/media-playback-speed/issues" rel="nofollow ugc">suggest</a> improvements, report conflicts, and/or make suggestions for integration hooks etc.

Media Playback Speed

Add speed controls to audio and video hosted from your WordPress blog.

AxesWeb Accessibility Solution vs Media Playback Speed