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.
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.