Re: [w3ctag/design-reviews] CSS inert (Issue #1055)

martinthomson left a comment (w3ctag/design-reviews#1055)

Hi @flackr, the TAG just discussed this and we weren't able to work out how the accessibility of something that uses this property would be handled, specifically in this new carousel model examples.

Consider that you have a carousel with all the scrolling business set up (using the new features you are defining, a new scrollable container with linked buttons, etc...).  If you focus the content in that carousel, I'd assume that you could then scroll it to see stuff that was not within the visible space.  As a concrete example, you might have an image carousel with three images shown and a number more offscreen.  Maybe each item has a link or interactive controls.

Someone using a keyboard (arrow keys, tab) might focus the first and then use keys to move to the second and third.  If the fourth is offscreen and therefore inert, would having it be inert make it not possible to focus it with keys?  Obviously, someone clever could avoid the problem by avoiding use of inert for the items that are next up.  But that would seem to defeat the point of having the content be inert.

In general, if we are viewing this as a specialized scroll container, if you look at a regular iframe or `overflow: auto; visibility: hidden` elements, the things that are not in view are not made inert in any way, they just aren't shown.  Accessibility tools know how to handle that.  If this work is providing new scrolling affordances in line with ordinary scrollable content, does the [accessibility advice](https://www.w3.org/WAI/tutorials/carousels/working-example/) you refer to still apply?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1055#issuecomment-2684334587
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1055/2684334587@github.com>