Adam Rosenkoetter

RayWP Accessibility is a comprehensive WordPress plugin that helps improve your website’s accessibility to better meet WCAG guidelines and accessibility standards. The plugin implements ARIA attributes and accessibility improvements throughout your entire page output, including navigation, headers, footers, and all page elements, not just post content. Unlike widget-based solutions, this plugin works automatically without requiring user intervention.
Important: This plugin helps identify and fix common accessibility issues, but no automated tool can guarantee full WCAG compliance. Manual testing with assistive technologies and expert review are still essential for true accessibility conformance.
Automated Detection:
<ul>
<li>Site-wide accessibility scanning across multiple pages</li>
<li>Color contrast ratio checking (WCAG 2.1 SC 1.4.3)</li>
<li>Missing iframe title detection</li>
<li>Auto-playing video detection</li>
<li>Form accessibility issue scanning</li>
<li>Detailed issue reporting with recommendations</li>
</ul>
Automated Fixes:
<ul>
<li>Skip navigation links (WCAG 2.1 SC 2.4.1)</li>
<li>Enhanced keyboard focus indicators (WCAG 2.1 SC 2.4.7)</li>
<li>ARIA attribute injection via CSS selectors</li>
<li>Color contrast overrides for problem elements</li>
<li>Missing iframe titles added dynamically</li>
<li>Video controls for auto-playing media</li>
</ul>
Developer Tools:
<ul>
<li>Unlimited ARIA attribute rules using CSS selectors</li>
<li>Complete selection of ARIA landmark roles</li>
<li>Real-time CSS selector validation before applying</li>
<li>Output buffer processing for entire page coverage</li>
</ul>
Supported Form Plugins:
<ul>
<li>Contact Form 7 (full scanning and fixes)</li>
<li>WPForms (scanning)</li>
<li>Gravity Forms (basic scanning)</li>
</ul>
Who This Plugin Helps:
<ul>
<li>Site owners needing to improve accessibility compliance</li>
<li>Developers adding ARIA attributes without manual coding</li>
<li>Content editors identifying accessibility issues before publishing</li>
<li>Agencies managing accessibility across client sites</li>
</ul>
<h3>External services</h3>
This plugin does not use any external services – all analysis occurs within the plugin.

RayWP Accessibility

Scan your entire WordPress site for WCAG accessibility issues, apply ARIA attributes automatically, and detect color contrast problems - all without e …

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.

RayWP Accessibility vs Media Playback Speed