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.

Dennis Ploetner

lucatume

A simple, powerful, and user-friendly plugin that adds multilingual support to your <a href="https://wordpress.org/documentation/article/create-a-network/" rel="ugc">WordPress multisite</a> installation, whether using multiple subdomains or folders. Multisite Language Switcher allows you to effortlessly manage translations for posts, pages, custom post types, categories, tags, and custom taxonomies.
The plugin uses flag icons from <a href="http://famfamfam.com" rel="nofollow ugc">FamFamFam</a>. Thanks to Mark James for his great work. In addition, I would like to thank <a href="https://creativpin.com" rel="nofollow ugc">Jürgen Mayer</a> for creating the plugin’s banner.
Please, don’t forget to <a href="https://wordpress.org/support/plugin/multisite-language-switcher/reviews/" rel="ugc">rate this plugin</a>! 🙂
<h3>Translators</h3>
Thanks to all the translators for their great work.
<ul>
<li>German (de_DE) – <a href="http://lloc.de/" rel="nofollow ugc">Dennis Ploetner</a></li>
<li>Italian (it_IT) – <a href="http://www.freely.de/it/" rel="nofollow ugc">Antonella Cucinelli</a></li>
<li>Dutch (nl_NL) – <a href="http://www.buurtaal.de/" rel="nofollow ugc">Alexandra Kleijn</a></li>
<li>Brazillian Portuguese (pt_BR) – <a href="http://www.coolweb.com.br/" rel="nofollow ugc">Coolweb</a></li>
<li>Spanish (es_ES) – <a href="http://www.ab-weblog.com/en/" rel="nofollow ugc">Andreas Breitschopp</a></li>
<li>French (fr_FR) – <a href="http://www.ab-tools.com/en/" rel="nofollow ugc">Andreas Breitschopp</a></li>
<li>Russian (ru_RU) – <a href="http://j4vk.com/" rel="nofollow ugc">Andrey Vystavkin</a></li>
<li>Ukrainian (uk) – <a href="http://worm.org.ua/" rel="nofollow ugc">Victor Melnichenko</a></li>
<li>Croatian (hr_HR) – <a href="https://github.com/Brankec69" rel="nofollow ugc">Brankec69</a></li>
<li>Romanian (ro_RO) – <a href="http://caveatlector.eu/" rel="nofollow ugc">Armand K</a></li>
<li>Polish (pl_PL) – <a href="http://www.mojito-networks.com/" rel="nofollow ugc">Kamil Frejlich</a></li>
<li>Lithuanian (lt_LT) – Ovidijus Pukys</li>
<li>Catalan (ca_ES) – Joan López</li>
<li>Czech (cs_CZ) – Rastr</li>
<li>Hungarian (hu_HU) – RobiG</li>
<li>Georgian (ka_GE) – <a href="http://www.gwebpro.com/" rel="nofollow ugc">Jas Saran</a></li>
<li>Greek (el) – <a href="http://www.aivazidis.org/" rel="nofollow ugc">Christoforos Aivazidis</a></li>
<li>Serbian (sr_RS) – <a href="http://www.webhostinghub.com/" rel="nofollow ugc">Web Hosting Hub</a></li>
<li>Turkish (tr) – Alican Cakil</li>
<li>Armenian (hy_AM) – Yeghishe Nersisyan</li>
<li>Bengali (bn_BD) – Md. Nazmul Huda</li>
<li>Japanese (ja) – <a href="http://themeboy.com/" rel="nofollow ugc">ThemeBoy</a></li>
<li>Swedish (sv_SE) – <a href="http://www.bernskioldmedia.com/" rel="nofollow ugc">Erik Bernskiold</a></li>
<li>Traditional & Simplified Chinese (zh_CN & zh_TW) – DrBenson</li>
<li>Arabic (ar) – Mohamed Elwan</li>
<li>Norwegian (nb_NO) – Ibrahim Qraiqe</li>
<li>Bulgarian (bg_BG) – <a href="http://www.catblue.net/" rel="nofollow ugc">Vencislav Raev</a></li>
<li>Mexican Spanish (es_MX) – <a href="https://fernandomata.mx/" rel="nofollow ugc">Fernando Mata</a></li>
</ul>
You can translate this plugin on <a href="https://translate.wordpress.org/projects/wp-plugins/multisite-language-switcher/" rel="nofollow ugc">translate.wordpress.org</a>, or if you prefer and have created your language pack, or have an update of an existing one, you can <a href="mailto:re@lloc.de" rel="nofollow ugc">send me</a> your Gettext PO and MO so that I can 
bundle it into the Multisite Language Switcher. You can download the latest POT file 
<a href="https://plugins.svn.wordpress.org/multisite-language-switcher/trunk/languages/default.pot" rel="nofollow ugc">from here</a>.

Multisite Language Switcher

Do I have to add anything else?

Made my life (a lot) easier!

It does exactly what it should

I have been using this plugin in combination with MslsMenu for more than 7 years now. 

For me this is a simple, yet absolutely perfect solution for any multilingual WordPress site. Very easy to use. Easily linking cross-blog pages together without having to worry about any third-party plugin compatibility. 

Its simplicity allows website admins full control over the content of each individual blog. Perfect if not all your blogs offer the exact same content, like country-restricted services such as gift cards or house calls or payment methods.

WordPress MultiSite handles all settings per blog and with MultiSite Language Switcher you can use different date/time formatting, even different email addresses, etc. tailored to the blog's locale. 

Thank you very much for providing the perfect solution, Dennis!

The prefect, simple solution!

A simple, powerful and easy-to-use plugin that will help you to manage multilingual content in a multisite WordPress installation.

Language Attribute for Container Blocks vs Multisite Language Switcher