[4.0][BackEnd] Scrolling the BackEnd using the keyboard - Usability

[adj9]

Context

In any BackEnd screen (e.g. modules) it is possible to scroll the screen vertically and horizontally.
I bring an example for the modules but the context can be generalized to all the screens with multiple layers.

Steps to reproduce the issue

1 - actions

1. Click with the mouse on the module
2. Scroll with the down arrow on the keyboard
   at the end of the window it automatically switches to the next screen (in this case it is Menu Assignment)

2 - actions

1. Click with the mouse on the module
2. Click inside the white rectangle
   at the end of the window it does not automatically switch to the next screen

Expected result

The expected result in both cases is that there is no transition to the next screen.

Peculiar case

Applying the case 1 positioning myself on Menu Assignment there is the passage to the next screen (Advanced).
By clicking the arrow at the bottom of the keyboard, I expect a block of the page. This is because the Menu Assignment fields are few.

Actual result in all cases

It does not automatically switch to the next screen when using the keyboard. This independent of action 2.2.
In my opinion, the passage to the next screen can be enabled with step 1.1 and the click of the side arrow of the headboard.

Code to be modified

I think it's a rule to be implemented with JavaScript and HTML.

System information (as much as possible)

• Web site
• Safari 13.0.5
• Chrome 81.0.4044.138 (Build ufficiale) (a 64 bit)
• macOS Catalina 10.15.3

[dgrammatiko]

Scroll with the down arrow on the keyboard

The down arrow is also used for changing tabs. This is expected (and actually recommended for a11y) behaviour

PS what is not expected is the scrolling, that is a bug, the down key should not scroll the page (given that we're in the tabs links area). Easily fixable with an event.preventDefault();

[adj9]

For the particular case (described above) I understand the scrolling of the page should not be there. But in another case why shouldn't there be scrolling on the page?

Is the regular behavior present in the documentation?