GuestSpokenFeedbackTest.FocusToolbar also fails on the same reason.

SelectToSpeakTest cases are not timed out anymore (they still fail due to  issue 888750  though). This remains open since SpokenFeedbackTest and GuestSpokenFeedkbackTest still timeouts.  Maybe we should apply the same fix to them?

katie@ made the fix for fixing the timeout for SelectToSpeakTest, just cc-ing.

TestAsNormalAndGuestUser/SpokenFeedbackTest.OverviewMode/0 and TestAsNormalAndGuestUser/SpokenFeedbackTest.OverviewMode/1 are also failing.

These will probably keep failing until we make some changes to accessibility node tree support. I'm talking to dmazzoni and dtseng about this now. I'll take this bug.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/999ba2f0c1a11331937ff2c3985a6bd340abfc9a

commit 999ba2f0c1a11331937ff2c3985a6bd340abfc9a
Author: Jun Mukai <mukai@chromium.org>
Date: Mon Oct 01 22:01:26 2018

Suppress TestAsNormalAndGuestUser/SpokenFeedbackTest.OverviewMode

These tests are now failing on the bots due to the same reason
as other SpokenFeedbackTests.

BUG= 889093 
TEST=none

Change-Id: I1d3ac92f103e5aaf087fa0cb63ac88ceb5b8f631
Reviewed-on: https://chromium-review.googlesource.com/1252337
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595552}
[modify] https://crrev.com/999ba2f0c1a11331937ff2c3985a6bd340abfc9a/testing/buildbot/filters/chromeos.single_process_mash.interactive_ui_tests.filter

I suspect these are failing due to a hit test problem. I'll look and see if there's something simple we can do for SingleProcessMash.

There's no simple fix for this. We need per-widget ui::AXTreeIDs. Marking issue 891773 as blocking.

This will get fixed with the "fence hopping" accessibility serializer.