WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Carousel next and previous buttons

for

From: Birkir R. Gunnarsson
Date: Dec 19, 2017 5:44PM

That requirement is fine.
Another (in some ways easier) implementation is to have an live region
with the page title and/or position, e.g.
<div aria-live="polite" aria-atomic="true">
Slide title (x of y)
</div>

When user presses either button the slide title gets inserted into this div.
If this is part of a slide show with a known number of slides you can
do the second part also.
The aXe tool uses this approach when you navigate through groups of issues.
There is a live region that says "issue 1 of 3" and if you press the
next button the focus stays on it and the live region is updated to "2
of 3".
If you implement the widget with tabs and the user presses the next or
previous buttons, the focus should land on the tab control for the
active tab.


On 12/19/17, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
>
>
> 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
> > > > >


--
Work hard. Have fun. Make history.