- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Tue, 15 Mar 2016 12:40:55 -0400
- To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>, "White, Jason J" <jjwhite@ets.org>, Fred Esch <fesch@us.ibm.com>
- Cc: ARIA Working Group <public-aria@w3.org>, Richard Schwerdtfeger <richschwer@gmail.com>
Hi Amelia,
On 2016-03-15 10:51 AM, Amelia Bellamy-Royds wrote:
> A negative tabindex value will always make an element "focusable but
> not in the current tab order", regardless of whether or not it is
> normally focusable by default.
Apparently, it's not that simple*. The HTML documentation for negative
tabindex says that it "... should not allow the element be reached using
sequential focus navigation". Note that it's a "should not" and not a
"must not". In subsequent note, it gives an example of a keyboard only
user, and states that if the sequential navigation is the only way the
user can move focus to the element then the "... user agent would be
well justified in allowing the user to tab to the control regardless" [1].
[1] https://www.w3.org/TR/html5/editing.html#negative-tabindex
* - me pining for simplicity.
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Tuesday, 15 March 2016 16:41:24 UTC