- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Sep 2017 20:26:36 +0000
- To: public-css-archive@w3.org
> complex-selector only for "up, left, right, down". For nav-index/tab-index there are no complex-selector. It is equivalent of HTML tabindex attribute with additional "none" (non-focusable). Thus Shift+tab is no problem. I don't get your reason why you are against a selector for the `nav-index` property. > nav-order - is it needed if tab-index/nav-index (and tab-index-group) will be implemented? How should work "Visual" for fixed positioned elements? If it will be implemented, the one medium shall be "screen/tv". Yes, `nav-order` is independent of `nav-index`, please see https://github.com/w3c/csswg-drafts/issues/1764#issuecomment-327096527. >> 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. > > Can you explain what you mean by that? As in screen readers 'interpreting' tabindex? I never used a screen reader. So, I am wondering how they read a page. Do they read the whole page at once? And if so, do they consider the `tabindex` attribute set on elements, i.e. do they read text of focusable elements in navigation order or in DOM order? Or do they just read the text of the currently focused element, meaning they implicitly follow the navigation order? Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1748#issuecomment-329286812 using your GitHub account
Received on Wednesday, 13 September 2017 20:26:29 UTC