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

RE: Carousel pattern revisions based on today's meeting

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Tue, 18 Dec 2018 17:05:27 +0000
To: Matt King <a11ythinker@gmail.com>, "public-aria-practices@w3.org" <public-aria-practices@w3.org>
Message-ID: <SN6PR03MB4383DAAB2B6516887A04F7BFF2BD0@SN6PR03MB4383.namprd03.prod.outlook.com>
Thanks,
Personally I recommend the use of aria-current instead of aria-disabled, because aria-current represents the active state which is more important in this case. The disabled state in contrast, implies that this option is irrelevant, which is not true.


Bryan Garaventa
Principle Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com<http://www.LevelAccess.com>

From: Matt King <a11ythinker@gmail.com>
Sent: Monday, December 17, 2018 8:42 PM
To: public-aria-practices@w3.org
Subject: Carousel pattern revisions based on today's meeting

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hey all,

Thank you for the awesome carousel discussion today. I just pushed the following changes to the feature branch:


  *   Revised language throughout the pattern so that auto rotation is not assumed.
  *   Removed use of term "horizontally scroll".
  *   Simplified wording of first paragraph.
  *   In second paragraph about importance of rotation control:

     *   Added sentence about properly hiding content.
     *   Clarified description of auto rotate consequences.

  *   Changed rotation control requirements list:

     *   to unordered list.
     *   to list essential elements first.
     *   To put auto-rotation related requirements in conditional sublist.

  *   In Terms, added slide to the definition list.
  *   In keyboard requirements, added note saying to not move focus when activating the prev/next/auto-rotate controls.
  *   In states and properties, added optional aria-live guidance to basic carousel section.

One question: In a grouped carousel, Should aria-disabled or aria-current be used for the picker button that corresponds to the displayed slide. What I have in the draft now is:

"The picker button representing the currently displayed slide has the property aria-disabled set to true. Note: aria-disabled is preferable to the HTML disabled attribute because this is a circumstance where screen reader users benefit from the disabled button being included in the page Tab sequence."

I was leaning toward aria-disabled because I am assuming that activating the button probably does nothing. It's not like you can "reload" a slide. On the other hand, this use case precisely fits the definition of aria-current. Using both current and disabled at the same time would be quite verbose and kind of overkill.

You can read the draft pattern at:
https://raw.githack.com/w3c/aria-practices/issue43-add-carousel-pattern/aria-practices.html#carousel

Best,
Matt
Received on Tuesday, 18 December 2018 17:05:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 December 2018 17:05:55 UTC