WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Bryan Garaventa
Date: Feb 9, 2016 5:51PM


Unfortunately carousels can be a pain, since there are so many variables that go into it. E.G mouse interaction pausing and resuming interaction, the same when focus moves into or out of it, the pausing or resuming when desired via an explicit action, and the announcement of slides when manually switching panes though not doing so automatically all the time.



Often this is made more complicated than it needs to be. For example you can make an accessible carousel using standard links and buttons and don't actually need ARIA Tab markup, nor role=grid plus left right navigation, nor ARIA Listbox markup, all of which is usually overkill in many cases.



This implementation is based on the WAI Carousel Tutorial

http://whatsock.com/tsg/Coding%20Arena/Carousels,%20Slideshows,%20and%20Wizards/Carousel%20(Flat%20from%20XML%20with%20Overrides)/demo.htm



Which can also be downloaded from

http://whatsock.com/test/Carousel%20(Flat%20from%20XML%20with%20Overrides).zip

If you want to change the content in the slides. This is pulled from the CDATA tag within the XML file, and accepts any kind of markup including active elements.



Earlier aria-live was mentioned, but this wasn't meant to be used every time a slide changes, just when a slide is manually invoked using the Next or Previous buttons for instance, so that the user is notified of the content change without requiring focus to be moved somewhere else.



Otherwise, when focus is elsewhere on the page, the changing content is ignored by ATs by setting aria-live to ‘off'.



Hopefully this helps a bit.



All the best,

Bryan