Follow up for #1810386: Create workflow to setup multilingual for entity types, bundles and fields

Problem/Motivation

The new workflow for translation settings on bundles is great. But both sighted and screenreader users sometimes do not notice a new table appearing when a bundle is checked to enable translation. This happens especially when there are many entity types and/or the bundle types have many fields.

Proposed resolution

See if any of the patterns from the research in #1810386-79: Create workflow to setup multilingual for entity types, bundles and fields suggest good initial solutions to try.

Remaining tasks

research common pattern for similar situations
implement on proposed resolution
get feedback from manual testing in browser
get feedback from accessibility point of view / using a screen reader

User interface changes

Work in progress. Nothing specific proposed yet. (new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)

API changes

No api changes anticipated.

CommentFileSizeAuthor
#6 UNDBMD-2013.5.24-17.26.png159.2 KBpixelite
Members fund testing for the Drupal project. Drupal Association Learn more

Comments

YesCT’s picture

Issue tags: -sprint

updating tags

Bojhan’s picture

Just wanted to note, this is a problem found in pretty much all interfaces on the web that are complex and do off-screen updates. In Drupal you find it par example, in Views - where you never notice that "updates" are carried out to the live preview.

Other than some ugly signaling, I see no clear solution to this. The thing we can do, is add from the top, rather than from the bottom.

plach’s picture

The thing we can do, is add from the top, rather than from the bottom.

Currently table are revealed in the same order of the entity type list above, I think that swapping their order might be somehow confusing. I think you didn't explain why you are against vertical tabs, which have always seemed the proper solution to me.

mgifford’s picture

Seems like WAI-ARIA is going to need to be injected here. There are some other examples of their proposed use here:
https://drupal.org/project/issues/search/drupal?issue_tags=aria

YesCT’s picture

Assigned: YesCT » Unassigned

unassigning

pixelite’s picture

FileSize
159.2 KB

Just adding a screenshot to illustrate the problem. When I check the 'User' checkbox, a new table is added at the bottom of the page but I can't see this unless I scroll down.

Content language settings config page

Gábor Hojtsy’s picture

Component: translation_entity.module » content_translation.module
mgifford’s picture

Issue summary: View changes

Should this get bumped to 8.1?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.