WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS 15 Vs JAWS 16 (Carousel widget example)

for

From: Robert Fentress
Date: Feb 10, 2016 9:52AM

Another thing to keep in mind, that I just noticed, is that you would
also have to watch out for the edge case where focus is on an element
in a slide and then the slide disappears. In such instances, you'd
have to set focus somewhere sensible--like maybe the newly active
slide button/tab? Man, carousels stink!

On Wed, Feb 10, 2016 at 8:24 AM, Jonathan Avila
< <EMAIL REMOVED> > wrote:
>> So in this case, no aria markup and hidden sections not in the tab order
>
> In the carousel cases like you describe with a small number of panels that slide and in out on a home page I totally agree -- a non-ARIA approach like the one discussed in the WAI Carousel tutorial is what I'd recommend.
>
> My comments were purely around carousels such as those found in video streaming sites or retail sites that likely contain hundreds if not thousands of items consisting mainly of a small picture and a view words that are links. In some cases these carousels may even contain 2 or more rows of items in the same carousel. The idea of multiple rows in a carousel is not that uncommon and starts looking more like a scrolling grid.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
> 703.637.8957 (o)
> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
>