W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2001

Re: Alternate tag of "tabindex", for Netscape

From: Jim Ley <jim@jibbering.com>
Date: Tue, 27 Nov 2001 10:10:51 -0000
Message-ID: <006401c1772b$d07f7e80$ca969dc3@emedia.co.uk>
To: <w3c-wai-ig@w3.org>
"jonathan chetwynd":
> On Saturday 24 November 2001 01:05, Charles McCathieNevile wrote:
> > Jonathan is right that it is not possible to put a tabindex on an img
> > element.

It's a definate oversight in the event binding this (IMHO of course) It
causes an device independance problem - you can interact with the mouse
with just about all elements in the DOM (onclick/onmouseover/onmousedown
etc.) yet there's no way of providing keyboard input to anything but what
you can tab to which doesn't include all elements.

One thing I'm looking at currently is interfaces for various reports,
that are more friendly, I'd like users to be able to go through their
document and be told on each element any problems (currently validation,
but in future all accessibility ones.) However due to the fact there's no
way to create a DI version of this (in all but IE, which has taken a
sensible DI approach to tabindex), I have barriers, I'll be requiring a
mouse.

> Win'98 IE6 does kind of support this, and I'm assured winXP does even
better.

There really should be no difference, I'm struggling to find why...

Jim.
Received on Tuesday, 27 November 2001 05:12:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:58 GMT