Marco Almeida | Webdados

Naked Cat Plugins

This plugin aims to ensure that any language change in a page’s content is indicated to assistive technologies at the container block level, helping a website comply with WCAG guidelines.
This feature is available on the core block editor only at a text formatting level after code from <a href="https://wordpress.org/plugins/lang-attribute/" rel="ugc">Jb Audras plugin “Lang Attribute for the Block Editor”</a> was merged into core. The objective of this plugin is to provide the same functionality at a container block level (Group – including all its variants, Columns, Cover, and other specific block types) so that the language applies to all child elements, no matter the kind of content inside.
The plugin also supports setting the language at the page or post level, both on the blocks and the classic editor. When an entire page is written in a different language than the website’s default, you can override the HTML <code>lang</code> and <code>dir</code> attributes for that specific page directly from the Document Settings sidebar, without needing to wrap everything in a container block. 
For even broader coverage, the plugin supports setting the language at the template level in the Site Editor (Appearance → Editor → Templates). A language set on a template is automatically applied to all pages and posts using that template, unless a specific language is set at the individual post or page level — in which case the post-level setting takes precedence. 
This plugin is heavily inspired by the Jb Audras plugin (including this readme file). The development started at WordCamp Europe 2025 Contributor Day, by Marco Almeida from <a href="https://profiles.wordpress.org/nakedcatplugins/" rel="nofollow ugc">Naked Cat Plugins</a> / <a href="https://profiles.wordpress.org/webdados/" rel="nofollow ugc">Webdados</a>, and the help from <a href="https://profiles.wordpress.org/welcher/" rel="nofollow ugc">Ryan Welcher</a> on the code side and <a href="https://profiles.wordpress.org/alh0319/" rel="nofollow ugc">Amber Hinds</a> on the accessibility compliance side.
For more context: this plugin helps you to make your website compliant with the Web Content Accessibility Guidelines (WCAG) success criteria:
<ul>
<li>3.1.1 – Language of Page: The default human language of each web page can be programmatically determined. Use the template-level setting when all posts or pages sharing a template are in the same language, or the page-level setting when an entire page or post is written in a language other than the website or template default.</li>
<li>3.1.2 – Language of Parts: The human language of each passage or phrase in the content can be programmatically determined. Use the block-level setting when only specific sections within a page are in a different language.</li>
</ul>
The purpose of these success criteria is to ensure that user agents can correctly present content written in multiple languages.
Keep in mind that you should set the <code>lang</code> and <code>dir</code> attributes only on a container block or page if the content is written in a language different from the one set globally on your website.
As per Web Content Accessibility Guidelines:
This enables user agents and assistive technologies to present content according to the presentation and pronunciation rules of that language. This applies to graphical browsers, screen readers, braille displays, and other voice browsers.
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 language’s pronunciation rules. Visual browsers can display characters and scripts appropriately.
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.
That’s not just good for accessibility. It’s also great for SEO. Search engines like Google can better understand your content when languages are clearly defined. That means improved indexing and potentially better rankings.
Banner photo by <a href="https://unsplash.com/@hannahwrightdesigner?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash" rel="nofollow ugc">Hannah Wright</a>.
<h3>Supported block types</h3>
<ul>
<li>Group (<code>core/group</code>): Group contents together and set a language for them</li>
<li>Columns (<code>core/columns</code> and <code>core/column</code>): Organize content into a set of columns and set a language for all the columns or a specific column</li>
<li>Cover (<code>core/cover</code>): Set the language to all the contents inside a cover block</li>
<li>Navigation (<code>core/navigation</code>): Create full navigation menus in different languages</li>
<li>Submenu (<code>core/navigation-submenu</code>): Set a different language on a sub-section of your menu (for example, if you have the default language pages on the first level and a sub-menu with pages in another language)</li>
<li>Page List (<code>core/page-list</code>): List all the pages on your website that are written in a different language and created as a child of the main page of that language</li>
<li>Content (<code>core/post-content</code>): Set the post content on a custom template to a different language</li>
</ul>
<h3>Features</h3>
<ul>
<li>Set the language and text direction at the template level in the Site Editor: a “Template Language” panel lets you define the default language for all pages and posts using that template, which is automatically applied unless overridden at the individual post or page level</li>
<li>Set the language and text direction for an individual page or post, both on the blocks and classic editor: a “Page Language” panel in the Document Settings sidebar overrides the HTML <code>lang</code> and <code>dir</code> attributes for that specific page, taking precedence over any template-level setting</li>
<li>Add <code>lang</code> and <code>dir</code> attributes to Group, Columns, Cover, and other specific WordPress Blocks, mentioned above</li>
<li>Show visual outline around blocks that have a language attribute set – For easy identification of blocks you have already set to a different language during your editing process, only for Administrators and Editors, and if enabled in Settings – Writing</li>
</ul>

Language Attribute for Container Blocks and Pages/Posts

Add lang and dir attributes to Group, Columns, Cover, and other specific WordPress Blocks, Templates, or to specific Posts/pages.

Tony Hayes

Want to use and/or not use the new Block Editor (Gutenberg) according to your needs?
Guten Free Options provides this for your WordPressed Burger err I mean Editor.
Guten Free Options allows you to smoothly transition your writing experience to WordPress 5+ by giving you full control over when a post should be edited with the Classic Editor or Block Editor… plus have a button to easily switch between them like other page builders.
With this plugin you can set the default editor to be used at ANY level, and more specific levels will override the previous ones – but only if they are set (similar to how cascading stylesheet inherit rules.)
This means complete flexibility – defaults for multisite networks, single sites, any user role, author preference, as well as being able to easily set default requirements for different custom post types and post templates, and then also switch over or override for individual posts as needed. Here is the list of possible options (in order):
<ul>
<li>Network Default – for Multisite if plugin network activated</li>
<li>Site Editor Default – set the base editor default for the site</li>
<li>User Role Defaults – set a default editor for each role</li>
<li>User Selection – optional default editor per user via profile</li>
<li>Post Type – set a default editor to use for each post type</li>
<li>Post Type Locking – lock any post type at this filtering level</li>
<li>Existing Blocks – use block editor if post has existing blocks</li>
<li>Post Template – set a default editor for each post template</li>
<li>Metabox Override – allows selection on the post edit screen</li>
<li>Querystring Button – easily switch between the editors any time</li>
<li>Admin Override – post IDs or slugs specified on plugin screen</li>
</ul>
Compatible with both WordPress 4.9.x with Gutenberg plugin and WordPress 5 beta+ Block Editor, and includes filters everywhere for further custom use case control.
Also features some extra tweaks:
<ul>
<li>Awesome button on either editor page to switch between editors</li>
<li>Disable the Gutenberg install plugin nag (for WP 4.9 only)</li>
<li>Remove the Gutenberg menu (for Gutenberg plugin only)</li>
<li>Prevent update disabling the Gutenberg plugin (on update to WP 5 only) 
(so you can continue to update Gutenberg plugin separately to core.)</li>
</ul>
Forget your personal editor allergies and install this plugin to just use what you need when you need it! 🙂
<a href="https://wpmedic.tech/guten-free-options/" rel="nofollow ugc">Guten Free Options Home</a>

Guten Free Options

If you like Gutenberg but you want to test drive gutenberg but default to classic, this is the plugin for you!

Works perfectly

Gutenberg Free Options for your WordPressed Burger err I mean Editor.

Language Attribute for Container Blocks and Pages/Posts vs Guten Free Options