- From: Rich Schwerdtfeger <richschwer@gmail.com>
- Date: Sat, 13 Aug 2016 11:21:40 -0500
- To: Matt King <a11ythinker@gmail.com>
- Cc: ARIA Working Group <public-aria@w3.org>
Received on Saturday, 13 August 2016 16:22:10 UTC
That is true. However, we did not see the need for multiple descriptions. Also, if you change that it would be a normative change. Since both define a description, the reason for the precedence is that authors can hide aria-details content where they are not allowed to with aria-details - meaning it is accessible to everyone and not just AT users. aria-details is intended to be shown. Rich Rich Schwerdtfeger > On Aug 12, 2016, at 4:56 PM, Matt King <a11ythinker@gmail.com> wrote: > > WRT completing ACTION-2107, Make editorial changes to aria-details, I have one question. > > What is the intended meaning of the following sentence from the aria-details specification? > "When both aria-describedby and aria-details are provided on an element aria-details takes precedence." > > Since aria-details is not part of the name and description calculation, it clearly does not refer to precedence in that calculation. Does it refer to a user agent behavior? If not, whose is responsible for creating the precedence, and how is that precedence manifest? > > Thanks, > matt
Received on Saturday, 13 August 2016 16:22:10 UTC