- From: Matt King <a11ythinker@gmail.com>
- Date: Wed, 5 Dec 2018 13:32:22 -0800
- To: <public-aria-practices@w3.org>
- Message-ID: <004c01d48ce2$02d33280$08799780$@gmail.com>
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#c arousel Matt
Received on Wednesday, 5 December 2018 21:33:18 UTC