If a field is not translatable, then WCAG 2.0 language of parts requires a lang attribute be applied to that field giving the source language to render on all translations which display that untranslated field. This is not being done.
1. Create a site
2. Extend > enable Content Translation and Language
3. Configure > Languages > add Spanish
4. Structure > Content Types > Basic Page > edit > Language Settings > check Show Language Selector and Enable Translation
5. Content > Add content > create a test page in English, including typing into the Title and Body fields in English > leave Published checked > click Save
6. Click Translate tab
7. On the row for Spanish, click Add
8. Enter the page title in Spanish
9. Don't type in the Body field, as that is not translatable.
10. Save
11. View the Spanish translation
12. Inspect the Body field text
Expected result: Untranslated body field has lang="en" attribute on the Spanish translation to mark that its content has been taken from the English.
Actual result: Untranslated body field on the Spanish translation does not have any language attribute, and therefore is considered to have the page's language, Spanish.
If translation is not allowed on a field, add lang="[site language]" attribute. That said, there may not be a good setting for this, since we don't know what language is in the field. Perhaps we need to have the editor state what language the content is in that is being shared across the original and all translations.
For discussion.
Active
10.1 ✨
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.