[Webkit-unassigned] [Bug 151429] New: AX: aria-owns attribute does not work as expected

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=151429

            Bug ID: 151429
           Summary: AX: aria-owns attribute does not work as expected
    Classification: Unclassified
           Product: WebKit
           Version: Safari 9
          Hardware: Macintosh
                OS: Mac OS X 10.11
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jondallas at gmail.com
                CC: webkit-bug-importer at group.apple.com

Hello, my expectation for aria-owns is that a developer can use it to group controls that are not otherwise grouped in DOM. My understanding is it’s a way to achieve and extend similar functionality as native radio controls using the name attribute. The developer can put radio buttons anywhere on the page but if the name property matches they are grouped together and announced as such in assistive technology.

Spec for of aria-owns (which is brief and a little vague): http://www.w3.org/TR/wai-aria-1.1/#aria-owns


Here is a test case:
    <div role="group" id="group">
        <h1>Single state inputs with descriptions</h1>
        <div role="textbox" aria-selected="false" aria-owns="group">Alpha</div>
        <div>Description</div>
        <div role="textbox" aria-selected="true" aria-owns="group">Beta</div>
        <div>Description</div>
        <div role="textbox" aria-selected="false" aria-owns="group">Gamma</div>
        <div>Description</div>
    </div>

I would expect the elements with role="textbook" to announce that they are part of a group of three textbooks and state whether or not this textbook is the selected one. Currently VoiceOver does not do this, likely because this information is not added to the accessibility tree.

Attaching code for the example above.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151119/004f64fa/attachment.html>