Comment 1 by mdcurran on 2008-06-27 07:09
Could you please give an example of some situations where this may be useful?
Also, can you clarify exactly what you mean by clickable element. Do you mean the fields that NVDA reports as 'clickable' (they have an onclick attribute) or do you also mean to include any other element that can be clicked, such as links and form fields?

Comment 2 by surfer0627 (in reply to comment 1) on 2013-12-09 01:35
Replying to mdcurran:
Hello developers,
Is it possible to add a single character key for clickable element?
It is useful on Google book mark, youtube, and other web pages.

I know that character (c, l, i, k) are already assigned.

Maybe we could use / or other key for this navigation.

Thank you.

Comment 3 by surfer0627 on 2014-02-04 09:44
Example:
In this web page, there are 4 clickable elements that user could move to other pages by clicking it.

It would be great that NVDA could add quick nav. key for next and previous clickable element.

Notes:
browser: Internet Explorer

page link:
http://www.businessweekly.com.tw/KBlogArticle.aspx?ID=4549&pnumber=2

Comment 7 by surfer0627 on 2015-01-27 06:30
Hi,
Let's come back to this issue. Here is an example.
If user use Google Bookmarks to create a new bookmark.
In the web page, there are two clickable elements "Cancel" or "Add bookmark".
Hoping that user could use quick nav to jump to clickable elements.
Thanks.
notes:
clickable element: means the fields that NVDA reports as 'clickable' (they have an onclick attribute).

Comment 8 by leonarddr on 2015-02-06 15:56
I could give implementing a try, though only when devs agree.

I thoroughly agree - more and more clickable elements are appearing in websites and particularly online ocument editors and creators. I would like to request not only clickable elements to have a single letter navigation key assigned (or available but unassigned by default through Input Gestures dialog) but also its listing in the Elements List dialog, as some websites have a particularly large numbr of clickable elements.
Thanks for your consideration.

I agree with the need of a Quick Nav key to clicable elements, but only
agree with the inclusion of clicable elements in the Elements list if it is
one more option like Links, Titles and so on...
The reason for this is the enormous number of licable elements, in some
pages, with no meaning...

Hi,

I agree that this function can simplify using web, cause more and more webpages use this (onclick) element. I think possibility to assign letter and shift+letter should be enough.

Adding to this, assigning a keystroke to application should be possible.
Like here, maybe not by default have one ssigned though.

I also still agree this might be helpful. What quick nav key would be suitable for this? We have j, p, y and z left if it comes to alphanumeric keys. I belief jaws uses ; (semicolon) or / (slash) for this.

Hi,

I prefer one of letters due to Slovenian and some other keyboards does not have "/" or ";" as "free" keys. it means if I wanted to press those characters I would press shift key plus another key.
Yes, I can assign a diferent key for slovenian users via gestures.ini but I think, this is not a good solution. however I will accept your suggestions and than I will try to customise NVDA as little as possible to make slovenian users comfortable.

thx, J

any news about this ticket?
It is very interesting and the Y letter is a good idea.

Hi.

Bumping this issue due to constant conversations on the email list about it. I do agree that it is relevant, and Y or Z can be a key for this purpose. Any thoughts @michaelDCurran @josephsl @jcsteh and @feerrenrut?

Hi.

W is already used for spelling errors. I think Y is the best option at the moment.

In #10424: I added support for quick navigation scripts that are unbound by default.

This can now be implemented pretty easily, as we now support quicknav scripts that are unbound by default.

Hi. Well then, I think it's time to seriously look into implementing this.

Hi.

Any update on this? I'd think it would be quite the simple fix. I however don't know the first clue of coding to do this :(

cc: @feerrenrut

Well, all I will say is that clickables do seem to have increased a lot in the last five years or so. I really do not understand why they are needed rather than links, but obviously there has to be a reason so feel its entirely appropriate now to need some way to isolate these and present t them so users may be able to find them easier. Brian

@feerrenrut
@seanbudd

Is there any news on this issue?
Thanks

leonardder commented on 19 Nov 2019

This can now be implemented pretty easily, as we now support quicknav scripts that are unbound by default.

@LeonarddeR would you mind to create an add-on that makes possible the navigation through clickable items?if you have time?

Also let us know if you do not have plan to work on this, e.g. I'm not really interested in taking this further, honestly.

Thanks.

closing in favor of #14429 which has been filled more according to the template and is more prominent being newer.

Feel free to install NVDAExtensionGlobalPlugin add-on to get that funcionality.
https://github.com/paulber19/NVDAExtensionGlobalPlugin.git