- From: sirisha gubba <nsfsiri2014@gmail.com>
- Date: Fri, 7 Dec 2018 16:14:19 -0600
- To: public-aria-practices@w3.org
- Cc: Matt King <a11ythinker@gmail.com>
- Message-ID: <CAGm6BFOkNQhAe_3F856ezGNNju8vaJ7QU-CoaBZpNJnCZJb2rQ@mail.gmail.com>
These are few suggestions 😊 - In the first line I will suggest to add “slider” along with carousel - A carousel can have auto rotating images or text slides. So I suggest to “text slides” in the first sentence. - Carousel should have explicit play and pause button - Depending upon the scenario tablist could be a better option then next and previous buttons. - Please add text to avoid nested carousel. Updated definition after Inserting few of the suggestions: A carousel *slider* is a composite widget for rendering auto-rotating image slides *or text slides* for highlighting the activities or accomplishments of an organization and often providing navigation links to more information the topic of the slide. The image is the dominate visual feature of each slide and slides often have additional content in the form of text content for titles and links to additional information. The carousel slides should be contained in a complementary or region landmark with a label identifying the region as containing auto-rotating slides. Slides that are not rendered should be hidden using display: none or equivalent technique. The requirements for controlling the slide rotation include pausing rotation on keyboard focus and pointer hover, an explicit pause *and play* button, previous button and a next slide buttons. Optionally a tablist can be used to provide additional control over the navigation of the slides. I have not addressed other details like buttons and tablist should pass color contrast ratio, image should have alt text, proper structure for the slide, good VFI etc. Thanks, Siri *From:* Matt King <a11ythinker@gmail.com> *Sent:* Wednesday, December 5, 2018 3:32 PM *To:* public-aria-practices@w3.org *Subject:* Help defining carousel Hi all, We are working on wrapping up toolbar this week, and next week, we will focus on carousel. In preparation, one aspect of carousel I'd like some feedback on is the definition paragraph that we include at the beginning of each pattern, especially the first sentence. Following is Jon's first draft. We typically do not include implementation detail in the description, so I will move that out. I'm not looking for grammar or structure help right now. I'd like to know what others believe are the defining characteristics of a carousel. ---------- draft content ---------- A carousel is a composite widget for rendering auto-rotating image slides for highlighting the activities or accomplishments of an organization and often providing navigation links to more information the topic of the slide. The image is the dominate visual feature of each slide and slides often have additional content in the form of text content for titles and links to additional information. The carousel slides should be contained in a complementary or region landmark with a label identifying the region as containing auto-rotating slides. Slides that are not rendered should be hidden using display: none or equivalent technique. The requirements for controlling the slide rotation include pausing rotation on keyboard focus and pointer hover, an explicit pause button, previous button and a next slide buttons. Optionally a tablist can be used to provide additional control over the navigation of the slides. ---------- End draft content ---------- Draft carousel pattern: https://raw.githack.com/w3c/aria-practices/carousel-v2/aria-practices.html#carousel
Received on Friday, 7 December 2018 22:16:58 UTC