Disabled input not properly read when in a table with no value

[BEpic123]

Summary

If you have a disabled input with no value in a table, then JAWS will not inform the user that the input is unavailable.

Example:

1. Find or quickly throw together some HTML with a table containing an input field of type "text". Set the input to disabled and do not add a value attribute so the input is blank.
2. Turn on JAWS and enter the table.
3. Navigate to the table cell containing the disabled input. (Can use Ctrl + Alt + Arrow keys)
4. JAWS will not inform you that the input is unavailable.
5. Add a value to the input and try again.
6. JAWS will inform you that the input is unavailable.

Expected result

JAWS will inform the user that the input is unavailable by reading out something to the effect of "... edit unavailable blank..."

Actual result

JAWS does not indicate the input is unavailable and reads out something to the effect of "... edit blank..."

Example

> A test case that demonstrates the issue - provide linked test case, CodePen, JSbin, etc...

Additional Information

JAWS version and build number

JAWS Version 2022.2204.20 ILM

Operating System and version

Windows 10 Build: 19044.1826

Browser and version:

Chrome version 104.0.5112.80 (Official Build)(32-bit)

[JAWS-test]

The problem only occurs when navigating to the table cell with Ctrl + Alt + Arrow keys, but not when reading linearly with the Arrow keys.