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.

Supracorona

💬 
Dear and respected members of the WordPress community, especially those who still believe that “Code is Poetry” — believe it or not, there are people like me for whom this removed feature still matters.
This plugin restores the classic 
“Visual Editor Options” 
section to the user profile screen.
It’s a clean, dependable tweak — made for those who prefer writing in plain text, without distraction, without visual clutter.
No extra settings. No noise. Just the option that once was.
Perfect for:
<ul>
<li>writers who live in the HTML tab,</li>
<li>developers who avoid visual editors,</li>
<li>or anyone who simply misses that checkbox.</li>
</ul>
It works with both the Classic and Block editors, 
and doesn’t require any additional plugins.
Just install, and enjoy the silence of plain text.
<h3>How It Works</h3>
<ol>
<li>A checkbox labeled “Disable the visual editor when writing” is added to each user’s profile page.</li>
<li>When checked, the plugin disables visual editing features and saves the preference (<code>rich_editing = false</code>).</li>
<li>Both TinyMCE and Gutenberg are bypassed — only the plain text editor is shown.</li>
</ol>
Additional behaviors (enabled by default):
<ul>
<li>Prevents loading of unnecessary editor scripts and styles for users who opt out.</li>
<li>Removes visual editor metaboxes when not needed.</li>
<li>Displays a dismissible admin notice if visual editing is disabled but the plugin is no longer active.</li>
</ul>
<h3>Compatibility</h3>
<ul>
<li>Works with both Classic and Block (Gutenberg) editors.</li>
<li>Compatible with the Genesis Framework and most modern themes.</li>
<li>Functions independently — does not require the Classic Editor plugin.</li>
<li>Honors native WordPress capabilities like <code>user_can_richedit</code> and <code>use_block_editor_for_post</code>.</li>
</ul>
<h3>Translations</h3>
This plugin is translation-ready. 
Currently available in:
<ul>
<li>Japanese (thanks to @kimipooh) </li>
</ul>
If you would like to contribute a translation, please visit: 
https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options/

Classic Visual Editor Options


Thank you for providing such a great plugin!I translated the main part into Japanese \^^/;.



When entering code in the classic editor, the forced substitution function would sometimes be activated in the visual editor, so this feature was very useful. I agree with Gutenbeng's philosophy, but it's a shame that the option for a simpler editor is disappearing.


Great plugin!

Restores the “Visual Editor Options” section in user profiles.

Language Attribute for Container Blocks and Pages/Posts vs Classic Visual Editor Options