WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Synchronic Alternatives for Sliders

for

From: Birkir R. Gunnarsson
Date: Feb 10, 2017 1:45PM

Check out the ARIA authoring practices spec for the slider widget:
https://www.w3.org/TR/wai-aria-practices-1.1/

The Paciello Group has a great tutorial on accessible sliders (though old):
https://www.paciellogroup.com/blog/2008/05/aria-slider-part-1/

For carousels,
Google "accessible carousel"
The first 3 matches are great resources.
especially http://www.w3.org/WAI/tutorials/carousels/functionality/

Also check out: http://shouldiuseacarousel.com for a humorous take on
the problem.
With carousels:
User has to be able to stop them (either by clicking a button, or
focus them with the keyboard).
The screen reader user has to figure out what is the carousel area
(you can use regions with aria-labels).
If carousel is stopped but you can still flip thorugh it, screen
reader and keyboard only users need to be able to flip (if there are
next/prev buttons they have to be accessible).


Schnappy Schnappy Schnapp.
-B


On 2/10/17, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
> Hi once more!
> I still have the question: How to make sliders, carousels and slideshows as
> accessible as possible?
> Was my question not understood or is there no answer?
> Thanks, Wolfgang
>
> -----Ursprüngliche Nachricht-----
> Von: WebAIM-Forum [mailto: <EMAIL REMOVED> ] Im Auftrag
> von <EMAIL REMOVED>
> Gesendet: Dienstag, 07. Februar 2017 10:03
> An: <EMAIL REMOVED>
> Betreff: [WebAIM] Synchronic Alternatives for Sliders
>
> Hi!
>
> Sliders are a problem, but sometimes considered as necessary for design. So
> I think about ways to make the best out of them.
>
> Problem of perception with screen readers:
>
> When I list up element types like headings, links or form elements with
> screen reader functionalities (e.g. JAWS+F7), only the elements of the
> current slide are listed. Using a screen reader, You would probably not
> recognize the existence of other content or functionalities, which appear at
> another time.
>
> I don't think, a button, which fans out contents and functionalities of a
> time based (= diachronic) slider in a synchronic alternative is sufficient.
> If You list up links or headings with Your screen reader, You might miss the
> mechanism of a button. Or is this the only way to treat the problem?
>
> And should the alternative be hidden for the SR only?
>
> I'm curious about opinions and best practise examples!
>
> Wolfgang Berndorfer
>
> Innsbruck, Austia
>
> > > > >
> > > > >


--
Work hard. Have fun. Make history.