TVirtualStringTree and ScreenReaders (IAccessibility) problems

[ivancx]

Hello, We are having specific problems with Screen narators (readers) like NVDA (https://www.nvaccess.org/download/) , JAWS and others on TVirtualStringTree when navigatin using keyboard.

Seems like navigating using keyboard (e.g. up, down to change focused node) doesn't "send" text to screen reader. Mouseover works fine - since hitTest amd WM_GETOBJECT messages actions has been implemented in VirtualTree IAccessibility interface implementation and support.

But for cases when selection or focus has been changed by keyboard I believe we have to call

AccessibleObjectFromPoint

manually somehow on this change.

Units VirtualTrees.Accessibility and VirtualTrees.AccessibilityFactory have been written by Marco Zehe i 2007 - seems like it hasnt been updated since then?

We are using latest available source.

[joachimmarder]

Indeed, not much has been done on the accessibility units lately.

If the change you proposed fixes the issue, I will be happy to accept a pull request.

Can the issue be replicated with the sample projects that come with Virtual TreeView?

[ivancx]

Yes. They can be reproducable with every demo.

…

On 31 January 2019 19:38:21 Joachim Marder ***@***.***> wrote: Indeed, not much has been done on the accessibility units lately. If the change you proposed fixes the issue, I will be happy to accept a pull request. Can the issue be replicated with the sample projects that come with Virtual TreeView? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ivancx]

Anyone managed to do something with this issue?

[radioboss]

I sort of fixed this, here's my pull request #950

[MHumm]

What's the status of this pull request?

[joachimmarder]

See discussion in the pull request, this is an issue.