This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 70 - Accesskeys vs. tabindexes
Summary: Accesskeys vs. tabindexes
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.0b3
Hardware: Other other
: P2 minor
Target Milestone: 0.7.0
Assignee: Ville Skyttä
QA Contact:
Depends on:
Blocks: 856
  Show dependency treegraph
Reported: 2002-11-22 17:50 UTC by Ville Skyttä
Modified: 2004-09-15 18:40 UTC (History)
0 users

See Also:


Description Ville Skyttä 2002-11-22 17:50:28 UTC
Validator uses accesskeys 0-9 in its output, makes me wonder if this is a
confusion between accesskeys and tabindexes.  IMO, accesskeys should be letters,
as the current scheme of using numbers limits the range of possible accesskeys
to 10 (0-9).

I suggest changing the current accesskeys to tabindexes (and adding missing
ones), and defining new accesskeys, as letters.

Feel free to assign this to me if you feel I'm right... :)
Comment 1 Terje Bless 2002-11-23 20:28:42 UTC
IIRC the accesskeys were chosen to not conflict so easily with "native" keyboard
accellerators. Reassigning to Ville, setting target 0.6.0 Final, and blocking
Bug #50.
Comment 2 Ville Skyttä 2002-11-25 15:28:38 UTC
Duh, good point.  This clearly needs more thought, postponing to 0.7.0.
Comment 3 Ville Skyttä 2002-11-25 15:29:51 UTC
Removing blocker on #50.
Comment 4 Terje Bless 2004-09-01 16:33:59 UTC
Nominating for 0.7.0 release.
Comment 5 Ville Skyttä 2004-09-15 18:40:18 UTC
For those who have already got used to the current accesskeys, changing them
will be an annoying, backwards incompatible change.  And comment 1 is still a
good point, I cannot figure out how to "fix" this and take that into account.

If there are some issues with the tab navigation, that should be handled
separately.  I'm not aware of such issues ATM (but then again, I haven't tabbed
much in the validator UI).