Skip to content
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

Report object navigation the same as focus #2560

nvaccessAuto opened this issue Jul 25, 2012 · 1 comment


None yet
1 participant
Copy link

commented Jul 25, 2012

Reported by jteh on 2012-07-25 07:09
Currently, we use REASON_QUERY for object navigation, which means you hear a lot more information than you do for focus; e.g. focus silences certain roles, etc. This could make object navigation overly verbose and seem less user friendly. This is particularly relevant for touch screen users, who will use object navigation more than keyboard only users. I propose that we should isntead use REASON_FOCUS (or something similar) for object navigation. The report current navigator object command should still use REASON_QUERY to allow the user to query this information on demand, just as we do for report focus.


This comment has been minimized.

Copy link

commented Aug 13, 2012

Comment 1 by jteh on 2012-08-13 00:27
Done in 1044ded.
Milestone changed from None to 2012.3
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.