VoiceOver: QuickNav Less Responsive Than Native Operations

Originator:listsebby
Number:rdar://19901080 Date Originated:20-Feb-2015 10:55
Status:Open Resolved:No
Product:Accessibility Product Version:OS X
Classification:Performance Reproducible:Always
 
Summary:
With QuickNav turned on, the responsiveness of VoiceOver navigation is subtly, but noticeably, less than that of native VoiceOver commands, as performed using the VO keys, the commanders, or with the Control-Option lock.

Steps to Reproduce:
1.  Take any window.  Give it focus, and have VoiceOver on.

2.  Use VoiceOver commands to navigate the window, especially by moving through it using VO-left and VO-right, or by interacting with any text, and using VO-up and VO-down.  If you have a commander set up, such as a numpad commander, you can use this also.

3.  Make sure Quicknav is on.  Perform the exact same steps just using the arrow keys, with QuickNav on; that is, left and right, up and down.

4.  Optionally, repeat step 1, and use the Control-Option-lock feature of VoiceOver to hold down the VO keys, so that you are still using just the arrows.

5.  Optionally, use a text field and standard arrow-key navigation, and observe that it is not unlike the performance of standard VO commands, but is also substantially better than that of QuickNav.

Expected Results:
QuickNav should, from a performance point of view, be indistinguishable from the use of standard VO navigation commands or commanders, with or without Control-Option lock, or with text fields using standard arrow-key navigation.

Actual Results:
There is a slight, but noticeable, and highly aggravating loss of efficiency using QuickNav.  Productivity is hurt on a laptop keyboard.

Notes:
This problem has been around for a good long while now, and I suddenly realised that that's why I use a keyboard with a number pad, and numpad commander.  Without it--that is, on a Bluetooth keyboard or a notebook--the need for QuickNav is much more pronounced.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!