Bug 121335

Summary: AX: elements with explicit tabindex should expose AXFocused as writable, since mouse clicks can focus it
Product: WebKit Reporter: James Craig <jcraig>
Component: AccessibilityAssignee: chris fleizach <cfleizach>
Status: RESOLVED FIXED    
Severity: Normal CC: aboxhall, apinheiro, cfleizach, commit-queue, dmazzoni, jdiggs, mario, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
patch none

James Craig
Reported 2013-09-13 17:39:57 PDT
AX: despite it being removed from the tab order, elements with tabindex="-1" should have their AXFocused state expose as writable (W), since mouse clicks can focus the element. Test case: https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/tests/test-files/test2.html
Attachments
patch (9.37 KB, patch)
2013-10-28 16:55 PDT, chris fleizach
no flags
Radar WebKit Bug Importer
Comment 1 2013-09-13 17:40:09 PDT
James Craig
Comment 2 2013-09-13 17:41:43 PDT
In other words, keyboard tab nav would not cause it to be focused, but the VoiceOver cursor landing on this element would cause focus to be set if VOU pref set focus to follow VO.
James Craig
Comment 3 2013-09-13 17:49:19 PDT
This also needs to work for tabindex="0" and tabindex="1", "2", n… https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/tests/test-files/test3.html
James Craig
Comment 4 2013-09-13 18:00:45 PDT
Blocks UAIG test cases 5, 6, and 9
chris fleizach
Comment 5 2013-10-28 16:55:44 PDT
Mario Sanchez Prada
Comment 6 2013-10-29 03:01:09 PDT
Comment on attachment 215348 [details] patch We'll maybe need some tuning for the GTK/EFL ports but I'm happy with getting this in now and checking later if it's needed or not
WebKit Commit Bot
Comment 7 2013-10-29 09:38:25 PDT
Comment on attachment 215348 [details] patch Clearing flags on attachment: 215348 Committed r158195: <http://trac.webkit.org/changeset/158195>
WebKit Commit Bot
Comment 8 2013-10-29 09:38:28 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.