JAWS loses its place when a button that has focus is set to disabled="true"

[SuzanneTaylor]

Summary

On HTML pages, JAWS Virtual Cursor loses its place when a button that the user is on becomes disabled through the HTML disabled property.

1. Go to http://www.manateeroad.com/BugReports/FocusDemo.htm
2. Navigate to the next button
3. Press it twice, so that it becomes disabled
4. Press down arrow to keep reading the page.

Expected result

When the disabled property is set to "true", you should hear something like, "next button unavailable". If you press down arrow, you should hear the sentence that appears just after the button, which is "We should read this after the buttons."

Actual result

The page title is read. If you try to move with the virtual cursor, you find yourself at the top of the page.

Example

http://www.manateeroad.com/BugReports/FocusDemo.htm

Additional Information

JAWS version and build number

2023.2307.37

Operating System and version

Windows 11 Pro 10.0.22621 Build 22621

Browser and version:

Chrome Version 118.0.5993.71 (Official Build) (64-bit) AND Microsoft Edge Version 118.0.2088.46 (Official build) (64-bit)

[JAWS-test]

I can confirm the problem.

It only occurs when reading linearly with virtual cursor, not with TAB navigation.

The problem also occurs with JAWS+Firefox.

The problem does not occur with NVDA.

[BrettLewisVispero]

Imported into ADO as bug 48523

[ThuyTrang144]

I am having the same issue. What is the status of fixing this issue? Is there an alternative solution available? Please help since JAWS is our main-used screen reader for users.

[timhecker]

+1