Don't fire a FOCUS accessibility event on a View that doesn't have focus.

ui/app_list/views/start_page_view.cc

Index: ui/app_list/views/start_page_view.cc
diff --git a/ui/app_list/views/start_page_view.cc b/ui/app_list/views/start_page_view.cc
index 31a4b5a6e8f4f88f2a505aee943530563f2b4ab2..a5c45bfd6a18d01269efc147ba078af27d77749f 100644
--- a/ui/app_list/views/start_page_view.cc
+++ b/ui/app_list/views/start_page_view.cc
@@ -86,7 +86,7 @@ class CustomLauncherPageBackgroundView : public views::View {
     selected_ = selected;
     SetVisible(selected);
     if (selected)
-      NotifyAccessibilityEvent(ui::AX_EVENT_FOCUS, true);
+      NotifyAccessibilityEvent(ui::AX_EVENT_SELECTION, true);

[sky, 2016/02/14 16:21:52]

Do you really only want to notify if selected, or if the selection changes?

[dmazzoni, 2016/02/17 00:25:19]

In this particular case a notification when something is selected seems to work
best we need an explicit notification when you use the arrow keys to choose an
app / result, but we don't if you press a key and that unselects an item because
focus is in the text field and pressing the key is already sending accessibility
events there.

Another way to do this would be to make the relationship between the focused
view and the list of results more explicit (e.g., the focused view's accessible
state could include fields like "active descendant" or "selected children"),
then we could just fire a "something changed" type of event and it'd be possible
for the accessibility client to figure out what happened. I was planning on that
as a possible future improvement, but let me know if you'd prefer something like
that now.

   }
 
   bool selected() { return selected_; }