elements, navigating using up/down arrow page-read keys causes JAWS to announce input values that reflect neighboring input values (instead of their own, if it was blank, and in addition if it had a value).
Expected result
JAWS should read the value of the input which was just navigated to, or "blank" if there was none.
Actual result
JAWS reads the value of the previously navigated-to input element instead of blank, or in addition to its actual value.
Use down-arrow navigation to enter the "Input 1" textbox and enter any value, e.g., "jaws"
Use down-arrow navigation until you reach the "Input 2" textbox
I expect "blank, edit, input 2 edit" but get "jaws, edit, input 2 edit"
Note that this works with reverse navigation (up arrow) + control too, and with or without a value present in the second input. This also works without label-divs, but I have kept them in the codepen for clarity.
This is an old problem that has been occurring for many JAWS versions. Incidentally, it has nothing to do with the fact that the input is nested in div. The problem occurs in all possible constellations, e.g. even if the input is in the label.
The problem is a result of the automatic switch to form mode.
Summary
When inputs are nested within
Expected result
JAWS should read the value of the input which was just navigated to, or "blank" if there was none.
Actual result
JAWS reads the value of the previously navigated-to input element instead of blank, or in addition to its actual value.
Example
https://codepen.io/zfine/pen/ExMmwEE
I expect "blank, edit, input 2 edit" but get "jaws, edit, input 2 edit"
Note that this works with reverse navigation (up arrow) + control too, and with or without a value present in the second input. This also works without label-divs, but I have kept them in the codepen for clarity.
Additional Information
--
JAWS version and build number
JAWS 2023.2303.144
Operating System and version
Windows 10 Version 22H2 (Build 19045.3930)
Browser and version:
Chrome 120.0.6099.225 (Official Build) (64-bit) (cohort: Control)
This is an old problem that has been occurring for many JAWS versions. Incidentally, it has nothing to do with the fact that the input is nested in div. The problem occurs in all possible constellations, e.g. even if the input is in the label. The problem is a result of the automatic switch to form mode.
Duplicate of https://github.com/FreedomScientific/standards-support/issues/465 and https://github.com/FreedomScientific/standards-support/issues/614.
Related: https://github.com/FreedomScientific/standards-support/issues/679