Bug 171184

Summary: AX: Expose elements with the ARIA "feed" role
Product: WebKit Reporter: Joanmarie Diggs <jdiggs>
Component: AccessibilityAssignee: Joanmarie Diggs <jdiggs>
Status: RESOLVED FIXED    
Severity: Normal CC: aboxhall, apinheiro, buildbot, cfleizach, commit-queue, dmazzoni, jcraig, samuel_white, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch none

Joanmarie Diggs
Reported 2017-04-22 19:40:36 PDT
(Creating a new bug since bug 151691 seems to be more about navigation and using the feed role. This bug is just about role mapping and ensuring it's not pruned from the tree.) Given: <body> <section role="feed" id="test"> <article>Article 1</article> <article>Article 2</article> </section> </body> I would expect the section element to be in the accessibility tree because it has an ARIA role other than none/presentation. But the element seems to be getting pruned in both Safari and in WebKitGtk. As for the exposure of role="feed", according to https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-feed: * WebKitGtk: ROLE_PANEL + object attribute xml-roles:feed * Mac: AXRole: AXGroup, AXSubrole: <nil>, AXRoleDescription: 'group' Note that at the time of this writing, the Mac's mappings include "Need to verify." A subrole-less group seems appropriate. But should the AXRoleDescription be "group" or "feed"?
Attachments
Patch (7.66 KB, patch)
2017-04-27 11:15 PDT, Joanmarie Diggs 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2017-04-22 19:40:57 PDT
<rdar://problem/31776098>
Joanmarie Diggs
Comment 2 2017-04-27 11:15:35 PDT
Created attachment 308412 [details] Patch
WebKit Commit Bot
Comment 3 2017-04-27 12:38:35 PDT
Comment on attachment 308412 [details] Patch Clearing flags on attachment: 308412 Committed r215886: <http://trac.webkit.org/changeset/215886>
WebKit Commit Bot
Comment 4 2017-04-27 12:38:37 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.