WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Carousel not accessible

for

From: Jonathan Avila
Date: Jan 15, 2018 2:27PM

Reusing the spacebar which scrolls the screen is problematic. Users would not expect to press control+space. Again space and enter are not passed through to web sites in browser mode -- but control+space is. In forms mode the screen reader will pass through enter and space.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
<EMAIL REMOVED>
703.637.8957 (Office)
Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
Sent: Monday, January 15, 2018 4:19 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Carousel not accessible


Actually, what's happening is our carousel works fine with keyboard only, without NVDA/JAWS. Space pauses the carousel, arrow keys work, etc.

It does NOT work with NVDA and JAWS using these keyboard combinations.

But we found that NVDA/JAWS must use these same keys in combination with Ctrl (e.g. Ctrl+Space, Ctrl+arrow) in order to work the same.

Our devs haven't done anything to listen for ctrl, specifically. The code only listens for onkeypress of arrow and spacebar. We think NVDA may only trigger with onclick but not onkeypress.

We're trying to figure out if needing to use ctrl-spacebar is normal and expected for NVDA/JAWS users in situations where an app is listening for the spacebar onkeypress. My understanding is that the same interactions should be possible for both keyboard only and screen reader users. If a carousel can be paused with spacebar, it should also be pausable with spacebar for NVDA and JAWS users, right?

From what I'm reading here, I suspect ctrl+key is not normal, I don't see any discussion anywhere about this and I think people are actually confused by the question.

We agree that a button would definitely be better but unfortunately that's not feasible so we must make the carousel accessible as it is.



> On Jan 15, 2018, at 3:20 PM, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
>
> Another thing that could be happening here is that you code the
> element to respond to keyboard events (onkeyup or onkeypress). But
> screen readers, in default browse mode, fire the onclick event when
> enter or space bar is pressed.
> The solution could be as simple as adding an onclick event to whatever
> the control is that you are using.
> Since the onclick event is synthetic, make sure there is no visual
> overlay that captures the onclick event before it gets to the element.
> All that being said, having a simple play/pause button (coded with the
> <button> element) is the most straight-forward solution to this, I
> think.
> Remember, auto playing content does not only bother screen reader
> users, the carousel must be stoppable for all users. Having a button
> would achieve that.
>
>
>
>> On 1/15/18, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> From the description it is not clear if space works anywhere on the
>> page or requires a certain control to be focused. Control plus space
>> is likely required because the screen reader is in browse mode and control space is
>> not captured. Shortcuts like this can be problematic because there is no
>> clear method for visual affordance (when no control exists ) or users of
>> screen reader to know the keystroke. Space also provides another function
>> on pages - to scroll except when certain controls are focused.
>>
>> Jonathan
>>
>> Sent from my iPhone
>>
>>> On Jan 15, 2018, at 1:24 PM, " <EMAIL REMOVED> " < <EMAIL REMOVED> >
>>> wrote:
>>>
>>> Hi All,
>>>
>>> The question here is whether it's normal for screen reader users to
>>> need to use the control key to pause/stop/play a carousel. I don't
>>> think it is.
>>>
>>> Spacebar is almost a universal pattern or interaction for
>>> pausing/playing media or timed sequences, by my understanding. Does
>>> NVDA and JAWS have something going on which prevents spacebar alone
>>> from being used to pause/stop/play? Do JAWS and NVDA require
>>> developers to code it in a way which requires a modifier key such as control plus spacebar?
>>>
>>>
>>> Rob C
>>>
>>>
>>>
>>>> On Jan 15, 2018, at 10:35 AM, Gurpreet kaur < <EMAIL REMOVED> >
>>>> wrote:
>>>>
>>>> Hi accessibility experts,
>>>>
>>>> We have a carousel with auto play functionality on website. As far
>>>> as we know that the behavior for the screen reader user is that "
>>>> when carousel comes in focus, space should be used to play/ pause
>>>> the carousel". But in our carousel, space alone is not pausing or
>>>> playing the carousel. We have to use control key along with space
>>>> to perform the function. This is an issue with NVDA and JAWS both.
>>>>
>>>> Without screen reader, we are able to use space key alone.
>>>>
>>>> So my question is, Is this behavior acceptable according to WCAG
>>>> requirements? We need some direction.
>>>>
>>>> Thanks
>>>> Gurpreet
>>>>
>>>> >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > archives at http://webaim.org/discussion/archives
>