In the Carousel pattern docs it states under "Features needed to provide sufficient rotation control": - Buttons for displaying the previous and next slides.
However, the Auto-Rotating Image Carousel with Tabs for Slide Control Example does not include previous/next buttons. It uses only a tablist for slide navigation (plus a pause/play button for rotation control).
Is this intentional? If so, could the pattern documentation clarify when previous/next buttons can be omitted?
My assumption is that tablist semantics provide equivalent functionality via arrow key navigation between tabs, satisfying the underlying requirement. But it's just that...an assumption!
In the Carousel pattern docs it states under "Features needed to provide sufficient rotation control":
- Buttons for displaying the previous and next slides.However, the Auto-Rotating Image Carousel with Tabs for Slide Control Example does not include previous/next buttons. It uses only a tablist for slide navigation (plus a pause/play button for rotation control).
Is this intentional? If so, could the pattern documentation clarify when previous/next buttons can be omitted?
My assumption is that tablist semantics provide equivalent functionality via arrow key navigation between tabs, satisfying the underlying requirement. But it's just that...an assumption!