58997 - Provide option to include objects (images etc) in Tab cycle

Status: VERIFIED WONTFIX

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Description

[Matthew T (active 1999-2002)]

In order to allow a user to do everything with the keyboard that they can do with 
the mouse, and since not all items in the context menu are accessible by other 
means (bug 34357), all context menus should be accessible just using the 
keyboard.

On a basic level, keyboard access to the context menu is covered by bug 36665. 
But that does not ensure that all objects with context menus can be given focus. 
In particular, there is currently no way of giving focus to images and other 
objects (plugins etc) in order to bring up their context menu.

So, I request that a preference (with checkbox GUI) be provided to `Include 
multimedia objects when tabbing between items'.

Comment 1

[Viswanath Ramachandran]

Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
thanks,
	Vishy

Comment 2

[Chris McAfee]

Why should this be an option?  Should images always be in
the tab order?  What does 4.x/IE do?

Comment 3

[timeless]

in order to get context menus for all objects w/o using a mouse *sigh*.

Comment 4

[Lakespur Roca]

Another thing we have to remember is mozilla is in this case trying to be much
better than 4.x which was rather poor in Accessability and IE which is a little
better. That means implimenting some things that IE and 4.x don't have.
Previously in 4.x images were only in tab order if they were also a link. This
makes it difficult for people with out a mouse to get the information on what
this image is. Another interesting thing is mozilla is being implimented in all
sorts of devices. Some with out mouse or other pointing things this will make it
easier for those devices to work properly.  (My first bug response since
returning from disability. Hi every one!)

Comment 5

[Jesse Ruderman]

Tabbing to plug-ins sounds dangerous... the plug-in most likely doesn't provide 
a way to let you "tab out" of the plug-in.

Dup of bug 66285?

Comment 6

[sairuh (rarely reading bugmail)]

jesse: hmm, no. mpt did a kickass job of referring to this in bug 66285
--methinks i'll keep this one around as a seperate [albeit related] issue. for
the nonce. :)

Comment 7

[sairuh (rarely reading bugmail)]

[i was referring to not dupping this, that is. the plug-in issue does indeed
sound potentially sticky.]

Comment 8

[sairuh (rarely reading bugmail)]

*** Bug 69119 has been marked as a duplicate of this bug. ***

Comment 9

[Blake Ross]

-> alecf

Comment 10

[Aaron Leventhal]

I must say, you would not want this as a pref. No one would want to tab to all
images. That said, it's a UAAG requirement to be able to navigate to any
"interactive element", which means anything with an event handler, or context menu.

We'll also have to speak with potential users of this feature to get more ideas. 

Comment 11

[Aaron Leventhal]

reassigning alecf keyboard bugs

Comment 12

[Aaron Leventhal]

I notice that if you view "Page Info" (Accel+I or View:Page Info), there is an
Images tab in that dialog.

It allows you to arrow through a list of images.
This could help us solve the images part of this bug.
For example, it could allow you to get a context menu for images in that list
(via  Shift+F10 or right click). I think you should also be able to right click
on the image shown in the viewing area below the list.

I've also spoken with people about creating an outline view of the current
document, with checkboxes specifying what types of items should be part of the
outline. Hierarchy could be visible through the tree structure. 

Do people see lists and outline views as a valid way to get context menus for
some of these items that don't currently receive focus? Would they still need to
actually focus those items if they could get context menus the other way?

Finally, a fully implemented browse with caret feature might complete our
requirements. It would allow you to navigate anywhere in the page. Navigating
right before an image, a user could press Shift+F10 to get the context menu for it.

Thoughts, defects, shortcomings? Whatever it is, please lay it on the line.

Comment 13

[Matthew T (active 1999-2002)]

> Do people see lists and outline views as a valid way to get context menus for
> some of these items that don't currently receive focus?

No. It would make IMG LONGDESC (for example) horribly difficult to get at.

Comment 14

[Sitsofe Wheeler]

*** Bug 129910 has been marked as a duplicate of this bug. ***

Comment 15

[Aaron Leventhal]

I think the best way to accomplish this is not to add more things to the tab cycle:

1) Browse with caret mode allows you to select any image with the keyboard
2) We can add an images tab to page info or include images in an outline view

Comment 16

[sairuh (rarely reading bugmail)]

mass-verifying Wontfix bugs.

mail filter string for bugspam: Tursiopstruncatus