Marco Almeida | Webdados

Naked Cat Plugins

This plugin aims to provide a way to ensure that any language change in the content of a page 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.
This plugin is heavily inspired by the Jb Audras plugin (including this readme file), and 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 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.
Keep in mind that you should only set the lang and dir attributes to a container block if the content you’re going to insert inside it is written in a different language than that set globally on your website.
As per Web Content Accessibility Guidelines:
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.
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.
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>Add “lang” and “dir” attributes to Group, Columns, Cover, and other specific WordPress Blocks</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

Add “lang” and “dir” attributes to Group, Columns, Cover, and other specific WordPress Blocks.

Tim W

Loco Translate provides in-browser editing of WordPress translation files and integration with automatic translation services.
It also provides Gettext/localization tools for developers, such as extracting strings and generating templates.
Features include:
<ul>
<li>Built-in translation editor within WordPress admin</li>
<li>Integration with translation APIs including DeepL, Google, Lecto, Microsoft and OpenAI.</li>
<li>Create and update language files directly in your theme or plugin</li>
<li>Extraction of translatable strings from your source code</li>
<li>Native MO file compilation without the need for Gettext on your system</li>
<li>JSON (Jed) file compilation compatible with WordPress script localization</li>
<li>Support for standard PO features including comments, references and plural forms</li>
<li>PO source view with clickable source code references</li>
<li>Protected language directory for saving custom translations</li>
<li>Configurable PO file backups with diff and restore capability</li>
<li>Built-in WordPress locale codes</li>
</ul>
Official <a href="https://localise.biz/" rel="nofollow ugc">Loco</a> WordPress plugin by Tim Whitlock. 
For more information please visit our <a href="https://localise.biz/wordpress/plugin" rel="nofollow ugc">plugin page</a>.
<h3>Keyboard shortcuts</h3>
The PO file editor supports the following keyboard shortcuts for faster translating:
<ul>
<li>Done and Next: <code>Ctrl ↵</code></li>
<li>Next string: <code>Ctrl ↓</code></li>
<li>Previous string: <code>Ctrl ↑</code></li>
<li>Next untranslated: <code>Shift Ctrl ↓</code></li>
<li>Previous untranslated: <code>Shift Ctrl ↑</code></li>
<li>Copy from source text: <code>Ctrl B</code></li>
<li>Clear translation: <code>Ctrl K</code></li>
<li>Toggle Fuzzy: <code>Ctrl U</code></li>
<li>Save PO / compile MO: <code>Ctrl S</code></li>
<li>Toggle invisibles: <code>Shift Ctrl I</code></li>
<li>Suggest translation: <code>Ctrl J</code></li>
</ul>
Mac users can use ⌘ Cmd instead of Ctrl.

Loco Translate

must have


Great plugin. Very useful to be able to translate plugins without an external tool like poedit.


Great tool

I'm using it in all one language projects


We recommend this to all of our clients who ask about translations.



It can even be used to "translate" (alter) default English texts within a plugin/theme too.


Awesome Plugin

Great support!


A must-have plugin for managing the lifecycle of translations in custom plugins and themes. 



There's a steep learning curve to climb when it comes to language and translation management. This plugin helps a lot and works really well.



Also impressed with the speed of response to my help topic. Thanks Tim!


Excellent plugin and support

Translate WordPress plugins and themes directly in your browser. Versatile PO file editor with integrated AI translation providers.

Language Attribute for Container Blocks vs Loco Translate