🎩 What? Why?

Users using Decidim in other languages than the language initially provided for them cannot understand the "choose language" text, so it should be shown in all locales available for the users.

This also moves the "lang" attribute in the language controls to the link instead of the <li> element which is apparently more correct (according to the original issue report).

There is an related issue with the dropdown control which is that the contents of the control are automatically added to the aria-label attribute which is incorrect. I will look into this as a separate issue, it may also come from Foundation.

WCAG 2.2 / 3.1.2 Language of Parts (Level AA)

https://www.w3.org/TR/WCAG22/#language-of-parts
https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts.html

Testing

Ask a person speaking only another language to choose the language on a Decidim page.

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.