Re: [csswg-drafts] [css-overflow-5] Focus order of generated controls (#10912)

The CSS Working Group just discussed `[css-overflow-5] Focus order of generated controls`, and agreed to the following:

* `RESOLVED: choose option 2 in the issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;dbaron> flackr: we need a well defined focus order when you tab through these generated controls<br>
&lt;dbaron> flackr: aria has guidelines for rough expectation of focus in a carousel-like experience<br>
&lt;dbaron> flackr: this prpoosal aligns with that order<br>
&lt;dbaron> flackr: the buttons are together and occur before the contents of the scroller<br>
&lt;dbaron> flackr: the marker's position is before or after the scrolling contents depending on the scroll-marker-group property<br>
&lt;dbaron> flackr: my proposal is that the buttons... if the markers are before they come first, then the buttons, then the content, then the markers if they come after<br>
&lt;dbaron> flackr: see my last comment in the issue<br>
&lt;dbaron> flackr: one additional thing is question of when to focus the scroll container itself<br>
&lt;TabAtkins> +1 to the Option 2 in the issue<br>
&lt;dbaron> flackr: I think it still makes sense given the previous resolution for the container to come before the content.<br>
&lt;fantasai> Seems reasonable<br>
&lt;dbaron> flackr: so before markers, buttons, container, content, after markers<br>
&lt;vmpstr> q+<br>
&lt;dbaron> astearns: haven't thought about this deeply, but the container focus is not meant to contain the button or makrers?<br>
&lt;dbaron> flackr: right<br>
&lt;dbaron> flackr: focusing the container is typically done to scroll the container, so makes sense as a separate item between the controls<br>
&lt;astearns> ack vmpstr<br>
&lt;dbaron> vmpstr: when focusing the content that means tabbing through all the focus items within the carousel before extiing to the after markers<br>
&lt;ydaniv> +1<br>
&lt;dbaron> flackr: correct<br>
&lt;astearns> ack fantasai<br>
&lt;dbaron> fantasai: by before markers and after markers do you mean ::before and ::after pseudos?<br>
&lt;dbaron> flackr: referring to whether scroll-marker-group property says before or after<br>
&lt;dbaron> fantasai: I see<br>
&lt;dbaron> fantasai: how do we typically lay out the order of a scroll container and its scrollbars?  Is that relevant here?<br>
&lt;TabAtkins> ::scroll-marker-group (before), ::scroll-button()s, scroller, scroller's contents, ::scroll-marker-group (after)<br>
&lt;dbaron> flackr: the scroll bars are not in the focus order<br>
&lt;dbaron> flackr: I think if they were ???... we're treating generaed controls as siblings of the scroller<br>
&lt;dbaron> fantasai: ... seems fine<br>
&lt;dbaron> flackr: I think with implementation and practice using it we'll see if it seems right, but this ist rying to follow best practices for these designs<br>
&lt;dbaron> astearns: what's the use of focusing markers?<br>
&lt;dbaron> flackr: User can tab to active marker, and use arrow keys to select which marker they want<br>
&lt;dbaron> TabAtkins: markers are links<br>
&lt;dbaron> astearns: I suppose AT could say "tab 2 of 4 is active"<br>
&lt;dbaron> flackr: exactly<br>
&lt;dbaron> astearns: sounds like we're converging on option 2, and we'll see how it goes<br>
&lt;dbaron> RESOLVED: choose option 2 in the issue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10912#issuecomment-2489033487 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 November 2024 16:22:55 UTC