If a view is in one language, but nodes that are in other languages are displayed, those nodes' contents need to be wrapped in a tag with a language attribute.
Steps:
1. At /admin/modules, enable Content Translation and Language modules.
2. At /admin/config/regional/language, add Spanish, Chinese traditional, Arabic.
3. At /admin/config/regional/content-language, check Content, Article, and Basic Page.
4. At /node/add/page, Add content in English (title and body), save and publish.
4. At /node/1/translations, add translations in Spanish, Chinese traditional, Arabic.
5. Structure > Views > Add new view
6. Check Create a page
7. Set name as test 2.
8. Leave display format as Unformatted list of teasers.
9. Click save and edit
10. Go to /test-2. Note that the language of the view is in English.
11. View source
Actual result: Arabic titles and teasers not wrapped in <div lang="ar"></div>, etc. In some cases there is an hreflang attribute, but that's the language of the target page, not a marking of the language on the current page.
Expected result: Arabic titles and teasers wrapped in <div lang="ar"></div>, etc.
Language on a page not in the page's language is supposed to be marked up with the lang attribute due to the language of parts accessibility requirement.
I would also expect this to happen with fields, although with fields there might be a workaround with rewriting.
Active
10.1 ✨
Last updated
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.