A follow-up to #1848940: When enabling or disabling a View, don't move the cursor to the top of the page → to address a similar issue in the Block UI.
When a user enables, disables, or removes a block, a full page refresh happens. This causes the keyboard focus position to return to the start of the page. If a keyboard-only user wants to work on several blocks, there's a lot of work to keep tabbing through the form to the block you are interested in.
We can reduce the amount of effort needed from a keyboard-only user, by using AJAX to dynamically update the page whenever a block is enabled, disabled, or removed. ViewsListBuilder already does this, and it maintians the keyboard focus position.
Use AJAX for the block operations (enable, disable, remove).
Make it preserve keyboard focus position, like ViewsListBuilder.
TBD.
Make some features of the block UI (block operations like enable, disable, remove) behave without a page refresh, and preserving keyboard focus position. Intended to reduce effort needed by keyboard / screen-reader users.
TBD.
None expected.
Active
11.0 🔥
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.
jenniferhoude → made their first commit to this issue’s fork.
I can verify this is still happening.
Steps to recreate: By going to Block structure, selecting a block for disable or delete. When page refreshes the focus is taken to the top of the page.