You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by troopanum on 2012-05-22 19:29
For a substitute to the windows search box, I use a search program called everything.
For example, if I wanted to find a sertain setup file or search for a song on my computer I would type all or part of the name of the file into the edit box then I would press tab.
then I would press the down arrow to find the file I want.
However the edit box works fine with NVDA but when you pres tab and go to the list of files, it just says pane and when you press the down and up arrows it doesn't say anything at all.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2012-05-22 22:27
This is almost certainly due to problems with the accessibility implementation in that application. You should consider requesting that the developer fix the accessibility of the application in the first instance.
Comment 2 by erion on 2012-05-23 08:03
A couple of months ago I have requested a MSAA implementation. The author was very nice and promised that he will add it. I assume he is still working on it.
Closing as we do not have a way to contact the original author of this ticket, and the developer should really fix the accessibility of the application in the first instance.
Reported by troopanum on 2012-05-22 19:29
For a substitute to the windows search box, I use a search program called everything.
For example, if I wanted to find a sertain setup file or search for a song on my computer I would type all or part of the name of the file into the edit box then I would press tab.
then I would press the down arrow to find the file I want.
However the edit box works fine with NVDA but when you pres tab and go to the list of files, it just says pane and when you press the down and up arrows it doesn't say anything at all.
The text was updated successfully, but these errors were encountered: