Link to issue number:

Fixes #14609

Summary of the issue:

NVDA doesn't report multi-line state for Java Access Bridge components that expose it.

Description of user facing changes

NVDA will correctly report multi-line state in applications using Java Access Bridge.

Description of development approach

Added mapping from "multiple line" JAB state to NVDA multiline state. There is already a mapping from "multi_line" JAB state to NVDA state, but the string was incorrect, so NVDA didn't announce it. JAB uses the string from the following resource file: https://github.com/openjdk/jdk/blob/516cfb135f7e5fefaf6e6f2928f6ecb88806f1ef/src/java.desktop/share/classes/com/sun/accessibility/internal/resources/accessibility_en.properties#L114. Existing "multi_line" value probably comes from the name of Java's AccessibleState.MULTI_LINE const, but it doesn't seem to have ever been used as a resource value after looking at the git history. I still kept it in the mapping to ensure backwards compatibility: while unlikely, it's possible that in older Java versions the value was "multi_line".

Testing strategy:

Manual testing with the sample app from #14609. NVDA output before and after the changes:

Before

Single-line text: edit read only This is a text
tab
filler
Multi-line text: edit read only This is the first part of a

After

Single-line text: edit read only This is a text
tab
filler
Multi-line text: edit read only multi line This is the first part of a

Multi-line text is now correctly reported as "multi line". NVDA still reads only the first line, but this seems to be the same as with other read only multiline edits (e.g. NVDA Speech Viewer). Up/down arrows can still navigate the text, and the NVDA+down shortcut will read the whole text.

Known issues with pull request:

None.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.