E-mail List Archives
Re: Carousel not accessible
From: JP Jamous
Date: Jan 15, 2018 9:15AM
- Next message: escetic@gmail.com: "Re: Carousel not accessible"
- Previous message: Gurpreet kaur: "Carousel not accessible"
- Next message in Thread: escetic@gmail.com: "Re: Carousel not accessible"
- Previous message in Thread: Gurpreet kaur: "Carousel not accessible"
- View all messages in this Thread
Gurpreet,
It sounds to me as if you guys are using AccessKey and coding around it.
Before answering your question, the proper way for a carousel would be to have a pause and play button. You cannot expect your users to know that a space key would stop the carousel. However, if you provide a pause button then it is clear to keyboard and mouse users.
By expecting your users to anticipate what key to press, you are not in conformance of WCAG. The user is not told how to operate this carousel.
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Gurpreet kaur
Sent: Monday, January 15, 2018 9:36 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Carousel not accessible
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
- Next message: escetic@gmail.com: "Re: Carousel not accessible"
- Previous message: Gurpreet kaur: "Carousel not accessible"
- Next message in Thread: escetic@gmail.com: "Re: Carousel not accessible"
- Previous message in Thread: Gurpreet kaur: "Carousel not accessible"
- View all messages in this Thread