October 2, 2012
You can do that now, using addNav—this way, non-JS users don’t have mysterious, useless links floating around in their markup. You can, of course, still write them into the markup yourself (see the second example carousel).
Currently it’s triggering a click event on the next/prev links, which means that this will only work if you’ve added them to the markup or opted for the script to generate them. This won’t be a requirement on the next release, but for now just hide ’em if the situation calls for it.
Arrow keys, when focus is on the next/prev links or the pagination tabs.
Needs another pass in JAWS, but it’s a lot more usable from a screenreader perspective. You need not do a thing. It does this for you.
The callback param, has been removed—you now have (namespaced) events to hook into.
Created by Josep Martins
© 2013 jquer.in
Curated By Jay Kanakiya