E-mail List Archives
Re: Carousel not accessible
From: Bim Egan
Date: Jan 15, 2018 3:54PM
- Next message: Jonathan Cohn: "Re: testing keyboard access without a screen reader"
- Previous message: David Engebretson Jr: "testing keyboard access without a screen reader"
- Next message in Thread: David Farough: "Re: Carousel not accessible"
- Previous message in Thread: Jonathan Avila: "Re: Carousel not accessible"
- View all messages in this Thread
Hi Rob and Gurpreet,
I hope the following will help to clear the water a bit:
Jaws and NVDA should not be pausing the carousel using the key combination
Ctrl + space. As Jonathan says, this is a key combination occasionally used
to open a complex link to reveal further options: called a pass key
combination. The revealed content might be a sub-menu, for instance.
And as Birkir said, the space bar pressed on its own will fire an onclick
event, in both JAWS and NVDA.
So there's something else going on. Things to check:
A) Is the carousel movement control an <a> without an href? This could cause
the problem. It won't be very obvious if tabindex has been used to put the
control in the tab order.
B) What element is used to create the movement controller? It should be a
button, or be given the role of button.
C) Is the control the *only* markup in focus at the point when the user
should be able to stop the movement? Or, as Birkir asked, is there an
overlay that is blocking the screen reader from coming into contact with the
control?
HTH,
Bim
- Next message: Jonathan Cohn: "Re: testing keyboard access without a screen reader"
- Previous message: David Engebretson Jr: "testing keyboard access without a screen reader"
- Next message in Thread: David Farough: "Re: Carousel not accessible"
- Previous message in Thread: Jonathan Avila: "Re: Carousel not accessible"
- View all messages in this Thread