why do we design it as a sealed class instead of a simple enum?

I changed the API in the latest commit.

Now there is this class:

class ComposeViewportConfiguration internal constructor() {

    internal var isA11YEnabled: Boolean = true

    fun disableA11Y() {
        isA11YEnabled = false
    }
}

The fun ComposeViewport function now has a configure lambda where a user can change the configuration.

iOS has a similar config and a lambda in the entry point. So I think this would keep simple and allow for more features if needed.

Changed it again according to our discussion:

class ComposeViewportConfiguration internal constructor() {

    @ExperimentalComposeUiApi
    var isA11YEnabled: Boolean = true
}

Maybe ComboBox?

Most similar to TabList (kinda a tabbed role)

Role.Carousel KDoc:

Associated semantics properties for Pager accessibility actions: SemanticsActions.PageUp,SemanticsActions.PageDown,SemanticsActions.PageLeft, SemanticsActions.PageRight

TabList Description:

Keyboard interactions
For the tab list:
Tab
When focus moves into the tab list, places focus on the active tab element.

When the tab list contains the focus, moves focus to the next element in the page tab sequence outside the >tablist, which is the tabpanel unless the first element containing meaningful content inside the tabpanel is >focusable.

When focus is on a tab element in a horizontal tab list:

Left Arrow
moves focus to the previous tab. If focus is on the first tab, moves focus to the last tab. Optionally, activates >the newly focused tab

Right Arrow
Moves focus to the next tab. If focus is on the last tab element, moves focus to the first tab. Optionally, >activates the newly focused tab

When focus is on a tab element in a vertical tab list:

Up Arrow
moves focus to the previous tab. If focus is on the first tab, moves focus to the last tab. Optionally, activates >the newly focused tab

Down Arrow
Moves focus to the next tab. If focus is on the last tab element, moves focus to the first tab. Optionally, >activates the newly focused tab

If the tab list is horizontal, it does not listen for Down Arrow or Up Arrow so those keys can provide their >normal browser scrolling functions even when focus is inside the tab list.

When focus is on a tab in a tablist with either horizontal or vertical orientation: