Problem/Motivation

From #3041143-14: Add ARIA group roles to Layout Builder UI

The Save Layout and Discard Changes buttons are only at the top of the custom layout, which means that the user will have to backwards tab all the way to the beginning of the customizable section in order to save their layout. I would suggest replicating these buttons at the bottom of the customizable layout area, as well, or providing the keyboard user some other means of getting to these buttons quickly once they have reached the final section of their layout.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#10 jumpToFormActions.png83.96 KBmrweiner

Comments

tim.plunkett created an issue. See original summary.

tim.plunkett credited rainbreaw.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Priority: Normal » Major
tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Parent issue: » #3007978: Accessibility Plan for Layout Builder
mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue tags: +keyboard navigation

tagging

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Issue tags: +sprint

Tagging

ccasals’s picture

ccasals commented
Assigned: Unassigned » ccasals
Issue tags: +Seattle2019

Hi all, I am working on this one for DrupalCon Seattle sprinting (friday)

ccasals’s picture

ccasals commented
Assigned: ccasals » Unassigned

:facepalm: wrong issue! I am not working on this one...

mrweiner’s picture

mrweiner commented
StatusFileSize
new jumpToFormActions.png83.96 KB

Think it'd be appropriate to add a "Jump to Form Actions" link below the layout area in a similar fashion to the "Skip To Main Content" link? Happy to add that in but can't quite tell what's generating that markup.
Jump to Actions Comp

Edit: This could even be attached to the bottom of each section instead of just the bottom of the form.

mrweiner’s picture

mrweiner commented

Actually, as a sidenote, does having the actions at the top of the form even conform to Drupal UI conventions? Action links for core admin-related forms are generally placed at the bottom of the form. See block placement page, block forms, node forms, views, etc. Views buttons were moved from above to below when it was moved into core for D8.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue tags: +wcag243

Tagging for https://www.w3.org/WAI/WCAG21/Understanding/focus-order

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.