Issue metadata
Sign in to add a comment
|
ARC: accessibility tree not focused on first launch |
||||||||||||||||||||||||
Issue description- enable ChromeVox arc support in chrome://flags - launch any app result: focus is somewhat racey. It often takes another alt-tab cycle away and back to the app for ChromeVox to pick up on the window's contents. This is likely due to the focus computation which points a views view to the accessibility child tree. If the view is not focused, then we don't correctly follow the link to the child tree.
,
Jul 18 2017
,
Jul 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b5bb8a4fb44cea51c624b44287b8de4273c517cf commit b5bb8a4fb44cea51c624b44287b8de4273c517cf Author: David Tseng <dtseng@chromium.org> Date: Tue Jul 18 17:13:40 2017 Fix focus state data in AXTreeSourceArc. Rather than relying on events, use the isFocused data from Android AccessibilityNodeInfo. This resolves various issues including: - initial focus. Users can now use Search+left and Search+right on initial launch of the app since focus properly points to content within the app - text field focus/input tracking. Since ChromeVox only reads output from focused text fields, we need this data to be accurate. This was sometimes flakey. TEST=verify consistent tracking of focus when clicking on text fields and other focus transitions. Bug: 744714 Change-Id: I5a304d95a927c6a25f0fa5c3bc002a1771c3a065 Reviewed-on: https://chromium-review.googlesource.com/575568 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by: Yuki Awano <yawano@chromium.org> Cr-Commit-Position: refs/heads/master@{#487508} [modify] https://crrev.com/b5bb8a4fb44cea51c624b44287b8de4273c517cf/chrome/browser/chromeos/arc/accessibility/ax_tree_source_arc.cc
,
Jul 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5df48632e07524d6fed06a1b3cb7079939186b67 commit 5df48632e07524d6fed06a1b3cb7079939186b67 Author: David Tseng <dtseng@chromium.org> Date: Thu Jul 27 05:34:20 2017 Introduce a fallback tree for native arc accessibility support Bug: 745978 , 744714 Test: launch an app known to incorrectly omit task created message. Verify the app uses the fallback tree. Change-Id: Id67b7e958f01667ef7411c51ed8a8a1cac5bee9c Reviewed-on: https://chromium-review.googlesource.com/576547 Reviewed-by: Yuki Awano <yawano@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#489864} [modify] https://crrev.com/5df48632e07524d6fed06a1b3cb7079939186b67/chrome/browser/chromeos/arc/accessibility/arc_accessibility_helper_bridge.cc [modify] https://crrev.com/5df48632e07524d6fed06a1b3cb7079939186b67/chrome/browser/chromeos/arc/accessibility/arc_accessibility_helper_bridge.h [modify] https://crrev.com/5df48632e07524d6fed06a1b3cb7079939186b67/chrome/browser/chromeos/arc/accessibility/ax_tree_source_arc.cc
,
Aug 1 2017
,
Jan 22 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by yawano@chromium.org
, Jul 18 2017Owner: dtseng@chromium.org
Status: Started (was: Available)