Building upon this question... I'd be curious to hear if there are concerns, or possible mitigations, related to presenting groups of content, like carousels, as adjustables. Intuitively, using an adjustable for a leaf UI element that exposes a singular value makes total sense to me, but relying on this approach to essentially control a scroll position in a nested container or surface content for navigation within a collection seems like more of a reach. To be specific, my concern would be around discoverability of the content within the carousel, particularly among novice users of VoiceOver, who may only be familiar with the notion of default navigation, and may have not encountered situations where content -- potentially important content with associated actions, as described above -- is presented with this alternative navigation approach. In such a scenario, are we confident that users would be able to discover how to navigate reliably within the carousel's content, or is there another recommendation that would help users to skip past long-scrolling carousels for efficiency's sake while maintaining a traditional approach to navigating linearly through that UI? Appreciate any input on this!