more quick navigation keys for the virtual buffer

[mohammed]

It would be nice if the following quick navigation keys could be added:

• r: radio button
  
• x: check box
  
• c: combo box
  
• m: frame
  
• q: blocq quote
  
• s: separator
  
• g: graphic
  

[mohammed]

since this may or may not be related, so advise if this should be opened as a new feature request:

next heading of level x, where x = 1 through 6.

[chris1988]

Replying to mohammed:

more quick navigation keys for the vertual buffer:

we currently have the following single letter navigation keys:

h: heading
l: list
i: list item
k: link
t: table
f: form

it would be nice if we also have:

v: visited link
e: edit box
r: radio button
x: check box
b: button
c: combo box
m: frame
q: blocq quote

Hello,
We currently do have the following key commands:
e for edit fields
b for buttons
v for visited links.
I think there are other tickets for the other quick key navigations.

[pvagner]

Hello,
This is all debatable and I am sure we will get more comments on this.
I'd just like to complete the list of quick navigation keys which are already implemented.

v: visited link
u: unvisited link
e: edit box
b: button

While I am reading some discussion forums e.g. based off of phpBB or Vbuletin software I can see posts are delimited by the field with role separator. Perhaps I'd like to get quick navigation for jumping to the separator if I am not alone.

Also if the adobe flash application is folloving standards it seems to be correctly exposed to accessibility apis. It can therefore be quite usable with NVDA's object navigation. Would it be possible to add a quick navigation scripts for jumping to embedded objects?

[Iris]

Currently, we already have the button, visited link, and edit field commands.

[jteh]

Adding new quick navigation keys for individual elements is in most cases relatively trivial. However, I don't want to add quick navigation keys just for the sake of adding them. I can justify the addition of separator and frame, but I'm not sure of the usefulness of combo box, radio button, check box and block quote. These are just elements on a page; they have no real relevance to common page structure. One might argue that we do have button and edit field, but I can justify those:

• Buttons indicate an action that can be performed. Aside from the obvious structural significance, they may well indicate the end of a form.
  
• Edit fields are often the biggest or most important part of a form. While there may be many form controls, the edit fields often have some structural significance in dividing sections, etc.
  

If people can provide use cases to justify these, they probably do need to be added.

[jteh]

Replying to mohammed:

since this may or may not be related, so advise if this should be opened as a new feature request:
next heading of level x, where x = 1 through 6.

It is related, but it is much more difficult to implement, so should be opened as a separate ticket.

[jteh]

Frame (m) and separator (s) quick nav keys added in r2117.

[Iris]

Replying to mohammed:

It would be nice if the following quick navigation keys could be added:
* r: radio button
* x: check box
* c: combo box
* m: frame
* q: blocq quote
* s: separator

I would also like to append N and shift+N for next and previous blocks of text. As it stands now, it's very time-consuming to read through a webpage with the paragraph or downarrow keys just to find the next block of text. Furthermore, I would like to suggest G and shift+G for next and previous graphics. However, the one mostly needed would be the blocks of text navigation key.

[jteh]

Replying to Iris:

I would also like to append N and shift+N for next and previous blocks of text.

This is already covered in #71. See my last comment there and provide feedback if possible. The term "block of text" is very ambiguous.

Furthermore, I would like to suggest G and shift+G for next and previous graphics.

Is this actually useful in terms of the structure of the document? This one is actually pretty trivial to implement, but I don't follow its practicality.

[mohammed]

I just wanted to "justify" the use of the letter c to jump to the next combo box. in many sites, you would want to only use a combo box to, for example, change language, change country, or change accessibility options.

note that often combo boxes will be on their own, not as a part of a form, like with a button.

as for x for checkboxes, it may be slightly justified to bypass a big chunk of read only control, like agreement to some tos.

I am with the idea of implimenting all possible quick navigation keys as long as this doesn't have a negative effect on something else. what if we add them now even "just for the sake of adding them"? what evil will this cause?

[jteh]

Implemented in r2149.

A separate ticket, #118r, has been opened for the heading level quick navigation keys.