[Kde-accessibility] Re: Change in kicker behavior: Bug or feature

[Bill Haneman]

RE keynav of the kicker:

If it's at all possible, it makes sense to be consistent with the GNOME
panel.  If gnome-panel is doing something really stupid, then of course
we can revisit the gnome-panel behavior, but in any case we shouldn't
make the user learn two new keynav behaviors for the Free Desktop.

This topic is addressed in the GNOME Panel Keyboard Navigation Proposal
(which isn't really a "draft" anymore, since it has mostly been
implemented for a long time now):

http://developer.gnome.org/projects/gap/keynav/panelnav.html

- Bill


On Sun, 2004-10-17 at 20:32, Aaron J. Seigo wrote:
> On Sunday 17 October 2004 12:22, Olaf Jan Schmidt wrote:
> > Another big accessibility problem for kicker is the lack of keyboard
> > navigation. This probably really dificult to fix, but it is also very
> > important.
> 
> this is THE big one, obviously  and i do consider it as rather important. 
> 
> the way to go is to register a global keyboard shortcut that gives kicker the 
> ok to take keyboard focus and then come up with a set of navigation keys that 
> step through the elements in a ContainerArea one by one... 
> 
> would it be possible for our accessability team to come up with a 
> recommendation for these key schemes and then file a bug report with a high 
> priority detailing this schema? thanks!
> 
> -- 
> Aaron J. Seigo
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility at kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility