Re: [csswg-drafts] Please add "tab-index" to CSS specification

>>     nav-index: after(<complex-selector>)
>
> how to find element that shall be focused with shift+tab key?

As I [indicated earlier](https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-324283133), it is implied by the forward order. So, in the case of the `after()` function, the element that is focused by pressing <kbd>Shift</kbd>+<kbd>Tab</kbd> (going backwards in the order) is the first one matched by the selector of that function.
If the selector doesn't match any element, `nav-index` is interpreted as it weren't defined.

>>    nav-order: strutural | visual;
>
> The strutural value means the order of the DOM tree?

Yes. I'm open for better names.

>> The CSS including floating, position absolute, fixed and relative can
>> change the visual order of elements, The developer shall have a tool
>> to set appropriate TAB order for all elements.

Very good point! It's an important point to think of vision impaired people in regard of this feature.

> Won't this be really confusing for someone using a text reader, e.g.
> someone blind?
> the DOM order isn't changed, and that's what the text
> reader will use. So the right thing isn't to change the tab order to be
> different from the document order, perhaps, but to tell the browser
> that the document order has (in a sense) changed. What do you think?

How would you do that?

When talking about the "visual order" for the navigation path, I see two solutions for screen readers:

1. Use the DOM order.
2. Follow the layout algorithm and also use the visual order.

Having said that, I wonder if screen readers currently interpret the `tabindex` HTML attribute.

Of course, this also applies to the `nav-order` property I suggested in issue #1764.

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-326408754 using your GitHub account

Received on Thursday, 31 August 2017 20:16:59 UTC