Matthias Kittsteiner

epiphyt

<p>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.</p>
<p><strong>Note: This plugins requires the PHP extension <a href="https://www.php.net/manual/en/book.dom.php" rel="nofollow ugc">“Document Object Model” (php-dom)</a>.</strong></p>
<h4>Features</h4>
<ul>
<li>Fully support of the block editor</li>
<li>Built with accessibility in mind</li>
<li>Create forms with an unlimited number of fields</li>
<li>Select from a wide variety of field types</li>
<li>Use a predefined form or start from scratch</li>
<li>Store form submissions in the WordPress backend</li>
<li>Integrated honeypot for spam protection</li>
<li>Integrated knowledge base for field types</li>
<li>Client-side and server-side validation</li>
</ul>
<h4>Getting started</h4>
<ol>
<li>Add the “Form Block” block anywhere you want to enable a form in your block editor.</li>
<li>Select a predefined form or start from scratch.</li>
<li>Add/Edit/Remove fields to your form as you like. You can select from input, select and textarea fields.</li>
</ol>
<p>After submission, the form data will be sent to the email address you have set in the settings.</p>
<h4>Coming soon</h4>
<p>There is much more planned for Form Block. Here is a small selection of features that are coming soon:</p>
<ul>
<li>Flood Control</li>
<li><a href="https://wordpress.org/plugins/antispam-bee/" rel="ugc">Antispam Bee</a> integration</li>
<li>Custom date picker</li>
<li>More customization options</li>
</ul>
<h4>Pro version</h4>
<p>There is also a Pro version of Form Block available. It offers additional features, such as:</p>
<ul>
<li>Extended server-side validation</li>
<li>Custom recipient(s) for each form</li>
<li>Custom form action</li>
<li>Upload via drag and drop</li>
<li>Storing files in WordPress instead of attaching them to an email</li>
<li>Global defined consent checkbox</li>
<li>Field dependencies</li>
<li>Advanced functionality for accessibility</li>
</ul>
<p>You can find more information at <a href="https://formblock.pro/en/" rel="nofollow ugc">https://formblock.pro/en/</a>.</p>


Form Block


Just tried out this simple Form Block plugin and it's awesome – every block in the editor should be like this. Making a contact form is super easy. You just install it, add the block in the editor, pick the pre-made contact form, and you’re done. Editing the fields is a breeze, and it even includes a GDPR checkbox automatically. It works right away, sending the info to the WP admin email without any extra setup. The free version is perfect for beginners.


Effortless Contact Form Plugin, Easily Used as Block, GDPR Compliant

An extensive yet user-friendly form block.

Whodunit

Jb Audras

Guillaume TURPIN

<p><strong>Disclaimer: This plugin was merged into WordPress Core. It is not relevant anymore to install it. I plan to ask for a removal from the repo by the end of the year.</strong></p>
<p>The intent of this plugin is to provide a way to ensure any language change in the content of a page is indicated to assistive technologies. This feature is not available by default in the block editor so it is difficult to make a website fully compliant to WCAG guidelines using the block editor for now.</p>
<p>We clearly hope this feature will be natively implemented in the block editor in middle term, because this very simple feature is really needed to help people to create accessible websites. But in short terms, we need a solution and this plugin is a solution you may want to use to make your website compliant to accessibility guidelines 🙂</p>
<p>For more context: this plugin helps you to make your website compliant to the Web Content Accessibility Guidelines (WCAG) success criterion 3.1.2: “Language of Parts”. The purpose of this success Criterion is to ensure that user agents can correctly present content written in multiple languages.</p>
<p>As per Web Content Accessibility Guidelines:</p>
<p>This makes it possible for user agents and assistive technologies to present content according to the presentation and pronunciation rules for that language. This applies to graphical browsers as well as screen readers, braille displays, and other voice browsers.</p>
<p>Both assistive technologies and conventional user agents can render text more accurately if the language of each passage of text is identified. Screen readers can use the pronunciation rules of the language of the text. Visual browsers can display characters and scripts in appropriate ways.</p>
<p>This is especially important when switching between languages that read from left to right and languages that read from right to left, or when text is rendered in a language that uses a different alphabet. Users with disabilities who know all the languages used in the Web page will be better able to understand the content when each passage is rendered appropriately.</p>


Lang Attribute for the Block Editor

Add lang attribute to the text formatting toolbar in the block editor.

Form Block vs Lang Attribute for the Block Editor