- From: Birkir Gunnarsson <birkir.gunnarsson@deque.com>
- Date: Thu, 18 Aug 2016 17:12:21 -0400
- To: "'White, Jason J'" <jjwhite@ets.org>, "'Matt King'" <a11ythinker@gmail.com>, "'ARIA Working Group'" <public-aria@w3.org>
- Message-ID: <00ea01d1f995$368b30b0$a3a19210$@deque.com>
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? This language could be simplified and added to the aria-errormessage section as a note. "Note: When aria-errormessage is present on an invalid formfield it takes precedence over other description properties such as aria-describedby and aria-details). From: White, Jason J [mailto:jjwhite@ets.org] Sent: Thursday, August 18, 2016 2:56 PM To: Matt King <a11ythinker@gmail.com>; ARIA Working Group <public-aria@w3.org> Subject: RE: ACTION-2107: proposal for Revised aria-details description From: Matt King [mailto:a11ythinker@gmail.com] All, The action2107-aria-details branch in the ARIA repository contains a proposal for a revised description of the aria-details property. [Jason] +1 to the proposal. As I read it, if both aria-details and aria-describedby are specified, the UA may supply both of them in the accessibility tree, but, since this is not supported on some platforms, only the availability of aria-details is guaranteed in that situation. I look forward to reviewing the corresponding provisions of the AAM. _____ 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 Thursday, 18 August 2016 21:12:47 UTC