Cursor routing don't work with IntelliJ idea community edition 2019.1.1, NVDA 2019.1.1 and HumanWare Brailliant BI 40

[Nitram1123]

Steps to reproduce:

Run NVDA Run IntelliJ Open a java file in the editor Test the cursor routing

Expected behavior:

No button works on my Brailliant BI in the editor

System configuration

NVDA version:

2019.1.1

Windows version:

Windows 10

Name and version of other software in use when reproducing the issue:

Java jre 1.8.0_172

Other questions

I believe this feature is supported by NVDA? If not, do you know when it will be? log-nvda.txt

[clementb49]

Hi I think the problem is not caused by NVDA because the routing cursor doesn't work in IntelliJ based IDE with other screen readers like JAWS. For a Java Access Bridge Application, how does NVDA send that the cursor needs to be moved? CC @jcsteh

[mwhapples]

I agree that this looks like an IntelliJ issue. I have inserted additional logging statements into NVDA and that shows correct calculation of new cursor position based on routing keys and calling of Java Access Bridge setCursorPosition function with this value. I also have launched the JDK demo notepad application and cursor routing works there. Inspecting the accessibility information with access bridge explorer, I see one main difference between the IntelliJ editor and the demo application's text control. The demo application's text control has actions where as the IntelliJ editor exposes no actions. May this be linked to the issue?

[seanbudd]

Has this been reported to JetBrains / IntelliJ?

[mwhapples]

I plan to report this to jetbrains today.

[mwhapples]

Here is a link to the JetBrains bug report I have created https://youtrack.jetbrains.com/issue/IDEA-299407/The-main-source-code-editor-view-in-IntelliJ-IDEA-and-other-jetBrains-IDEs-do-not-respond-to-accessibility-setCaretPosition

[mwhapples]

OK, my issue was closed and marked as duplicate of another issue, here is a link to that issue https://youtrack.jetbrains.com/issue/JBR-4599

[fcnjd]

Yes, last year I filled an automated IntelliJ survey where I wrote that there are a lot of accessibility issues, and after that I got contacted by technical support and they created the issues for me, including this one. I hope they'll improve that soon, as there are already a lot of users who wrote that they would find working routing keys helpful as well.