W3C home > Mailing lists > Public > public-aria@w3.org > May 2016

Re: aria-ACTION-2067: Write text to state the order of aria-owns ids wrt. the dom child order and sequential aria-owns ids

From: James Nurthen <james.nurthen@oracle.com>
Date: Thu, 26 May 2016 11:31:01 -0700
To: Joseph Scheuhammer <clown@alum.mit.edu>, public-aria@w3.org
Message-ID: <5e6898b5-384e-ec06-32b8-720a6586cd8e@oracle.com>


On 5/26/2016 11:24 AM, Joseph Scheuhammer wrote:
> Hi James,
>
> With respect to this sentence in your new text:
>
> "If the DOM children should not be first then they should also be listed
> in aria-owns in the correct order."
>
> First, is the "should" in lower case on purpose, or is it an RFC "SHOULD"?
No - I will rephrase and re-send.
>
> Secondly, does this change require anything of the browsers?  More
> concretely, is any change to the Core-AAM mapping spec needed?  It
> sounds like browsers should (must?) order the children according to what
> aria-owns specifies, and that directive needs to be noted in the mapping
> spec.
It probably should. I tested this in chrome, FF and IE and they all 
seemed to be doing exactly what I wrote already. I don't have a mac 
available so couldn't test Safari (and have no idea how to inspect there 
anyway)
>
> Thanks.
>
>
> On 2016-05-23 7:12 PM, James Nurthen wrote:
>> Replace
>>
>>                 <p>Authors SHOULD NOT use <pref>aria-owns</pref> as a
>> replacement for the <abbr title="Document Object Model">DOM</abbr>
>> hierarchy. If the relationship is represented in the DOM, do not use
>> <pref>aria-owns</pref>. Authors MUST ensure that an element's ID is
>> not specified in more than one other element's <pref>aria-owns</pref>
>> attribute at any time. In other words, an element can have only one
>> explicit owner.</p>
>>
>> With
>>
>>                  <p>If an element has both aria-owns and DOM children
>> then the order of the child elements with respect to the parent/child
>> relationship is the DOM children first, then the elements referenced
>> in aria-owns. If the DOM children should not be first then they should
>> also be listed in aria-owns in the correct order. Authors SHOULD NOT
>> use <pref>aria-owns</pref> as a replacement for the <abbr
>> title="Document Object Model">DOM</abbr> hierarchy.  If the
>> relationship is represented in the DOM, do not use
>> <pref>aria-owns</pref> except when there are both DOM children and
>> aria-owns and when the order of the children needs to be changed.
>> Authors MUST ensure that an element's ID is not specified in more than
>> one other element's <pref>aria-owns</pref> attribute at any time. In
>> other words, an element can have only one explicit owner.</p>
>>
>>
>> Regards,
>>
>> James
>>
>>
>> On 5/12/2016 10:53 AM, Accessible Rich Internet Applications Working
>> Group Issue Tracker wrote:
>>> aria-ACTION-2067: Write text to state the order of aria-owns ids wrt. the dom child order and sequential aria-owns ids
>>>
>>> http://www.w3.org/WAI/ARIA/track/actions/2067
>>>
>>> Assigned to: James Nurthen
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> -- 
>> Regards, James
>>
>> Oracle <http://www.oracle.com>
>> James Nurthen | Principal Engineer, Accessibility
>> Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415
>> 987 1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com
>> Oracle Corporate Architecture
>> 500 Oracle Parkway | Redwood Cty, CA 94065
>> Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
>> developing practices and products that help protect the environment
>>
>

-- 
Regards, James

Oracle <http://www.oracle.com>
James Nurthen | Principal Engineer, Accessibility
Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987 
1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com 
<sip:james.nurthen@oracle.com>
Oracle Corporate Architecture
500 Oracle Parkway | Redwood Cty, CA 94065
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment
Received on Thursday, 26 May 2016 18:31:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:27 UTC