- From: Miriam Suzanne via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 21:44:28 +0000
- To: public-css-archive@w3.org
It's strange to me that the issue is about 'off-screen' content, which is seemingly a heuristic browsers understand – but the proposed solution is entirely un-tethered from that concept. I share the concern mentioned above that authors tend to misuse CSS features that don't have an obvious visual impact. Even when there is visual impact: it's extremely different to have something readable-but-not-clickable, and something removed entirely from the AT. And we're not generally providing authors with excellent tools for noticing that difference, or knowing what solution is appropriate. The fact that CSS makes this easier to achieve than JS… does not fill me with confidence. I'm skeptical that the 'carousel' feature which spawned this is being sold as a way solve accessibility issues for authors, but the actual result is a new low-level and invisible-to-debug CSS property that puts the responsibility _back on authors_ to get it right. Meanwhile we've potentially made _getting it wrong_ much easier. I've been following this from the start, and I'm not sure when I should use this, or how to use it _correctly_ without causing issues. Is this going to be another feature (like `order`) that we ship and then tell authors not to use in the ways they expect it to work? Are we inventing solutions to a problem we should be avoiding in the first place? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-3358267254 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 21:44:29 UTC