Added battery level and time to the status tray's accessible name.

chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc

Index: chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc
diff --git a/chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc b/chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc
index 4afc4e3268e07a1232859e3bbe6b5c78b49b381e..88e2b99836eb235937cab578e4cf0108a1a4b2ef 100644
--- a/chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc
+++ b/chrome/browser/ui/views/accessibility/accessibility_event_router_views.cc
@@ -26,7 +26,8 @@
 using views::FocusManager;
 
 AccessibilityEventRouterViews::AccessibilityEventRouterViews()
-    : most_recent_profile_(NULL) {
+    : most_recent_profile_(NULL),
+      most_recent_view_(NULL) {
   // Register for notification when profile is destroyed to ensure that all
   // observers are detatched at that time.
   registrar_.Add(this, chrome::NOTIFICATION_PROFILE_DESTROYED,
@@ -163,6 +164,26 @@ void AccessibilityEventRouterViews::DispatchAccessibilityEvent(
     return;
   }
 
+  // The highest focusable view is processed to handle cases where there are

[sky, 2014/07/11 15:44:02]

It's not clear to me why you want the highest focusable view? If you hover over
|view| isn't |view| the interesting view and not some ancestor? Also, if you are
going to look for a focusable ancestor shouldn't you stop at the first one?

I suspect you want the first ancestor (including view) that would handle the
mouse event, but I'm not sure there. How is this code called?

[dmazzoni, 2014/07/11 16:11:38]

If a view is focusable, it's usually atomic wrt accessibility.

The example this is fixing is the status tray button. The button itself is
focusable and has proper accessibility attributes, and if you focus it with the
keyboard it does the right thing.

It also has several child views - the battery, time, some icons - but when
hovering over these views it doesn't make sense to announce them separately,
because they're all just part of the same button.

[sky, 2014/07/11 19:06:08]

What mechanism does the status tray button use to ensure only it shows active?
Hit targetting? Seems like this code should do the same.

[evy, 2014/07/12 00:32:50]

Aha. If I go to the next highest accessibility focusable view, it works. Does
this implementation seem okay to you?

+  // views inside other focusable views (e.g. hover for date text on the
+  //  status bar) and the status bar information should be read instead

[sky, 2014/07/11 15:44:02]

nit: you've got an extra space at the beginning.

[evy, 2014/07/11 18:15:10]

Done.

+  // of the specific button inside. Here |view| is updated its highest
+  // focusable ancestor.
+  views::View* temp_view = view;
+  while (temp_view->parent()) {
+    temp_view = temp_view->parent();
+    if (temp_view->IsFocusable()) {

[dmazzoni, 2014/07/10 23:25:58]

Nit: in C++, braces aren't needed when the "if" condition and the statement each
fit on one line.

[evy, 2014/07/11 18:15:10]

Done.

+      view = temp_view;
+    }
+  }
+
+  // Since multiple items could share a highest focusable view, these items
+  // could all dispatch the same accessibility hover events, which isn't
+  // necessary.
+  if (type == ui::AX_EVENT_HOVER && most_recent_view_ == view)
+    return;
+  most_recent_view_ = view;

[sky, 2014/07/11 15:44:02]

I don't see this ever set to NULL. What if most_recent_view_ is deleted?

[dmazzoni, 2014/07/11 16:11:38]

It should be harmless because all we ever do is test whether or not
most_recent_view_ is equal to the current view.

Would you prefer ViewStorage here instead, or is this fine, maybe with just a
comment indicating that most_recent_view_ may be invalid and we should only use
it for equality comparison.

[sky, 2014/07/11 19:06:08]

Two concerns: there is nothing stopping the pointer from getting recycled, and
since the member is a view there is nothing stopping code added later on
attempting to use the member as a View and not realizing it may be deleted.
I prefer view storage.

[evy, 2014/07/12 00:32:50]

Done.

+
   ui::AXViewState state;
   view->GetAccessibleState(&state);