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 JamaicanUser on 2015-05-28 14:14
For some time, the quick navigation keystrokes in their current state have been unchanged, and new possibilities have not been explored. I propose the following:
A key to move to the next/previous clickable element, even if reporting clickable elements is turned off.
A key to move to the next paragraph or block of text. I have seen this implemented in an add-on on the French add-ons web site, (NVDA extension global plugin), but the add-on is somewhat unusable as the translation is poor. This would prove useful for persons who just want to read non-link plain text.
A keystroke to move to the next division/region. Again, the above mention add-on has a good implementation of this.
Maybe these commands can be unbound by default? Trust me, this is of good use to a power user like myself.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh (in reply to comment description) on 2015-05-28 21:11
Replying to JamaicanUser:
A key to move to the next/previous clickable element, even if reporting clickable elements is turned off.
We could consider this one. However, it's worth noting that this would often not work as expected because often, a much higher container is made clickable and it handles clicks in elements inside it.
A key to move to the next paragraph or block of text.
This is already implemented: control+downArrow.
This would prove useful for persons who just want to read non-link plain text.
That's a different command again and is already implemented: the "n" key.
A keystroke to move to the next division/region.
If you're just talking about HTML div tags, they are internal implementation details and usually aren't useful for navigation. It'd also be very difficult to explain waht this actually does to a user. On some sites, they might be used for big blocks of content. On other sites, every single link in a navigation bar might be a div.
Reported by JamaicanUser on 2015-05-28 14:14
For some time, the quick navigation keystrokes in their current state have been unchanged, and new possibilities have not been explored. I propose the following:
Maybe these commands can be unbound by default? Trust me, this is of good use to a power user like myself.
The text was updated successfully, but these errors were encountered: