RE: aria-ISSUE-1028 (SeparatorNotWidget): Separator is a structure but the description says it can be interactive [ARIA 1.1]

During the call, we found a way to address the issue that the group saw as containable. Revised text is on its way.

 

From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Friday, May 20, 2016 3:06 PM
To: White, Jason J <jjwhite@ets.org>
Cc: Matt King <a11ythinker@gmail.com>; Joanmarie Diggs <jdiggs@igalia.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: aria-ISSUE-1028 (SeparatorNotWidget): Separator is a structure but the description says it can be interactive [ARIA 1.1]

 

We need to lock ARIA down. This issue was brought in too late. I don't see this important enough to hold up html 5.1 and svg2.

 

Rich

Sent from my iPhone


On May 19, 2016, at 1:45 PM, White, Jason J <jjwhite@ets.org <mailto:jjwhite@ets.org> > wrote:

 

 

From: Matt King [mailto:a11ythinker@gmail.com] 
Sent: Wednesday, May 18, 2016 9:42 PM




My minimum proposal is to get rid of the language that causes readers to falsely believe you could use separator as a splitter widget. Then, at least we can prevent incorrect use of a structural role.

 

Concretely, this would entail omission of the “moveable separator

between two regions in a split pane” example. It could be argued in any case that a moveable separator would need to be assigned a widget role and therefore is not a genuine instance of the separator structural role as presently defined.

 

While I think Matt’s proposal to introduce a new widget role for this purpose is reasonable, I agree with Rich that now is not the time for its introduction.

 

 

  _____  

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

 

Thank you for your compliance.

  _____  

Received on Friday, 20 May 2016 22:26:48 UTC