WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL]Accessible Carousel Working

for

From: glen walker
Date: Jan 5, 2021 3:38PM

No matter which behavior you choose, you'll make someone unhappy. As a
keyboard user myself, I hate it when my focus gets moved. If I navigate to
the next button and press space/enter to see what's next in the carrousel,
if the contents of the carrousel are not what I want yet, I want to press
space/enter again on the button without having to navigate to it again.

But for other users, if they press next, they might want to hear what was
scrolled into view without having to navigate to the new content.

It's more of a UX issue and you'll have to evaluate which behavior would be
appropriate for your expected audience, if known.

On Tue, Jan 5, 2021 at 3:15 PM Radhika Soni < <EMAIL REMOVED> > wrote:

> Thank you so much for your response and examples. My question here is- If
> we have a carousel with pagination dots and a next and previous button. If
> the user hits the next or previous button, should the focus move on to the
> slide which is shown on the screen or should it stay on the previous or
> next button. Will it cause any kind of violation if we move the focus on
> the slide?
>
> Also, the example you have referred-
> https://www.w3.org/WAI/tutorials/carousels/working-example/ if user moves
> to the next slide the screen reader has to come back to the slide to read
> what is on that slide. Is that ok. Should we not force the focus on the
> slide when the user hits the next slide. Let me know, what are your
> thoughts on it
>
> Thank you in advance!
>
> Regards,
> -Radhika
>
>
>