Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding expected behaviors for carousels #831

accdc opened this Issue Aug 13, 2018 · 1 comment


None yet
2 participants
Copy link

accdc commented Aug 13, 2018

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.


This comment has been minimized.

Copy link

devarshipant commented Aug 21, 2018

Echoing @accdc;

Consider a carousel operable using left / right arrow keys, that doesn't disrupt focus, and conveys desired information (and status) on the active slide.

It might help to be aligned with Carousel recommendations in Web Accessibility tutorial, or they should be consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.