You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the carousel example, when traversing the DOM with the keyboard the user is required to cycle through all the list items before they can tab put of the carousel.
Would it be better to only allow tabbing to focus visible elements instead of revealing the next "page" of list items? If the tab order went
First visible item
N visible items
Last visible item
Next pagination button
Next focusable DOM element
Paging to the next set of list items would be triggered with an arrow key while a visible list item has focus, or by the pagination button.
The text was updated successfully, but these errors were encountered:
The intent is to handle this by using the inert property to remove the content on the non-visible pages from the tab flow. I haven't prototyped it in the JS polyfill yet but it should behave exactly as you expect.
In the carousel example, when traversing the DOM with the keyboard the user is required to cycle through all the list items before they can tab put of the carousel.
Would it be better to only allow tabbing to focus visible elements instead of revealing the next "page" of list items? If the tab order went
Paging to the next set of list items would be triggered with an arrow key while a visible list item has focus, or by the pagination button.
The text was updated successfully, but these errors were encountered: