RE: ACTION-2107: proposal for Revised aria-details description

Jason, +1. This is exactly how I was thinking when I made the revisions to
the text .

>Before suggesting any normative language on this or
aria-describedby/aria-details, 

>it would be helpful to find out from the AAM maintainers which APIs can't
handle multiple relationships 

>and how good the prospects are of fixing this at the API level. 

>I think this is a case in which APIs need to catch up with the needs of
today's Web applications.

 

Matt

 

From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Friday, August 19, 2016 5:39 AM
To: Birkir Gunnarsson <birkir.gunnarsson@deque.com>; 'Matt King'
<a11ythinker@gmail.com>; 'ARIA Working Group' <public-aria@w3.org>
Subject: RE: ACTION-2107: proposal for Revised aria-details description

 

 

 

From: Birkir Gunnarsson [mailto:birkir.gunnarsson@deque.com] 
Sent: Thursday, August 18, 2016 5:12 PM

What about aria-details and aria-errormessage?

It would be problematic if aria-errormessage is overridden by aria-details.

Do we need normative language added to this section that says that when both
aria-details and aria-errormessage are present on a form field with
aria-invalid="true" the aria-errormessage takes precedence over
aria-details?

[Jason] Before suggesting any normative language on this or
aria-describedby/aria-details, it would be helpful to find out from the AAM
maintainers which APIs can't handle multiple relationships and how good the
prospects are of fixing this at the API level. I think this is a case in
which APIs need to catch up with the needs of today's Web applications.

 

  _____  

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.

  _____