W3C home > Mailing lists > Public > public-aria-practices@w3.org > December 2018

Re: Help defining carousel

From: sirisha gubba <nsfsiri2014@gmail.com>
Date: Mon, 17 Dec 2018 08:21:49 -0600
Message-ID: <CAGm6BFOt85upqi_pjVnsZ6ndXQmyAZS0ksA3Lxkn=9U0Z5eQOA@mail.gmail.com>
To: Matt King <a11ythinker@gmail.com>
Cc: public-aria-practices@w3.org
Hi Matt,
I like the updated definition but  the word "horizontal scrolling" is
misleading as carousels do not use a scroll bar to navigate through the
slides.
Rest  of it looks good to me.
Thanks,
Siri

On Wed, Dec 12, 2018 at 10:33 AM Matt King <a11ythinker@gmail.com> wrote:

> Siri,
>
>
>
> Thank you for the suggestions.
>
>
>
> Here is what I have so far for a first paragraph:
>
>
>
>         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.
>
>
>
> Does this capture the essence of a carousel?
>
>
>
> Note that we do not want any implementation details in the descriptive
> paragraph. Also, we typically do not include non-ARIA related accessibility
> requirements, e.g., contrast, in the patterns.
>
>
>
> While nesting carousels sounds completely insane, if someone is crazy
> enough to do it, couldn’t it be done in an accessible way? Usability is
> surely an issue, but I would assume that applies equally to all people and
> is not necessarily a disastrously worse problem for people with
> disabilities.
>
>
>
> Best,
>
> Matt
>
>
>
> *From:* sirisha gubba <nsfsiri2014@gmail.com>
> *Sent:* Friday, December 7, 2018 2:14 PM
> *To:* public-aria-practices@w3.org
> *Cc:* Matt King <a11ythinker@gmail.com>
> *Subject:* Re: Help defining carousel
>
>
>
> 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 Monday, 17 December 2018 14:22:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 17 December 2018 14:22:24 UTC