Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Regarding expected behaviors for carousels #831
Sorry, I posted this in the wrong place earlier.
This is a placeholder for Carousel.
To follow up with our discussion
Personally, I think using interactive form controls such as ARIA Tabs or Listboxes and the like is overkill for carousels, and that a standard Button role is simpler and provides all of the same functionality without forcing screen reader users into and out of Browse/Virtual cursor and Forms/Applications cursor modes when attempting to interact with it.
This is important for variable scenarios when the carousel paradigm may be used to represent interactive regions such as those including links and buttons, or structural content such as headings, images, and tables, or when even representing simulated wizard constructs consisting of sequential forms.
Also, if what was suggested during the call is done, where when the focused Tab is activated focus moves to the slide container, this breaks the ARIA Tab paradigm where focus is not supposed to be moved away from selected tabs when activated, which will end up being just another case of hacking something that isn't meant to be used for such a purpose and breaking it slightly to do something else.