Once upon a time Colin Lieberman shaped the electrons to say...
> Certainly that's reasonable. Yes, you are absolutely right insofar as FF
> goes, although I'm not 100% convinced that authors should be left in the
> driver's seat; this may be something best left 100% in the hands of UA.
The UA c
Gervase Markham wrote:
Before doing that, it might make sense to consult the accessibility
teams of the UA vendors. In Mozilla's case, that's Aaron Leventhal. I
believe that there have been recent changes to this property to better
allow keyboard accessibility of DHTML widgets:
http://develope
Colin Lieberman wrote:
Drop tabindex altogether. It's just not useful.
Before doing that, it might make sense to consult the accessibility
teams of the UA vendors. In Mozilla's case, that's Aaron Leventhal. I
believe that there have been recent changes to this property to better
allow keyboa
Drop tabindex altogether. It's just not useful.
See the Web Accessibility Initiative Interest Group discussion on the
subject:
http://www.w3.org/Search/Mail/Public/search?type-index=w3c-wai-ig&index-type=t&keywords=tabindex&search=Search
Tabindex is not a substitute for poorly organized docum
On Wed, 21 Mar 2007 04:16:41 +0100, Simon Pieters <[EMAIL PROTECTED]>
wrote:
3) The "tab order" should be up to the user. In Opera you can navigate
in any direction you want using e.g. Shift+arrows, allowing you to
freely navigate in tables for instance. The author shouldn't have any
say
Dropping tabindex /might/ make sense if HTML5 was to be so feature
complete that no-one would ever build a DHTML widget out of generic
elements ever again. Is this likely to be the case? Because, if not,
tabindex looks like part of a solution:
http://developer.mozilla.org/en/docs/Key-navigable_cus
On Mar 20, 2007, at 8:16 PM, Simon Pieters wrote:
Hi,
I think tabindex="" has a number of problems:
1) Lacking a feature to scope tabindexes into local contexts, which
I proposed[1] a while back, makes the feature rather useless for
its intended purpose (which, AIUI, was to provide a mean
Simon Pieters writes:
The "tab order" should be up to the user. In Opera you can navigate in
any direction you want using e.g. Shift+arrows, allowing you to freely
navigate in tables for instance. The author shouldn't have any say about
the tab order other than the source order.
In a table, I t
Hi,
I think tabindex="" has a number of problems:
1) Lacking a feature to scope tabindexes into local contexts, which I
proposed[1] a while back, makes the feature rather useless for its
intended purpose (which, AIUI, was to provide a means for the author to
suggest a different tab order t
