earl.johnson@Eng 1998-05-29

This long winded report is saying that known group components (JRadioButton, JMenuBar, and JToolBar) should us the arrow key to navigate between the objects within the the component not the Tab key. The keyboard navigation bugs that cover this are:
o JRadioButton: 4104452 (Win32), 4104454 (Motif), 4110476 (JLF)
o JMenuBar: 4104403 (Win32), 4104398 (Motif), 4112265 (JLF)
o JToolBar: 4104431 (Win32), 4104433 (Motif), 4112280 (JLF)

=========

Name: mf23781 Date: 05/28/98


The implementation of keyboard accessibility does not work in button groups.

Currently all buttons in a button group (in Swing) are in the tabbing order.
The problem with this is it actually reduces the accessibility
efficiency by placing to many components in the tabbling order
for applications that contain many buttons. IBM has this problem
with their new BluePages (Company Phone Book) JFC application which we are trying to
make accessible.

What should actually occur is the first button in the button group
(example: radio buttons). Once that button has the focus, the user should
only be able to use the arrow keys to switch focus to each component within
the button group. The Tab key, at any point would have the user Tab out
of the group to go to the next Component in the tabbing order.

Note: Toolbars should operate in the same fashion as toolbars can
be considered a button group as well.


======================================================================