Title not translateable

Open on Drupal.org →

Created on 30 July 2022, almost 2 years ago

Updated 12 June 2023, about 1 year ago

Problem/Motivation

The title field is applied across all languages, instead of being translatable. However, the page is marked for language. This means all but one language will have an incorrect language attribute markup, a WCAG 2.0 A violation. Since Title doesn't appear in the Content Type configuration, there doesn't appear to be a way to configure Title to have separate values per translation.

Steps to reproduce

1. Create a site
2. Extend > enable Content Translation and Language
3. Configure > Language > add Spanish
4. Structure > Content Types > Basic Page > edit > Language Settings > check Show Language Selector and Enable Translation
5. Structure > Content Types > Basic Page > Manage Fields > Body > edit > Check User may translate this field

Note that this cannot be done for Title, since Title is not a configurable field. This is a moot point since WCAG 2.0 A requires that users may always translate title, so I would not expect a need to configure this.

5. Content > Add content > create a test page in English > leave Published checked > click Save
6. Click Translate tab
7. On the row for Spanish, click Add

Expected result: Title field label reads Title
Actual result: Title field label reads Title (All languages)

Proposed resolution

Set core to always allow users to translate title. Even if there are 3rd party modules to accomplish this, lack of this feature seems to make core violate WCAG 2.0 A. It needs to be sufficient that if content translation is enabled in core, then title translation is enabled in core.

Remaining tasks

User interface changes

None. It's a WCAG 2.0 A requirement, so I would expect it not to need to be separately configured.

API changes

Data model changes

Release notes snippet

🐛 Bug report

Status

Closed: duplicate

Version

11.0 🔥

Component

Language system →

Last updated about 22 hours ago

Maintained by
🇩🇪Germany @sun

Created by

🇺🇸United States Charles Belov San Francisco, CA, US

Live updates comments and jobs are added and updated live.

Accessibility
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

wcag312

language of parts

Incomplete comments

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 year ago →
🇨🇦Canada mgifford Ottawa, Ontario
I haven't validated this, but it would be under https://www.w3.org/WAI/WCAG21/Understanding/language-of-parts.html
Comment about 1 year ago →
🇺🇸United States Charles Belov San Francisco, CA, US
@sleitner, confirmed.

If Title is treated in Drupal 10 like any other field, then this issue is now a duplicate of 🐛 Untranslated translatable fields on translations of nodes are not marked for Language of Parts Active .

If Title is a special field that is handled differently from other fields, then I need to update the current issue to follow the same wording as 🐛 Untranslated translatable fields on translations of nodes are not marked for Language of Parts Active but as applicable to the Title field.

Which is the case is beyond my Drupal 10 knowledge.

Please advise, or else close as duplicate of 🐛 Untranslated translatable fields on translations of nodes are not marked for Language of Parts Active as appropriate.
Status changed to Closed: duplicate about 1 year ago12:15pm 12 June 2023
Comment about 1 year ago →
🇩🇪Germany sleitner
Closed as duplicate of 🐛 Untranslated translatable fields on translations of nodes are not marked for Language of Parts Active . Title field provides the same language options as other fields, shown in #4.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024