Revised carousel description

All,

 

Please have a look at my revision to the description of carousel . just the
text down the the examples heading . nothing after that. I have not edited
keyboard, roles, states, or properties. Find it here:

https://raw.githack.com/w3c/aria-practices/issue43-add-carousel-pattern/aria
-practices.html#carousel

 

Here is a quick copy of the text as JAWS reads it .

 

A carousel presents a set of items, referred to as slides, by rotating,
i.e., horizontally scrolling, a subset of the slides into view at a time.
Typically, one slide is made visible at a time, and rotation automatically
starts when the page loads. In some implementations, rotation automatically
stops once all the slides have been displayed. While a slide may contain any
type of content, image carousels where each slide contains nothing more than
a single image are common.

 

Ensuring all users, especially screen reader users, can control slide
rotation is an essential accessibility feature of carousels. If content is
hidden and replaced while a screen reader user is reading it, the experience
can be confusing and disorienting, especially if the user is not aware of
the automatic

slide rotation.

 

Features needed to provide sufficient rotation control include:

 

list of 5 items

1. Rotation pauses when keyboard focus enters the carousel.

2. Rotation pauses when the mouse hovers over the carousel.

3. A button for pausing and restarting rotation. This is particularly
important for supporting assistive technologies operating in a mode that
does not move either keyboard focus or the mouse.

4. Buttons for displaying the previous and next slides.

5. Optionally, a control, or group of controls, for choosing a specific
slide to display. For example, the selection controls can be marked up as
tabs in a tablist with the slide represented by a tabpanel element.

list end