WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Carousel next and previous buttons

for

From: escetic@gmail.com
Date: Dec 21, 2017 12:12PM

Hi Brian,

You raise a good point but there are some considerations giving me pause.

First, when a user clicks a button I assume they want something to happen, rather than nothing, that we all want some kind of immediate feedback that activating the button has worked as intended. Secondly, I would would want to hear which slide I'm on, at least, and presumably also the heading or title of the slide (otherwise I'd have to memorize which slide is which). I also think on first encountering the carousel, assuming I don't want to skip it altogether, I may want to advance through all slides first, listening to their content, before I get to a point where I know I want to advance from the current slide to slide 6.

If prev/next buttons are also supplemented with arrow key functionality then these could work as an easy method to get from the current slide to slide 6, advancing the slides but bypassing all content but slide number and heading? Meanwhile, prev/next buttons could assume the user wants to hear each slide content?

What do you think?

Rob C


> On Dec 20, 2017, at 8:50 AM, Lovely, Brian via WebAIM-Forum < <EMAIL REMOVED> > wrote:
>
> I tend toward an "inform and empower" policy when it comes to coding with screen readers in mind. I don't suppose any of us think that a screen reader user wants an entire page read out; that's just too much information to absorb, and the user doesn't have the ability to decide what gets read out and when. While this is an extreme example, I think it can inform our decisions on a smaller scale.
>
> I wouldn't read anything automatically, nor would I recommend shifting focus from the slide controls. A carousel, for better or worse, is a common feature that users recognize. A screen reader user who encounters a "previous" or "previous slide" button is likely to examine the surrounding elements and will then discover that they have encountered a carousel. It's the user's decision to consume the slide contents or not. As to shifting focus off the button when it is activated, what if a user wants to advance the carousel by more than one slide? Imagine how irritating it would be to activate the "next" button, have to navigate back to it, activate it again, and so on.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
> Sent: Tuesday, December 19, 2017 3:48 PM
> To: <EMAIL REMOVED>
> Subject: [WebAIM] Carousel next and previous buttons
>
>
>
> Hi All,
>
> Using any example of an paused accessible carousel, when a screen reader user presses enter on a previous or next button, should:
>
> 1) Should focus be placed within the content on the previous or next slide and should this be announced.
>
> 2) Should nothing announce and the onus be on the user to navigate into the slide content themselves.
>
> 3) Is either 1) or 2) acceptable?
>
> Let's us https://wet-boew.github.io/v4.0-ci/demos/tabs/tabs-carousel-en.html as an example of accessible sliders.
>
> My requirements to devs have thus far been that on pressing a previous or next button focus should automatically go to the slide content which should announce preferably its heading, first, followed by slide (e.g. 2 of 3), followed by content, etc.
>
> What does everyone think?
>
> Thank you in advance!
>
> Rob C
> > > > >
> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
> > > >