dariyam

This plugin will allow WordPress users to automatically provide an audio version of their written content, using the HearWho Text to Speech engine. Upon creation of a new blog post a “Listen to this text” link will be prepended to blogs and allow the user to listen to the blog entry rather than read it. This is useful for folks trying to read-content while on the go, for visually impaired users visiting your blog, or for those that would just rather have content read to them, rather than read it directory. Users of this plug must obtain a free license key on https://hearwho.com to use the functionality. A free key is valid for use on conversion of up to 3,000 characters (most blog posting are usually under 3,000 characters). If you need more than this, we charge a very modest fee to substantially increase those limits (3.99 USD/month).
Instructions:
<ol>
<li>Install plugin through your WordPress administration page. (Or, extract the contents of the zip file and upload it directly into the plugins folder: “/wp-content/plugins/”).</li>
<li>Next, activate plugin and go to the HearWho Settings page in your WordPress site and enter your API Key. (If you need an API key, create a free account on HearWho.com and visit this same page to see your key.)</li>
<li>Now, every new blog post you publish, or anytime you update an existing blog post, a high quality “spoken version” of your posting will be prepended to your posting.</li>
</ol>
Note: the plugin will not retroactively add speech versions of existing blog posts. If you would like to add an audio version for an older post, simple open up the edit screen (not quick edit) as you normally do for an older post, an simply click the update or save button.
TheHearWho Automated Text to Speech is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <a href="https://www.gnu.org/licenses/" rel="nofollow ugc">https://www.gnu.org/licenses/</a>
You can contact us at support@HearWho.com

The HearWho Automated Text to Speech plugin

This plugin will allow WordPress users to automatically provide an audio version of their written content, using the HearWho Text to Speech engine.

Weston Ruter

Add text-to-speech (TTS) to content, with playback controls, read-along highlighting, multi-lingual support, and settings for rate, pitch, and voice.
<ul>
<li>Uses local text-to-speech engine in user’s browser. Directly interfaces with the <code>speechSynthesis</code> browser API. Zero external requests or dependencies.</li>
<li>Words are selected/highlighted as they are being spoken to allow you to read along.</li>
<li>Skips speaking elements that should not be read, including footnote superscripts (the <code>sup</code> element).</li>
<li>Pauses of different length added are between headings versus paragraphs.</li>
<li>Controls remain in view during playback, with each the current text being spoken persistently being scrolled into view. (Requires browser support for <code>position:sticky</code>.)</li>
<li>Back/forward controls allow you to skip to the next paragraph; when not speaking, the next paragraph to read will be selected entirely.</li>
<li>Select text to read from that point; click on text during speech to immediately change position.</li>
<li>Multi-lingual support, allowing embedded text with <code>[lang]</code> attribute to be spoken by the appropriate voice (assuming the user has it installed).</li>
<li>Settings for changing the default voice (for each language), along with settings for the rate of speech and its pitch. (Not supported by all engines.) Changes can be made while speaking.</li>
<li>Hit escape to pause during playback.</li>
<li>Voice preferences are persistently stored in <code>localStorage</code>, with changes synced across windows (of a given site).</li>
<li>Ability to use JS in standalone manner (such as in bookmarklet).</li>
<li>Known to work in the latest desktop versions of Chrome, Firefox, and Safari. (Tested on OSX.) It does not work reliably in mobile/touch browsers on Android or iOS, apparently due both to the (still experimental) <code>speechSynthesis</code> API not being implemented well enough on those systems and/or programmatic range selection does not work the same way as on desktop. For these reasons, the functionality is disabled by default on mobile operating systems.</li>
</ul>
<a href="https://westonruter.github.io/spoken-word/test/example.html" rel="nofollow ugc">Try it out</a> on standalone example with some test content.
<h4>Theme Config</h4>
The settings for Spoken Word are presented in an HTML5 <code>dialog</code> element. For browsers that do not yet support this feature, the plugin bundles the <a href="https://github.com/GoogleChrome/dialog-polyfill" rel="nofollow ugc">dialog-polyfill</a>. The polyfill is only included if it is detected the browser does not support <code>dialog</code> natively. The inclusion of the polyfill can be disabled by adding the following to your theme or plugin:
<pre>
add_filter( 'spoken_word_include_dialog_polyfill', '__return_false' );
</pre>
For themes that have a sticky header (such as the nav menu in Twenty Seventeen) you may need to add some additional CSS to ensure that the sticky-positioned playback controls do not get hidden behind the sticky header. For example in Twenty Seventeen, you can add the following to the Custom CSS in the Customizer:
<pre>
@media screen and (min-width: 782px) {
 body:not(.admin-bar) .spoken-word--active {
 top: calc( 0.5em + 70px );
 }
 body.admin-bar .spoken-word--active {
 top: calc( 0.5em + 32px + 70px );
 }
}
</pre>
<h4>Internals</h4>
A bookmarklet can be used to load the Spoken Word functionality into any site, even non-WordPress sites where the plugin is not installed. The key is to use the appropriate <code>contentSelector</code>:
<pre>
( () => {
 const link = document.createElement( 'link' );
 link.rel = 'stylesheet';
 link.href = 'https://unpkg.com/spoken-word/css/style.css';
 document.head.appendChild( link );

 const script = document.createElement( 'script' );
 script.src = 'https://unpkg.com/spoken-word/dist/spoken-word.js';
 script.addEventListener( 'load', () => {
 spokenWord.initialize( {
 contentSelector: [ /* 👈 Amend as desired. */
 '.hentry',
 '.entry-content',
 '.h-entry',
 '.e-content',
 '[itemprop="articleBody"]',
 ].join( ', ' )
 } );
 } );
 document.head.appendChild( script );
} )();
</pre>
The <code>spokenWord.initialize()</code> function takes an object as its argument which can have the following properties:
<pre>
 * @param {string} contentSelector - CSS Selector to find the elements for speaking.
 * @param {Element} rootElement - Root element within which to look for content.
 * @param {Object} chunkifyOptions - Options passed into chunkify.
 * @param {boolean} useDashicons - Whether to use Dashicons.
 * @param {Object} defaultUtteranceOptions - Default utterance options when none are supplied from localStorage.
</pre>
The dialog and the controls are rendered using <a href="https://preactjs.com/" rel="nofollow ugc">Preact</a>. For a list of all the modules used by this plugin, see the <a href="https://github.com/westonruter/spoken-word/blob/master/package.json" rel="nofollow ugc">package.json</a>.
This plugin is <a href="https://github.com/westonruter/spoken-word" rel="nofollow ugc">developed on GitHub</a> where the source can be viewed. Please <a href="https://github.com/westonruter/spoken-word/issues" rel="nofollow ugc">report issues</a> there. Pull requests welcome. The <code>spoken-word</code> package is also <a href="https://www.npmjs.com/package/spoken-word" rel="nofollow ugc">published on npm</a>.

Spoken Word

Add text-to-speech (TTS) to content, with playback controls, read-along highlighting, multi-lingual support, and settings for rate, pitch, and voice.

The HearWho Automated Text to Speech plugin vs Spoken Word