JAWS virtual cursor escapes modal dialog with input field present

[pastr1]

Summary

When using JAWS 2024 and UP/DOWN arrow keys to navigate in browse mode, the JAWS virtual cursor will leave the contents of the modal dialog, and reach content outside of the modal. Whenever there is a modal with text input control, and JAWS is set to AUTO Forms mode, using the DOWN arrow key seems to move the focus outside the modal after reaching the text input.

Steps to reproduce

Reproducible in ARIA APG dialog example and codepen example
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/dialog/
https://codepen.io/monkj/pen/vEBjgQX?editors=1010

Have a button that launches a modal dialog, and within this modal dialog there needs to be an input field. Once the dialog is launched and keyboard focus is within, use arrow keys to navigate in browse mode to reach the input field. Upon further press of the down arrow key, the virtual cursor will leave the modal dialog and begin announcing contents on the page behind. This is only seen with JAWS 2024. With JAWS 2023, the virtual cursor is contained within the dialog and subsequent down arrow presses will remain on the last focusable element in the dialog.

Expected result

The JAWS virtual cursor remains within the modal dialog when using browse mode.

Actual result

The JAWS virtual cursor reached content outside of the dialog when browsing away from an input field within.

JAWS version and build number

JAWS 2024.2411.16

Additional comments

This appears to be a regression from JAWS 2023 as this issue is not observed when performing the same actions with v.2023. When using NVDA v. 2024, the issue does not occur.

[JAWS-test]

This is an error caused by the automatic form mode change in JAWS. This should be avoided because it is so error-prone, see e.g.

• Using virtual cursor to read input field, JAWS reads content of previous field #614
• JAWS not reading form field placeholder text with arrow navigation #688
• JAWS reads the placeholder text of the previous element in browse mode. #679
• Incorrect output of input fields with the virtual cursor  #465
• Search field not properly read in VPC (navigate with arrow keys) mode #690
• JAWS announces previous input's value when reading next input #803
• JAWS drops out of forms mode when focus is programatically moved to an <input> on ArrowUp or ArrowDown #883

The problem also occurs with JAWS 2025.

[pastr1]

Thank you @JAWS-test , I tried the same example with forms mode switching to Manual and browse behavior worked as expected.

Is the recommendation for this issue (or even in general) to disable automatic forms mode switching in JAWS settings? From the related issues this seems like a long-running bug, are you aware if this is being looked at for future versions at all?

[JAWS-test]

@pastr1 Important note: I am not from Freedom Scientific and therefore cannot make any statements about troubleshooting. I can only state as a person who works professionally with JAWS that the problem has existed for many years and has serious effects (see all the linked bugs - and there are even a few more), so I would always recommend disabling automatic mode switching.

[MadanKumar7]

@JAWS-test @pastr1 I am facing the same issue. I have turned off the auto forms mode and it works fine. But, when I press "Enter" to modify the dropdown and then press escape to come out of forms mode, JAWS virtual cursor will leave the contents of the modal dialog, and reach content outside of the modal. How can I overcome this.

[JAWS-test]

@MadanKumar7 I think it would be good to open a new issue for the problem you describe, because it probably has nothing to do with that one in this issue