Form Block vs ResponsiveVoice Text To Speech

WordPress offers several (contact) form plugins, but most of them are not up-to-date anymore when it comes to creating forms. Form Block tackles this problem by utilizing the block editor’s power. It enables you to create a form effortlessly within the block editor itself, which makes the process of creating a form much more enjoyable and similar to creating other types of blocks. This innovative approach to form creation ensures that Form Block stands out from other WordPress form plugins. Note: This plugins requires the PHP extension “Document Object Model” (php-dom). Features Fully support of the block editor Built with accessibility in mind Create forms with an unlimited number of fields Select from a wide variety of field types Use a predefined form or start from scratch Store form submissions in the WordPress backend Integrated honeypot for spam protection Integrated knowledge base for field types Client-side and server-side validation Getting started Add the “Form Block” block anywhere you want to enable a form in your block editor. Select a predefined form or start from scratch. Add/Edit/Remove fields to your form as you like. You can select from input, select and textarea fields. After submission, the form data will be sent to the email address you have set in the settings. Coming soon There is much more planned for Form Block. Here is a small selection of features that are coming soon: Antispam Bee integration Custom date picker More customization options Pro version There is also a Pro version of Form Block available. It offers additional features, such as: Extended server-side validation Custom recipient(s) for each form Custom form action Upload via drag and drop Field dependencies Multi-step forms with sections Advanced functionality for accessibility You can find more information at https://formblock.pro/en/. Contribution Feel free to contribute. The code is available at GitHub. Documentation You can find the documentation for Form Block at docs.epiph.yt.

ResponsiveVoice adds HTML5 text-to-speech to your WordPress posts and pages — with nothing extra to install, across all smartphone, tablet and desktop devices. Your readers can listen with a tap: add a Listen button through the Gutenberg block or a shortcode, or turn on the WebPlayer to read a whole post aloud. It supports 51 languages through 158 voices out of the box — plus thousands of premium neural voices from major cloud providers (Google Cloud, Microsoft Azure, OpenAI and more) via bring-your-own-key on v2 accounts. Languages include UK English, US English, Spanish, French, German, Italian, Greek, Hungarian, Turkish, Russian, Dutch, Swedish, Norwegian, Japanese, Korean, Chinese, Chinese (Hong Kong), Chinese Taiwan, Hindi, Serbian, Croatian, Bosnian, Romanian, Catalan, Australian, Finnish, Afrikaans, Albanian, Arabic, Armenian, Czech, Danish, Esperanto, Hatian Creole, Icelandic, Indonesian, Latin, Latvian, Macedonian, Moldavian, Montenegrin, Polish, Brazilian Portuguese, Portuguese, Serbo-Croatian, Slovak, Spanish Latin American, Swahili, Tamil, Thai, Vietnamese and Welsh. Support and Questions visit here first: Support Useful Links: Live Demo Homepage Documentation Features: Listen to any post or page with the tap of a button A Gutenberg “Listen” block with a live voice picker — plus shortcodes for the classic editor The WebPlayer: a customizable player that reads a whole post aloud (v2 accounts) 51 languages through 158 voices, plus thousands of premium neural voices via bring-your-own-key (v2) Easy access to your content for every visitor — tap to listen to any page or post A more accessible website for a range of users, including the visually impaired and the elderly Web Content Accessibility Guidelines (WCAG) 2.0, ADA and BS 8878:2010 features Usage: Add a Listen button with the block In the block editor, insert the ResponsiveVoice Listen Button block wherever you want a Listen button. Pick a voice from the live list, adjust rate, pitch and volume, and preview it — all in the editor. Turn on the WebPlayer (v2) The WebPlayer is a ResponsiveVoice v2 feature that reads the whole post aloud — and the one ResponsiveVoice website feature you control right from WordPress. On a v2 account, open the ResponsiveVoice menu in your WordPress admin to enable or disable it and customise its appearance, position and behaviour, choose which content types show it, and override it per post. Your other ResponsiveVoice website features (such as the Welcome message that plays when a page loads) are configured in your ResponsiveVoice account dashboard. Shortcodes (classic editor and back-compatible) Add a Listen button anywhere in a post or page: [responsivevoice_button] Set the voice and the button label: [responsivevoice_button voice=”US English Female” buttontext=”Play”] Read just a section by wrapping it: [responsivevoice]Text you want ResponsiveVoice to read[/responsivevoice] Place the button after the text (it appears before by default): [responsivevoice buttonposition=”after”]Text you want ResponsiveVoice to read[/responsivevoice] Adjust rate, pitch and volume: [responsivevoice_button rate=”1″ pitch=”1.2″ volume=”0.8″ voice=”US English Female” buttontext=”Play”] Leave the voice unset to use your account’s default voice. A full list of voice names is in the Documentation. Your API key Create a free account and add your API key from the ResponsiveVoice admin menu to unlock the full voice catalogue and the WebPlayer. Without a key, the plugin runs in demo mode so you can try it first. For more details, please see the Documentation Requirements ResponsiveVoice runs in your visitors’ browsers, so there is nothing to install or configure on your server. It works in modern browsers across desktop and mobile. External services This plugin relies on the ResponsiveVoice service to synthesize speech, so text and your API key are sent to it from visitors’ browsers. The ResponsiveVoice library/SDK is loaded from code.responsivevoice.org / cdn.responsivevoice.org, or, in “bundled” delivery mode, served from your own site. When a visitor plays audio, the text to read and your site’s API key (a public website identifier, not a secret) are sent to the ResponsiveVoice Text-To-Speech API to generate audio. The visitor’s browser reads your site’s ResponsiveVoice configuration — your account’s website feature settings — from texttospeech.responsivevoice.org, so those features work on your site. When the ResponsiveVoice SDK plays audio (the WebPlayer, buttons or shortcodes), it reports the number of characters spoken to app.responsivevoice.org. This is a single number for usage accounting: no personal or user information, and not the spoken text, is sent. It is required so your account’s API usage is attributed correctly. Terms of Service: https://responsivevoice.org/terms/ Privacy Policy: https://responsivevoice.org/privacy-policy/