> 1. Those elements that support the tabindex attribute and assign a
> positive value to it are navigated first.
>
> "0" is not a positive number.
Evidently. Any number theorists in the house?
> That would typically be true, but there are still issues when setting
> the first element to a tabindex="0".
One would only do that if one wanted the element to receive tabbing
in no special way save for its order of appearance in the text.
tabindex="0" is useful. You could add a tabindex value to every <a>
element on the page. The ones you wanted people to navigate through
in a specific order you could assign a positive value to. The others
get 0. But you're consistent in that all the <a>s have a tabindex. I
could imagine this would be an issue of authoring tools more than
anything.
> Navigation does not start. I've
> tested this numerous times and validators do find the tabindex="0" as an
> error.
Evidently the validator is in error.
> Tabindex="0" does get ignored.
It shouldn't be.
--
Joe Clark | joeclark@joeclark.org
Author, _Building Accessible Websites_
<http://joeclark.org/access/> | <http://joeclark.org/book/>