JAWS is narrating the previous input data when focus goes to the next input in browser mode

[neopablix]

trafficstars

Summary

JAWS is narrating the previous input data when the focus goes to the next input in browser mode (up and down arrow keys).

Example: Go to https://codepen.io/neopablix/pen/abOmQYO

1. Put the focus on one textarea
2. Use the arrowDown key until focus on the next textarea or input.
3. You can hear that JAWS is narrating the placeholder or content of the previously selected input.

Expected result

When an input is focused on browser mode, just hear the info for that input.

Actual result

What actually did happen?

Example

https://codepen.io/neopablix/pen/abOmQYO

JAWS version and build number

2019.1906.10 ILM

Operating System and version

Windows 10 Enterprise v1909 build 18363.657

Browser and version:

Chrome v80.0.3987 64bit

[JAWS-test]

The problem also occurs with JAWS 2020. The problem also occurs in Firefox, but not with IE 11.

[bc-NikitaPuzanenko]

I am seeing the same behavior but with button elements. Works fine in IE 11 but in Chrome, when using tab to navigate from a one button to the next, the second button is narrated the same as the first.

[Mesuva]

I'm experiencing the same. I created a very simple test case to double check it wasn't scripting or something else on my page interfering.

I found that if I tried INSERT+DOWN ARROW, to read the full page, the labels and textareas/inputs were read correctly. But using arrow keys, it will highlight the field (using a red box), but read the previously highlighted field.