[Webkit-unassigned] [Bug 241694] New: AX: Consider re-implementing aria-owns to reorder the accessibility tree (to match Gecko and the more recent implementation of Chromium)

[bugzilla-daemon at webkit.org]

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

            Bug ID: 241694
           Summary: AX: Consider re-implementing aria-owns to reorder the
                    accessibility tree (to match Gecko and the more recent
                    implementation of Chromium)
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jcraig at apple.com
                CC: andresg_22 at apple.com,
                    webkit-bug-importer at group.apple.com

AX: Consider re-implementing aria-owns to reorder the accessibility tree (to match Gecko and the more recent implementation of Chromium)

Currently in WebKit, aria-owns maps to AXOwns, and conveys that reference through the accessibility API. IIRC, this was the original expectation of the ARIA group in ~2010 when the aria-owns implementation occurred in WebKit/Chromium (before Chrome forked from WebKit in 2013).

Since that time, Gecko/Firefox) and Chromium have both changed their implementation so that aria-owns allows authors to remap the accessibility tree. 

IIRC, this aria-owns implementation change in Chromium also happened *after* another major architecture change in Chromium, to base the AX tree off the DOM tree (like Gecko) rather than off the Render Tree (like WebKit).

In recent discussions with the ARIA Working Group, it's clear there is wide support for allowing aria-owns to be used to reorder the browser accessibility tree, as well as some anecdotal evidence that some of the original authors intended it to be used this way (pre-2010). 

The ARIA Working Group is therefore seeking a WebKit investigation of the implementation feasibility of this mapping change in WebKit. Personally, I expect this to be possible, but a significant amount of work. We may also want to consider other changes to WebCore/Accessibility at the same time, such as matching the Chromium/Gecko behavior to base the Accessibility tree off the DOM tree.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220616/5edb8809/attachment.htm>