New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigating dialog boxes or applications like on a web page #3676
Comments
Comment 1 by jteh on 2013-12-02 23:07 It's worth noting that often, if the application doesn't have good keyboard control, it probably doesn't have accessible controls at all. (If you can't find them with object navigation, NVDA won't be able to find them any other way.) Also, if this were implemented, it would be very slow. Browse mode is fast because the content is rendered in-process, but we can't do that for an arbitrary object tree, especially if you want overlay classes to be considered. Leaving open because this would be nice, but it probably won't happen any time soon. |
Comment 3 by vgjh2005 on 2014-12-22 01:37 |
CC @LeonarddeR and @derekriemer for general thoughts on this pretty interesting idea and @josephsl to discuss this feature request's impact on Windows 10 UWP apps. |
There is more chance of this happening now that mick has implemented edge support, and we have more idea of how to do this. |
It would be good to have up to date thoughts from @@michaelDCurran and @jcsteh about this subject. Note that this feature suggestion has many aspects that should be considered. For example, how to deal with display model information? I've been working on a system that integrates display model based object nicely into the nVDA objects tree, so that could help. |
I suggest closing this one in favour of #7759 which contains more in depth discussions and even a small global plugin which simplifies object navigation. |
Closing in favor of #7759. Let's continue discussions on that issue. |
Reported by heikofolkerts on 2013-11-30 19:34
Many applications are quite inaccessible because they have no good keyboard control. Many dialogs in such applications have no tab order etc.
If NVDA can recognize the objects within the application it would be very helpful if one could navigate through the controls like one navigates within a web page. E.g. one could jump to all radio buttons in a dialog by pressing r multiple times. The order should be derived from the object tree in deep search mode so that objects contained in a parent object will be visited together. This may not be in a good order but if the application has no keyboard control this is far better.
The requested feature should place the navigator on the next requested object so that the user can read and or activate it. The quick navigation keys can be very close to those in web pages and adding e.g. t for text boxes. If possible the dialog could also be rendered in a kind of virtual buffer so that the user can read the contents by arrowing down.
The requested mode should respect overlay classes so that it is possible to map unrecognized windows classes to known ones.
Blocking #4718
The text was updated successfully, but these errors were encountered: